Disable the annoying "Loading edmacro..." messages output to TTY?

use...@harkless.org

unread,

Jan 16, 2006, 11:35:14 PM1/16/06

to

I am using SUSE Linux 10.0, and the version of XEmacs included has a
really annoying quirk I have not seen before. Every time you start up
XEmacs, three lines are output to the TTY:

<a blank line>
Loading edmacro...
Loading edmacro...done

These lines appear as output to the terminal prior to the appearance of
the curses display if using 'xemacs -nw', or prior to the appearance of
the X UI if using just 'xemacs'.

Is there a way to disable this? The version of XEmacs is RPM version
21.5.21.20050721, -V output 'XEmacs 21.5 (beta21) "corn"
(+CVS-20050720) [Lucid] (i386-suse-linux, Mule) of Tue Sep 13 2005 on
macintyre'.

--
Dan Harkless
http://harkless.org/dan/

Dan Harkless

unread,

Jan 19, 2006, 1:47:28 AM1/19/06

to

Hmm, no responses. Can anyone at least tell me whether this is
expected behavior for current versions of XEmacs or whether it's
specific to this SUSE version?

David Wright

unread,

Jan 19, 2006, 5:42:43 AM1/19/06

to

Dan Harkless wrote:

Hmm, I just get "command not found" here...

My guess is it is some debug/logging code that got left in that should be
written to a log file, but is getting sent to stdout?

Dave

Torsten Mohr

unread,

Jan 20, 2006, 2:24:28 PM1/20/06

to

Hi,

i also have that problem and i'm interested in a solution. My system is
based on SuSE 9.3.

Best regards,
Torsten.

Joachim Schrod

unread,

Jan 25, 2006, 9:28:35 AM1/25/06

to

This is not the expected behavior. It did not happen with SUSE 9.2 either, but
between 9.2 and 10.0, SUSE upgraded XEmacs from 21.4 to 21.5 which is a vast
difference. It is also not caused by the SUSE-supplied site-start.el, where an
easy solution could probably be found.

If one compiles a new XEmacs oneself, it does not output that message.

A self-compiled XEmacs has the further advantage that XEmacs package updates
start to work. (They don't work on my SUSE 10.0 XEmacs. They worked on my SUSE
9.2 XEmacs.)

A self-compiled XEmacs has the disadvantage that XKBD is not supported by stock
XEmacs and one might need to fiddle with xmodmap to get all keyboard events
working. The particular culprit are shifted function keys and such.

Hope this helps,

Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: jsc...@acm.org
Roedermark, Germany

Dan Harkless

unread,

Feb 2, 2006, 1:44:13 PM2/2/06

to

Yes, thanks for the informative reply, Joachim. BTW, when you compiled
XEmacs from source, I presume you mean using a tarball from xemacs.org,
rather than the source RPM from SUSE? What did you compile, a current
21.5.x version?

Did you use the sumo packages with your self-compiled version? Today I
found that this bug has been reported at
https://bugzilla.novell.com/show_bug.cgi?id=130379 and Mike Fabian from
SUSE says he believes this is an upstream bug in the recent sumo
packages rather than an xemacs bug SUSE introduced.

Joachim Schrod

unread,

Feb 2, 2006, 8:42:34 PM2/2/06

to

Dan Harkless wrote:
>
> Yes, thanks for the informative reply, Joachim. BTW, when you compiled
> XEmacs from source, I presume you mean using a tarball from xemacs.org,
> rather than the source RPM from SUSE? What did you compile, a current
> 21.5.x version?

Yes, the most current beta, 21.5.24.
In fact, first I used 21.5.23 but that had an error that caused VM not to work;
an upgrade to 21.5.24 solved that problem.

I still find some small problems compared to my previous 21.4 installation, but
overall it has proved very stable.

> Did you use the sumo packages with your self-compiled version?

Yes, and later on I updated the packages via the package manager.