Re: xemacs under version 2.3.3
Re: xemacs under version 2.3.3
- Subject: Re: xemacs under version 2.3.3
- From: Samuel Isaacson <email@hidden>
- Date: Tue, 19 May 2009 15:14:34 -0600
"xemacs -vanilla" has the same problems...
I tried the two commands you suggest.
(system-name)^J immediately gives "wanderer-3.local" my hostname.
(display-device nil)^J gives "Symbol's function definition is void:
display-device".
My xemacs has always, in the past, started near instantaneously even
with startup files loading. If it routinely took 20 seconds I probably
would give up and switch to another editor.
Anyways I'll just alias it to explicitly set the display and then
everything is nice and quick...
Thanks for your suggestions,
-Sam
robert delius royar wrote:
Mon, 18 May 2009 (20:27 -0600 UTC) Samuel Isaacson wrote:
Thought I had emailed that to the list, but must have forgot to...
The display variable is set to:
DISPLAY = /tmp/launch-1CQvwq/:0
Running "xemacs -display ${DISPLAY}" hangs and takes a while to start
(just like running xemacs with no arguments). Using "xemacs -display :
0.0" works fine though...
I compile the 21.5 Mecurial sources on my iMac whenever they are
updated. I rarely have problems, but when I do, the XEmacs Beta mailing
list has always been helpful. I am not sure whether 21.4 has the
display-device function, but if it does, it might tell you what XEmacs
thinks it is connected to. I have been doing this since 2002.
When you are having problems, it is best to start your XEmacs without
any local startup files to make sure the error is not in code that you
are loading locally. [See if `man xemacs' works.]
Try starting with the command `xemacs -vanilla' to tell XEmacs to start
without extra site files or set up. Give it time to settle. The 21.5
branch (for example) takes about 20 seconds on my G5 to load when
startups are included but only 5 seconds with '-vanilla'.
If you get XEmacs running, try the following commands in an interactive
Lisp buffer:
(system-name)^J
(display-device nil)^J
Consider compiling your own 21.5 (which includes multilanguage support
and utf).
GNU-Emacs startup files can interfere with XEmacs startup and cause
difficult to diagnose problems. But since you had a working system
earlier, that is probably not the problem. Also, if you have efs or
other network file system editing software auto loading, there could be
a problem with its not finding a node. For a related example, the
package system will hang on some computers when connected to some ISPs
because of problems with PASV (or passive ftp) that seem somewhat
intractible. These show up on my Leopard Mac, but they do not show up
on my Xandros machine on the same network. And they only show up on US
mirrors for the repository. Others have reported similar issues.
See http://www.xemacs.org/ for details about the versions and to read
archives of xemacs-beta.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden