From: "Drew Adams" <drew.adams@Oracle.com>
To: <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: FW: loaded minor modes should be added to `mode-line-mode-menu'andOptions menu
Date: Mon, 11 Feb 2008 21:41:02 -0800 [thread overview]
Message-ID: <003301c86d39$dae12210$405a908d@us.oracle.com> (raw)
In-Reply-To: <E1JOmAn-0003Ji-8T@fencepost.gnu.org>
> It would be better for these menus to reflect the user's
> own context: to show which minor modes have been defined,
> whether they were predefined as part of Emacs or not.
> It makes at least as much sense for a user to be able
> to access, by menu, the modes s?he actually uses as modes
> s?he might never use.
>
> That would make the menu of modes so large
> it would be hard to use at all.
Fair enough. But instead of doing such filtering via hard-coding in a
repetitive way, why not let `define-minor-mode', `define-global-minor-mode',
and `define-globalized-minor-mode' do it? Let them accept an argument,
keyword or some other indication (e.g. lighter text prefix, just as we use *
and such for doc strings and for `interactive') to decide whether to add to
a menu.
IOW, on the spectrum from hand- and hard-coded to blindly and automatically
added, pick something systematic but manageable that's midway.
next prev parent reply other threads:[~2008-02-12 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 19:40 FW: loaded minor modes should be added to `mode-line-mode-menu' andOptions menu Drew Adams
2008-02-12 3:51 ` Richard Stallman
2008-02-12 5:41 ` Drew Adams [this message]
2008-02-12 17:44 ` FW: loaded minor modes should be added to `mode-line-mode-menu'andOptions menu Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003301c86d39$dae12210$405a908d@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).