* bug#7303: Suggestion: Move minor mode menus to one common top-level submenu
@ 2010-10-29 19:54 Lennart Borgman
2010-10-29 21:20 ` bug#7303: Suggestion: Move minor mode menus to one common top-levelsubmenu Drew Adams
0 siblings, 1 reply; 6+ messages in thread
From: Lennart Borgman @ 2010-10-29 19:54 UTC (permalink / raw)
To: 7303
I saw Jonas Bernoulli posted a similar question (for the modeline) here:
http://www.emacswiki.org/emacs/ModeLineMinorModeMenu
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7303: Suggestion: Move minor mode menus to one common top-levelsubmenu
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 ` Drew Adams
2010-10-29 21:53 ` Lennart Borgman
2020-11-19 4:36 ` Stefan Kangas
0 siblings, 2 replies; 6+ messages in thread
From: Drew Adams @ 2010-10-29 21:20 UTC (permalink / raw)
To: 'Lennart Borgman', 7303
> 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.
However, some general mechanism to deal with an overly wide menu bar or mode
line could be useful, especially if optional.
Currently, the menu bar and mode line are treated differently when their content
is too wide for the frame and window, respectively. The menu bar content is
wrapped. The mode line content is truncated at the right.
* This might be useful for the mode line:
Whenever stuff cannot be displayed and will be truncated, gather it and make it
all accessible by a link in the mode line. Obviously, the link itself takes
some space, but it could be short (e.g. `...').
* Something similar would be helpful for the menu bar:
Have a user option that specifies a max width. If nil, then the current behavior
would be followed (just wrap). Otherwise, if the menu-bar content is wider than
the option value, then the behavior would be similar to the mode-line behavior
suggested above: Gather all menus that would be wrapped into a final menu `...'
instead.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7303: Suggestion: Move minor mode menus to one common top-levelsubmenu
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
2020-11-19 4:36 ` Stefan Kangas
1 sibling, 0 replies; 6+ messages in thread
From: Lennart Borgman @ 2010-10-29 21:53 UTC (permalink / raw)
To: Drew Adams; +Cc: 7303
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).
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7303: Suggestion: Move minor mode menus to one common top-levelsubmenu
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
@ 2020-11-19 4:36 ` Stefan Kangas
2020-11-24 6:41 ` Lars Ingebrigtsen
1 sibling, 1 reply; 6+ messages in thread
From: Stefan Kangas @ 2020-11-19 4:36 UTC (permalink / raw)
To: Drew Adams; +Cc: 7303, Lennart Borgman
"Drew Adams" <drew.adams@oracle.com> writes:
>> 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.
I tend to agree. Does anyone object to closing this as wontfix?
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-11-24 16:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2020-11-19 4:36 ` Stefan Kangas
2020-11-24 6:41 ` Lars Ingebrigtsen
2020-11-24 16:19 ` Stefan Kangas
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).