From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Howard Melman <hmelman@gmail.com>,
"400@debbugs.gnu.org" <400@debbugs.gnu.org>
Subject: bug#400: [External] : bug#400: 23.0.60; C-h v should pick up lispified name in Customize
Date: Sat, 23 Oct 2021 21:25:53 +0300 [thread overview]
Message-ID: <87tuh7ac0u.fsf@mail.linkov.net> (raw)
In-Reply-To: <SJ0PR10MB5488681F3B9A7865AA21A6BFF3809@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Fri, 22 Oct 2021 16:51:50 +0000")
>> but I'm now thinking that something like outline-cycle
>> would be great in any customize buffer. Let S-TAB cycle
>> through the various states of all options at once.
>
> Fine. But:
>
> 1. There should also be a simple visual affordance
> (e.g., button or some indication of a key to hit).
> Customize is also (but not only) for new users,
> who won't necessarily know about such a cycling
> key.
A help text at the beginning should be sufficient.
> 2. Unfortunately, Emacs decided to follow the outside
> convention that S-TAB has the same behavior as TAB,
> except that it cycles backward. This wasn't a good
> idea, IMO, but it was done, so another key would be
> needed for your cycling behavior.
In outline-minor-mode, S-TAB cycles outlines only when point is
on the heading. Otherwise, S-TAB preserves its original binding
to move backward.
next prev parent reply other threads:[~2021-10-23 18:25 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 16:27 bug#400: 23.0.60; C-h v should pick up lispified name in Customize Drew Adams
2008-06-12 21:19 ` martin rudalics
2008-06-12 21:28 ` Drew Adams
2020-09-06 12:26 ` Lars Ingebrigtsen
2020-09-06 14:39 ` Eli Zaretskii
2020-09-06 16:33 ` Kévin Le Gouguec
2021-10-20 21:02 ` Stefan Kangas
2021-10-20 21:27 ` bug#400: [External] : " Drew Adams
2021-10-21 6:37 ` Eli Zaretskii
2021-10-21 16:15 ` Drew Adams
2021-10-21 3:09 ` Lars Ingebrigtsen
2021-10-21 3:35 ` Stefan Kangas
2021-10-21 3:38 ` Lars Ingebrigtsen
2021-10-21 5:01 ` bug#400: [External] : " Drew Adams
2021-10-21 7:40 ` Eli Zaretskii
2021-10-21 16:49 ` Stefan Kangas
2021-10-22 14:29 ` Lars Ingebrigtsen
2021-10-22 17:13 ` bug#400: [External] : " Drew Adams
2021-10-21 4:26 ` Drew Adams
2021-10-21 7:36 ` Eli Zaretskii
2021-10-21 6:31 ` Eli Zaretskii
2021-10-21 15:47 ` Howard Melman
2021-10-21 17:02 ` Eli Zaretskii
2021-10-22 2:36 ` Howard Melman
2021-10-22 6:38 ` Eli Zaretskii
2021-10-22 15:38 ` Howard Melman
2021-10-22 17:22 ` bug#400: [External] : " Drew Adams
2021-10-21 16:34 ` Stefan Kangas
2021-10-21 17:09 ` Eli Zaretskii
2021-10-21 17:50 ` Stefan Kangas
2021-10-21 18:00 ` Eli Zaretskii
2021-10-21 19:45 ` Stefan Kangas
2021-10-22 6:05 ` Eli Zaretskii
2021-10-22 8:12 ` Stefan Kangas
2021-10-22 10:49 ` Eli Zaretskii
2021-10-22 16:56 ` bug#400: [External] : " Drew Adams
2021-10-22 3:30 ` Howard Melman
2021-10-22 16:51 ` bug#400: [External] : " Drew Adams
2021-10-23 18:25 ` Juri Linkov [this message]
2020-09-06 17:06 ` Drew Adams
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=87tuh7ac0u.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=400@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=hmelman@gmail.com \
/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).