all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 27424@debbugs.gnu.org
Subject: bug#27424: 24.5; [PATCH] commands `apropos-local-variable', `apropos-local-value'
Date: Sat, 22 Jul 2017 17:11:43 +0300	[thread overview]
Message-ID: <83o9sc8stc.fsf@gnu.org> (raw)
In-Reply-To: <1610052b-f79c-485d-93e7-cc1d97961a26@default> (message from Drew Adams on Sat, 22 Jul 2017 06:59:05 -0700 (PDT))

> Date: Sat, 22 Jul 2017 06:59:05 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 27424@debbugs.gnu.org
> 
> > Could you please add corresponding changes for the
> > documentation: the Emacs manual and NEWS?  I will then install all of
> > that.
> 
> You will need to guide me for the latter

Sure, just tell what guidance you need.

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.

> and I don't think
> I want to get involved with the former (texinfo).  For the
> former, if you guide me I can propose text/wording, in case
> that helps.

Providing text is good enough, thanks.





  reply	other threads:[~2017-07-22 14:11 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>
2017-07-22 13:59   ` bug#27424: 24.5; [PATCH] commands `apropos-local-variable', `apropos-local-value' Drew Adams
2017-07-22 14:11     ` Eli Zaretskii [this message]
     [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
2017-07-28  7:49         ` 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=83o9sc8stc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27424@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.