Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

Using gentoo 1.4 rc3 both on a Athlon XP and a Pentium4 Xeon 
CFLAGS = -O3 -march=athlon-xp (-march=pentium3 for the Xeon) -fomit-frame-pointer 
 
The command menu from AucTeX 10.0g won't open in Emacs 21.3 (neither in 21.2)

Works fine here with app-emacs/auctex-10.0g and app-editors/emacs-21.3.

Are there any error messages in the Messages-buffer?
Check your load-path (e.g. C-h v <return> load-path <return>). It should contain
/usr/share/emacs/site-lisp/ and /usr/share/emacs/site-lisp/auctex.

Has this ever been resolved?

I have the same problem and it is unrelated to auctex. I tried 
emerge =app-emacs/auctex-10.0g and that didn't work either.
Manual installation of tarball also failed.

Manual installation of tarball in redhat 9.0 (booted from different partition) works perfectly.

What could this error be due to?

Recompiled emacs with userflag Xaw3d set and it works...

Same problem with gentoo on PPC. On starting emacs with auctex mode, it
reports:

Warning: Actions not found: reset, set, notify, unset
Warning: Actions not found: reset, set, notify, unset

Modifying the ebuild file of auctex so that the ebuild demands emacs compiled
with Xaw3d support should solve this. 

Meanwhile... just recompile emacs with userflag -Xaw3d set.It worked for
me.

Thanks for the comment. I confirmed the problem and added a notice for
users to enable USE="Xaw3d" if it is not set.

We are having this same problem (Command menu does not work).  Note that the
other auctex menus do work.

Just to be sure about the Xaw3d thing, I just rebuilt emacs (21.3.1-r3) with

USE="Xaw3d" emerge emacs

and reinstalled auctex (11.14) with

ACCEPT_KEYWORDS="~sparc" emerge --ask app-emacs/auctex

and still the same problem. Any ideas?

Ok, I figured out a workaround.  The gentoo default USE flags include "motif"
which appears to override "Xaw3d".  Building emacs with

USE="Xaw3d -motif" emerge emacs

fixes the problem on our system.

I see... I reversed motif and Xaw3d USE flag order because if a user
sets non-default Xaw3d USE flag I guess he/she does not intend to get
default motif interface.

The problem with the Command menu not working is related to an obscure conflict
with KDE. This is explained in detail at
http://groups-beta.google.com/group/comp.windows.x.motif/browse_frm/thread/c20cc6d768acd666

The way I "fixed" the problem is to change the following line in tex.el from:
(defconst TeX-command-menu-name "Command"
to:
(defconst TeX-command-menu-name "Commands"

Created an attachment (id=51225) [details]
Proposed patch for .../auctex/tex.el

Apply this patch to /usr/share/emacs/site-lisp/auctex/tex.el.
It changes the name of the menu from 'Command' to Commands' this fixes an
obscure conflict with KDE as pointed out in my earlier post (#10).

When I emerged emacs 21.4 and auctex 11.54, I noticed two problems that I
initially thought were unrelated: (1) the "command" menu bug described here and
(2) a "find file dialog box that was wider than the screen space, forcing me to
drag it across the screen to view the list of files.

After I recompiled with the USE flag suggested by Brett Presnell, both problems
went away. Now instead of a dialog box, emacs prompts me to enter the directory
path in the lowermost buffer. I'm new to emacs (and to gentoo), so I can't say
if that's the proper behavior or not. In any event, I prefer it to the oversize
dialog box.

My experience leads me to think that this bug is more wide-ranging than the
auctex menu problem.

Just a follow-up to my last post. Today I did an "emerge --update world." My
emacs was recompiled after a newer version of motif was installed, and the menu
problem is indeed fixed. Nonetheless, I think I will recompile with the
USE=Xaw3d flag for two reasons -- the pulldown menus appear with a mouse-over,
whereas with the motif menu I have to tap on my touchpad and secondly, I prefer
not to have the motif "find file" dialog box.