From: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70413@debbugs.gnu.org
Subject: bug#70413: 30.0.50; FR: skip inactive widgets when tabbing
Date: Wed, 17 Apr 2024 19:36:04 +0200 [thread overview]
Message-ID: <877cgv99iz.fsf@gmx.net> (raw)
In-Reply-To: <86frvkgfly.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 17 Apr 2024 18:42:49 +0300")
On Wed, 17 Apr 2024 18:42:49 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: 70413@debbugs.gnu.org
>> Date: Wed, 17 Apr 2024 15:57:56 +0200
>>
>> On Wed, 17 Apr 2024 15:04:34 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> >> +@defopt widget-skip-inactive
>> >> +If non-@code{nil}, navigating between widgets by @kbd{M-@key{TAB}}
>> > ^^^^^^^^^^^^^^^^^
>>
>> Oops, that was copy-pasta; thanks for catching it.
>>
>> > This should probably be @kbd{key{TAB}}.
>>
>> Or rather @key{TAB}, right? That's what's used earlier in the Widget
>> manual and IIUC is what (info "(texinfo) @key") recommends.
>
> No, @kbd{@key{TAB}} is correct when you are talking about user typing
> something (as opposed to talking about the key TAB).
>
> Texinfo explicitly tells you that @key is for naming a key, not for
> describing user input.
Ah, ok. I guess I misunderstood that, and also I misinterpreted the use
of @key{TAB} in (info "(widget) Widgets and the Buffer") that I referred
to above: it is in a table that begins with @table @kbd, so the effect
is that of @kbd{@key{TAB}}. (But I do think there are several typos or
incorrect markup in that node and possibly elsewhere in the Widget
manual; but I'll make a separate bug report about that.)
>> If non-@code{nil}, skip over inactive widgets when using @key{TAB}
>> (@code{widget-forward}) or @kbd{S-@key{TAB}} (@code{widget-backward},
>> also bound to @kbd{M-@key{TAB}}) to navigate between widgets.
>>
>> Is this formulation acceptable?
>
> Yes, thanks.
Thanks, I've pushed the changes to master as commit 91333dacfa1.
Steve Berman
next prev parent reply other threads:[~2024-04-17 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 9:20 bug#70413: 30.0.50; FR: skip inactive widgets when tabbing Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 12:53 ` Eli Zaretskii
2024-04-16 21:56 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 22:04 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 12:04 ` Eli Zaretskii
2024-04-17 13:57 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 15:42 ` Eli Zaretskii
2024-04-17 17:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-04-17 17:37 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=877cgv99iz.fsf@gmx.net \
--to=bug-gnu-emacs@gnu.org \
--cc=70413@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.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).