unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Rudolf Adamkovič" <salutis@me.com>
To: Juri Linkov <juri@linkov.net>, emacs-devel@gnu.org
Subject: Re: Horrible File menu
Date: Tue, 01 Feb 2022 22:27:09 +0100	[thread overview]
Message-ID: <m21r0m9t1u.fsf@me.com> (raw)
In-Reply-To: <864k5ldj6z.fsf@mail.linkov.net>

Juri Linkov <juri@linkov.net> writes:

> where the last item with the checkbox looks very ugly.

It look great on macOS, FYI.

> 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 like the idea of sub-menus.

> Why not to show the Undelete frame item only when at least one frame
> was deleted?

101 "classical" UX, from back when research guided the field instead of
fashion, teaches us that hiding menu items like that leads to confusion.
All menu items should live in one place.  Always.  If not applicable, we
can disable them.  Just because we can make everything dynamic, it does
not mean we should, IMO.

> And why require enabling this feature before the deleted
> frame can be undeleted?  Are a few kilobytes of memory used by the
> deleted frame data a real concern?

I find this strange as well.

Rudy
-- 
"Programming reliably -- must be an activity of an undeniably
mathematical nature […] You see, mathematics is about thinking, and
doing mathematics is always trying to think as well as possible."
-- Edsger W. Dijkstra, 1981

Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava
Slovakia



  parent reply	other threads:[~2022-02-01 21:27 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
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č [this message]
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=m21r0m9t1u.fsf@me.com \
    --to=salutis@me.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).