From: Drew Adams <drew.adams@oracle.com>
To: 39848@debbugs.gnu.org
Subject: bug#39848: 26.3; Provide better help for menu-bar, e.g., Options > Line Wrapping in This Buffer
Date: Sat, 29 Feb 2020 16:46:39 -0800 (PST) [thread overview]
Message-ID: <62a1ef4d-e9fa-4757-977d-dcb9d3e4aa52@default> (raw)
emacs -Q
C-h k
As one example, choose from menu-bar: Options > Line Wrapping in This
Buffer > Wrap at Window Edge
Buffer *Help* shows this:
<menu-bar> <options> <line-wrapping> <window-wrap> runs the command #[nil "\b\203\b\0\300\303!\210\304
\205\0\305\306!\207" [visual-line-mode word-wrap truncate-lines 0
nil toggle-truncate-lines -1] 2 nil nil] (found in global-map), which
is an interactive compiled Lisp function.
It is bound to <menu-bar> <options> <line-wrapping> <window-wrap>.
(anonymous)
Not documented.
That's nearly useless. It doesn't take advantage of Emacs or Lisp.
1. Please provide named commands for all Options menu choices.
2. Please try to have *Help* point to the file that defines those
commands.
3. Please keep byte-compiler gobbledygook out of Emacs help.
Consider this reasonable question, as one point of departure:
https://stackoverflow.com/q/60468217/729907
Yes, there's no satisfactory one-word answer to that user's question,
but s?he should at least be able to more easily track down the code that
provides the option behavior for the current buffer.
As it is now, it's not even obvious that the code is in menu-bar.el.
In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.18362
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2020-03-01 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 0:46 Drew Adams [this message]
2020-03-01 3:41 ` bug#39848: 26.3; Provide better help for menu-bar, e.g., Options > Line Wrapping in This Buffer Eli Zaretskii
2020-03-01 4:04 ` Stefan Kangas
2020-03-01 17:34 ` Drew Adams
2020-03-01 17:53 ` Eli Zaretskii
[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 ` Drew Adams
2020-03-02 8:00 ` 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=62a1ef4d-e9fa-4757-977d-dcb9d3e4aa52@default \
--to=drew.adams@oracle.com \
--cc=39848@debbugs.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).