all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
	"Juri Linkov" <juri@linkov.net>
Cc: Dan Jacobson <jidanni@jidanni.org>,
	"70212@debbugs.gnu.org" <70212@debbugs.gnu.org>
Subject: bug#70212: Customize Group buffer: add button to reveal underlying variable names
Date: Fri, 5 Apr 2024 17:13:27 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488815D501A6273E8E01373F3032@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87h6gfpxhe.fsf@gmail.com>

> > You can read the related discussion at bug#41905.
> 
> And bug#400 (referenced in bug#41905).

I'd forgotten about that one; thankx.  The other
two I mentioned were just closed as "won't fix".
That one has hung on as "wishlist".

> FWIW I agree making Custom > Help navigation more seamless would be
> neat; one may first be interested in browsing options via Customize's
> group hierarchies, then jump to a Help buffer to seek details about a
> specific variables (:version, estimated introductory release) or use
> help-mode-map commands (e.g. 'i', 's').

Yup.  More seamless - less seamful - would help. ;-)

  reply	other threads:[~2024-04-05 17:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  8:45 bug#70212: Customize Group buffer: add button to reveal underlying variable names Dan Jacobson
2024-04-05 12:27 ` Eli Zaretskii
2024-04-05 16:32   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-05 16:13 ` Juri Linkov
2024-04-05 16:47   ` Kévin Le Gouguec
2024-04-05 17:13     ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-04-06  6:40       ` Dan Jacobson
2024-04-14 16:27 ` Howard Melman

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=SJ0PR10MB5488815D501A6273E8E01373F3032@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=70212@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=jidanni@jidanni.org \
    --cc=juri@linkov.net \
    --cc=kevin.legouguec@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 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.