unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Horrible File menu
Date: Mon, 31 Jan 2022 10:13:04 +0200	[thread overview]
Message-ID: <86r18os4ng.fsf@mail.linkov.net> (raw)
In-Reply-To: <87a6fcg27w.fsf@yahoo.com> (Po Lu's message of "Mon, 31 Jan 2022 08:48:03 +0800")

>> 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"?
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.

>> These useless items are pushing off-screen other useful items
>> that are below them such as the Quit item and the Print submenu
>> with Print items that were originally on the File menu but were
>> moved to the submenu from the overgrowing menu.
>
> I find it hard to believe that two extra items "push offscreen" such
> important items as the Print menu and Quit.

What do you think about another variant to make the menu shorter:
to move frame items to the File>Frame submenu?

>> I don't understand what obstacle prevents from making this menu
>> more user-friendly?
>
> It already is user friendly.

No, it's not.  It requires the user to select the item "Allow Undeleting Frames"
on the "File" menu, then to select "Save Options" on the "Options" menu
to be able to occasionally undelete an accidentally deleted frame.

>> Are a few kilobytes of memory used by the deleted frame data a real
>> concern?
>
> Yes, which was discussed in detail in the discussion in the bug report.

This concern was recently addressed, this is why the discussion is reopened.



  reply	other threads:[~2022-01-31  8:13 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 [this message]
2022-01-31  9:46     ` Po Lu
2022-01-31 10:38       ` Robert Pluim
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

  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=86r18os4ng.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --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 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).