From: Miles Bader <miles@gnu.org>
Subject: problems with easy-menu-add on --without-x emacs
Date: 10 Apr 2004 12:20:20 +0900 [thread overview]
Message-ID: <877jwocydn.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
I notice several cases where things fail on an emacs compiled without X
support, because they call `easy-menu-add', and it calls `x-popup-menu'
which isn't defined when X support is disabled. I don't recall such
failures the last time I tried to make a no-X emacs, so maybe something
has changed recently.
Specifically:
(1) If I try to compose mail with `mail-user-agent' set to
message-user-agent, I get the following backtrace:
Debugger entered--Lisp error: (void-function x-popup-menu)
x-popup-menu(nil (keymap "Message" (sort\ headers menu-item "Sort ...
easy-menu-add((keymap "Message" (sort\ headers menu-item "Sort He ...
message-mode()
message-pop-to-buffer("*mail*")
message-mail(nil nil nil nil nil nil nil)
compose-mail(nil nil nil nil)
* call-interactively(compose-mail)
I'd think `easy-menu-add' should work regardless of X or no X,
but it indeed calls x-popup-menu.
(2) _Compiling_ `progmodes/ada-prj.el' fails, because it does (require
'ada-mode), and progmodes/ada-mode.el contains a top-level call to
(ada-create-menu)
and `ada-create-menu' calls easy-menu-add.
Oddly, `easy-menu-add' contains the comment that "This is a nop on
emacs", but obviously it isn't!
Thanks,
-Miles
--
Love is a snowmobile racing across the tundra. Suddenly it flips over,
pinning you underneath. At night the ice weasels come. --Nietzsche
next reply other threads:[~2004-04-10 3:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 3:20 Miles Bader [this message]
2004-04-10 15:33 ` problems with easy-menu-add on --without-x emacs Stefan Monnier
2004-04-12 3:52 ` Richard Stallman
2004-04-12 4:41 ` Stefan Monnier
2004-04-13 17:44 ` Richard Stallman
2004-04-13 18:14 ` Stefan Monnier
2004-04-14 22:53 ` Richard Stallman
2004-04-14 23:25 ` David Kastrup
2004-04-16 18:08 ` Richard Stallman
2004-04-16 18:27 ` David Kastrup
2004-04-17 19:46 ` Richard Stallman
2004-04-14 0:18 ` Alex Schroeder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877jwocydn.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.