Lucid Emacs newsgroups
Jim Thompson
>Thanks to Kyle Jones, we now have a pair of newsgroups bidirectionally
>gatewayed into the bug-lucid-emacs and help-lucid-emacs newsgroups.
>They are alt.lucid-emacs.bug and alt.lucid-emacs.help.
>
>I expect that many of you will want to unsubscribe from the mailing lists,
>and read the messages in newsgroup form instead. However, I would advise
>you to wait a few weeks before unsubscribing, so that we know that the
>gateway is functioning properly.
They appear to be working, as we're receiving them here on Sugar.
I need help with a problem. I built lemacs-19.2 on my box at work, a
Sparc 2 running SunOS-4.1.1 and X-windows release 5 (patchlevel 8, I
think), using gcc 2.0 and the Motif widget set.
When I run the dumped xemacs, it just sits there, doing nothing. If I
run temacs, it spits out a message saying that ASCII functionality
isn't available, and that I should check my DISPLAY variable to see
that it's set properly (it is).
Now, I read about a similar bug in the help-lucid-emacs archive, which
was caused by lemacs picking up emacs 18 lisp code rather than the
emacs 19 lisp. I tried this solution, by explicitly setting the
initial load-path in paths.h, and recompiling, but no joy.
Is there another variant of this problem, one with similar symptoms,
or am I just not setting up the load-path correctly? Can anyone
suggest how I might be able to tell?
>We wanted the newsgroups to be gnu.lucid-emacs.bug and gnu.lucid-emacs.help,
>but the FSF folks are not willing to allow the creation of those groups.
>In fact, it would appear that they are unwilling even to allow us to
>announce the existence of our version of emacs on their newsgroups.
Ah, but your lucid-emacs has the scent of commercial software heavy
about it; it may be freely distributable, but it is tainted
nevertheless. Can't have ideologically impure influences in the gnu
newsgroups!
--
_
_| ~-. James C. Thompson | "The place to be happy is here.
\, _} Webster, Texas | The time to be happy is now."
\( ji...@sugar.neosoft.com | -- Robert Green Ingersoll
Jamie Zawinski
In message <1992Jul02.1...@NeoSoft.com> Jim Thompson wrote:
>
> When I run the dumped xemacs, it just sits there, doing nothing.
Possibly this is the bug where emacs gets stuck in a loop in next_window
because it's trying to make an impossibly small window, because of bad
resource settings. Try "xrdb </dev/null" and see if that helps. If not,
run xemacs under gdb and see what it thinks its doing.
> If I run temacs, it spits out a message saying that ASCII functionality
> isn't available, and that I should check my DISPLAY variable to see
> that it's set properly (it is).
A side effect of the fact that tty support doesn't exist yet is that you
can't really run temacs except in batch mode.
-- Jamie