all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Stefan Kangas <stefan@marxist.se>
Cc: "400@debbugs.gnu.org" <400@debbugs.gnu.org>
Subject: bug#400: [External] : Re: bug#400: 23.0.60; C-h v should pick up lispified name in Customize
Date: Fri, 22 Oct 2021 17:13:19 +0000	[thread overview]
Message-ID: <SJ0PR10MB54889FBB8A3094D223E8350EF3809@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87sfwtdtfd.fsf@gnus.org>

> > Right.  We should probably add in more navigation commands in that
> > buffer as well.  "n" and "p" are already bound to `widget-forward',
> but
> > they would have been perfect candidates for a "go to next item"
> command.
> > Now they just give the same clunky behavior as with TAB.
> 
> Yeah, that sounds good -- duplicating the widget movements on the
> non-standard `n'/`p' bindings is confusing, anyway.
> 
> >> So adding more buttons doesn't make things a lot worse.  :-)
> >
> > I guess we could try it and see.
> 
> Yup.

1. Please, navigation is not what _this_ bug report
   is about.  Please discuss navigation possibilities
   elsewhere, and take care of them there.

2. Wrt that navigation discussion (add this to that
   new discussion elsewhere, when you start it):

   There are other keys used for navigation, which
   could be to move among different kinds of things
   (e.g. Customize entries: options, faces in a group).
   Dired uses `>', `<' for one kind of movement, and
   `C-M-n', `C-M-p' for another (in addition to `n',
   `p', for a third.

But please do respect #1.  This bug thread is not the
place to introduce miscellaneous possible Customize
enhancements or other Customize bugs.





  reply	other threads:[~2021-10-22 17:13 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                 ` Drew Adams [this message]
2021-10-21  4:26         ` bug#400: [External] : " 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB54889FBB8A3094D223E8350EF3809@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=400@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.