From: Lennart Borgman <lennart.borgman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 7303@debbugs.gnu.org
Subject: bug#7303: Suggestion: Move minor mode menus to one common top-levelsubmenu
Date: Fri, 29 Oct 2010 23:53:42 +0200 [thread overview]
Message-ID: <AANLkTikOono49WpMt0d=DJEifBzcQt7WvZgF2BurE242@mail.gmail.com> (raw)
In-Reply-To: <2ACD2D1AF0004AD38E4A3C9C6CD4815A@us.oracle.com>
On Fri, Oct 29, 2010 at 11:20 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> I suggest we move all minor mode to one common top-level submenu for
>> two reasons:
>>
>> - It takes less space in the menu bar.
>> - The distinction between minor and major modes becomes more clear.
>>
>> This submenu could also preferably be ordered by local and
>> global minor modes.
>
> IMO, that's not the right solution.
>
> We should leave it up to users and libraries to decide where to put menus. This
> kind of choice depends on the context, and sometimes on user preference. The
> devil is in the details.
Maybe there should be options, yes. But I think putting the minor
modes under one submenu by defaults would be a good start.
However I doubt that something will happen. Menu changes seems to have
very low priority (or we just can't agree).
next prev parent reply other threads:[~2010-10-29 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 19:54 bug#7303: Suggestion: Move minor mode menus to one common top-level submenu Lennart Borgman
2010-10-29 21:20 ` bug#7303: Suggestion: Move minor mode menus to one common top-levelsubmenu Drew Adams
2010-10-29 21:53 ` Lennart Borgman [this message]
2020-11-19 4:36 ` Stefan Kangas
2020-11-24 6:41 ` Lars Ingebrigtsen
2020-11-24 16:19 ` Stefan Kangas
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='AANLkTikOono49WpMt0d=DJEifBzcQt7WvZgF2BurE242@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=7303@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).