all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27424@debbugs.gnu.org
Subject: bug#27424: 24.5; [PATCH] commands `apropos-local-variable', `apropos-local-value'
Date: Sat, 22 Jul 2017 16:29:13 -0700 (PDT)	[thread overview]
Message-ID: <a86d199b-4b4b-4bdb-bf17-1909f0926963@default> (raw)
In-Reply-To: <<83o9sc8stc.fsf@gnu.org>>

> In general, NEWS entries for new commands just need to name the
> commands, and optionally say a sentence about what they do.  The idea
> is that the details will be picked up from the doc strings.

For NEWS:

New commands `apropos-local-variable' and `apropos-local-value,
which are buffer-local versions of `apropos-variable' and
`apropos-value'.  They show buffer-local variables who names
and values, respectively, match a given pattern.

For the Emacs manual, node `Apropos':

`M-x apropos-local-variable'
     Search for buffer-local variables whose names match
     the specified pattern.

`M-x apropos-local-value'
     Search for buffer-local variables whose values match
     the specified pattern.





       reply	other threads:[~2017-07-22 23:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<5d980f35-f43a-4968-8f59-d86acb06cca1@default>
     [not found] ` <<<83d18saoi4.fsf@gnu.org>
     [not found]   ` <<1610052b-f79c-485d-93e7-cc1d97961a26@default>
     [not found]     ` <<83o9sc8stc.fsf@gnu.org>
2017-07-22 23:29       ` Drew Adams [this message]
2017-07-28  7:49         ` bug#27424: 24.5; [PATCH] commands `apropos-local-variable', `apropos-local-value' Eli Zaretskii
     [not found] <<5d980f35-f43a-4968-8f59-d86acb06cca1@default>
     [not found] ` <<83d18saoi4.fsf@gnu.org>
2017-07-22 13:59   ` Drew Adams
2017-07-22 14:11     ` Eli Zaretskii
2017-06-18 21:33 Drew Adams
2017-07-22  8:01 ` Eli Zaretskii

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=a86d199b-4b4b-4bdb-bf17-1909f0926963@default \
    --to=drew.adams@oracle.com \
    --cc=27424@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.