all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 12924@debbugs.gnu.org
Subject: bug#12924: 24.3.50; Request: Provide a command to show the node in the manual where a variable is described
Date: Tue, 01 Jun 2021 09:07:33 +0200	[thread overview]
Message-ID: <87h7iidpvu.fsf@gnus.org> (raw)
In-Reply-To: <CAH8Pv0j96CALrC_d_egX-K+DdcuTQG_aRvQcKdx8YRn9K0hoFQ@mail.gmail.com> (Dani Moncayo's message of "Sun, 18 Nov 2012 15:19:36 +0100")

Dani Moncayo <dmoncayo@gmail.com> writes:

> Provide a command `Info-goto-emacs-variable-node', bound to `C-h V',
> that be to variables as `Info-goto-emacs-command-node' (bound to `C-h
> F') is to commands.
>
> That is: `C-h V search-whitespace-regexp' would take me to the info
> node "(emacs) Special Isearch", where this variable is explained.
>
> This would be a useful feature, and would fit quite well in the
> current scheme of help commands (`C-h f/F' for commands; `C-h k/K' for
> keys; and now `C-h v/V' for variables).

(I'm going through old bug reports that unfortunately got little response at
the time.)

`C-h V' is taken by `describe-variable' these days, and there's also
`C-h S' to lookup a symbol in the manuals.  I think that adding a new
command to lookup variables, too, would probably be overkill, since
there's not that much overlap between user variables and other symbols
in the manual, usually.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-06-01  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 14:19 bug#12924: 24.3.50; Request: Provide a command to show the node in the manual where a variable is described Dani Moncayo
2012-11-18 16:04 ` bug#12924: 24.3.50; Request: Provide a command to show the node in the manual where avariable " Drew Adams
2021-06-01  7:07 ` Lars Ingebrigtsen [this message]

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=87h7iidpvu.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=12924@debbugs.gnu.org \
    --cc=dmoncayo@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.