From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 39848@debbugs.gnu.org, stefan@marxist.se
Subject: bug#39848: 26.3; Provide better help for menu-bar, e.g., Options > Line Wrapping in This Buffer
Date: Mon, 02 Mar 2020 10:00:01 +0200 [thread overview]
Message-ID: <83imjnyyny.fsf@gnu.org> (raw)
In-Reply-To: <e0e31daf-dde3-4706-a3b8-7c03bb967983@default> (message from Drew Adams on Sun, 1 Mar 2020 13:50:16 -0800 (PST))
> Date: Sun, 1 Mar 2020 13:50:16 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: stefan@marxist.se, 39848@debbugs.gnu.org
>
> > > Command `menu-bar--wrap-long-lines-window-edge'
> > > is precisely the kind of command that a user
> > > might use, either directly or in lisp code.
> >
> > Why would they, when commands like visual-line-mode exist?
>
> Same reason they'd use it from a menu.
Invoking a command from the menu doesn't involve naming the command,
it just involves clicking with the mouse and selecting the menu item.
By contrast, invoking commands by name involves typing that name. And
we already have commands that perform the same operation as this menu
item. So having yet another advertised command which subtly differs
from those we have already (the differences make sense when you invoke
a command from the menu) makes little sense to me.
next prev parent reply other threads:[~2020-03-02 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<62a1ef4d-e9fa-4757-977d-dcb9d3e4aa52@default>
[not found] ` <<834kv8eo7q.fsf@gnu.org>
[not found] ` <<8736as67qh.fsf@stefankangas.se>
[not found] ` <<df8fe907-69c4-4bd3-97fd-58a3ea0b4c72@default>
[not found] ` <<83pndwynak.fsf@gnu.org>
2020-03-01 21:50 ` bug#39848: 26.3; Provide better help for menu-bar, e.g., Options > Line Wrapping in This Buffer Drew Adams
2020-03-02 8:00 ` Eli Zaretskii [this message]
2020-03-01 0:46 Drew Adams
2020-03-01 3:41 ` Eli Zaretskii
2020-03-01 4:04 ` Stefan Kangas
2020-03-01 17:34 ` Drew Adams
2020-03-01 17:53 ` Eli Zaretskii
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=83imjnyyny.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39848@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=stefan@marxist.se \
/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).