From: Robert Pluim <rpluim@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org, Juri Linkov <juri@linkov.net>
Subject: Re: Horrible File menu
Date: Mon, 31 Jan 2022 11:38:25 +0100 [thread overview]
Message-ID: <87k0egchr2.fsf@gmail.com> (raw)
In-Reply-To: <87o83sdyqr.fsf@yahoo.com> (Po Lu's message of "Mon, 31 Jan 2022 17:46:04 +0800")
>>>>> On Mon, 31 Jan 2022 17:46:04 +0800, Po Lu <luangruo@yahoo.com> said:
Po> Juri Linkov <juri@linkov.net> writes:
>>>> So by default, even when you don't use frames, these items take much
>>>> space on the File menu:
>>>>
>>>> (disabled) Delete frame
>>>> (disabled) Undelete frame
>>>> [X] Allow Undeleting Frames
>>>
>>> "Delete Frame" is not a recent development. It's been there for a long
>>> time, along with New Frame and the various monitor and multi-tty related
>>> variants of that.
>> To make the menu shorter, does it make sense to hide "Delete frame"?
Po> It does not.
If anything needs deleting from that menu, itʼs 'Make frame on
display'. Thatʼs useful to a vanishingly small percentage of users,
and I doubt they'd use the menu to do it.
>> Especially the users who don't use frames would benefit from this. Or
>> at least not to show the disabled "Undelete frame" until "Delete
>> frame" changes to the enabled state.
Po> How does someone "not use frames"? I thought that stopped being
Po> possible with Emacs 19, when every X window became a frame.
Some people only use a single frame. Some people use multiple frames
on tty. Tomayto, tomaato.
>> What do you think about another variant to make the menu shorter: to
>> move frame items to the File>Frame submenu?
Po> That I can agree with (but please let Eli and some other regulars
Po> comment first), thanks.
Fine by me: I have the menus turned off :-)
FWIW, Iʼd vote to have undelete frame enabled by default, which would
obviate the need for the menu item. Having to turn on a mode to get
'undo' behaviour just seems unfriendly.
Robert
--
next prev parent reply other threads:[~2022-01-31 10:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 20:59 Horrible File menu Juri Linkov
2022-01-30 21:45 ` Lars Ingebrigtsen
2022-01-31 1:01 ` Phil Sainty
2022-01-31 0:48 ` Po Lu
2022-01-31 8:13 ` Juri Linkov
2022-01-31 9:46 ` Po Lu
2022-01-31 10:38 ` Robert Pluim [this message]
2022-01-31 11:08 ` Po Lu
2022-01-31 13:04 ` Stefan Monnier
2022-01-31 13:16 ` Robert Pluim
2022-01-31 13:16 ` Po Lu
2022-01-31 13:36 ` Robert Pluim
2022-01-31 13:48 ` Po Lu
2022-01-31 15:01 ` Robert Pluim
2022-02-01 1:03 ` Po Lu
2022-02-01 8:56 ` Robert Pluim
2022-02-01 10:20 ` Po Lu
2022-01-31 12:37 ` Eli Zaretskii
2022-01-31 14:45 ` [External] : " Drew Adams
2022-02-01 21:27 ` Rudolf Adamkovič
2022-02-02 1:16 ` chad
2022-02-02 4:45 ` Po Lu
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=87k0egchr2.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=luangruo@yahoo.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 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.