From: David Kastrup <dak@gnu.org>
Cc: Gnus <ding@gnus.org>, emacs-devel@gnu.org
Subject: Re: No "Edit" menu-item in "Gnus"
Date: Wed, 16 Aug 2006 00:22:15 +0200 [thread overview]
Message-ID: <858xlp8wrs.fsf@lola.goethe.zz> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMOEIKCKAA.drew.adams@oracle.com> (Drew Adams's message of "Tue, 15 Aug 2006 15:12:34 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> >> There are several items on that menu that are useful when
> >> reading mail and news.
> >
> > Which specific items do you have in mind? I'd guess that at least the
> > most important "Search" and "Go To" items have Gnus equivalents.
>
> "Select All", "Copy", "Go To > Find Tag", "Beginning of buffer" ...
> (If those are useless in Gnus, then they are useless in everywhere)
> and:
> "Text Properties > Describe Properties"
>
> In general, I'd say:
>
> 1. Edit shouldn't be removed from the menu-bar for the sole reason
> of saving menu-bar space and because the buffer might be
> unmodifiable.
Menus are for frequently used commands. If in a particular situation
the entries of a menu are of rare use, and others are more important,
omitting the rarely used menu might make sense.
> If there is a problem with menu-bar space in some context, then some
> other solution should be adopted. One solution is to have a
> pull-down menu (e.g. "More", "...", or a triangle arrow) that
> combines some other menus as submenus. Another solution is to let
> the menu-bar extend over multiple lines when necessary - that's the
> current default, and it's OK too.
>
> It's silly to assume a fixed frame width, in any case, and to base
> decisions of which menus to include on that width. I shrink-fit
> frames to fit their buffers, for example, so they have different
> widths. Other people always maximize their frames, or always use
> some fixed width that's different from the default.
The menu bar should fit on an 80-column text tty. That is a hard
limit that can't be come by by changing font sizes or resizing
windows.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-08-15 22:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 8:01 No "Edit" menu-item in "Gnus" Kim F. Storm
2006-08-14 8:16 ` David Kastrup
2006-08-14 9:02 ` Jan Djärv
2006-08-15 12:40 ` Richard Stallman
2006-08-14 19:25 ` Reiner Steib
2006-08-15 20:54 ` Kim F. Storm
2006-08-15 22:12 ` Drew Adams
2006-08-15 22:22 ` David Kastrup [this message]
2006-08-15 23:37 ` Drew Adams
2006-08-16 3:24 ` Eli Zaretskii
2006-08-15 21:28 ` Jason Rumney
2006-08-16 6:24 ` Jan Djärv
2006-08-16 6:29 ` David Kastrup
2006-08-16 6:34 ` Jan Djärv
2006-08-16 7:16 ` Drew Adams
2006-08-16 19:27 ` Richard Stallman
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=858xlp8wrs.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
/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).