unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15632@debbugs.gnu.org
Subject: bug#15632: 24.3.50; doc string of `replace-match-maybe-edit'
Date: Fri, 07 Feb 2014 19:55:55 -0800	[thread overview]
Message-ID: <8738ju8dh0.fsf@building.gnus.org> (raw)
In-Reply-To: <7daeb745-0021-4380-a5de-1f74eed1d0c6@default> (Drew Adams's message of "Wed, 16 Oct 2013 08:48:11 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> 1. It is not true that NEWTEXT is "just passed on".  If `\?' is present
> then it is updated to the result of editing.  It is that possibly edited
> result that is then passed to `replace-match'.
>
> 2. Even though the first line suggests that this function will use
> `replace-match' as a helper, this part of the doc string is unclear (and
> false - see #1):
>
>   "NEWTEXT, FIXEDCASE, LITERAL are just passed on."
>
> The point of saying that an arg is "passed on" is to refer the reader to
> the function where it is actually used and documented.  Rather than
> documenting here what the parameter does, we send you to the doc of
> another function, where the parameter is described fully.
>
> The text should say something like this:
>
>   "FIXEDCASE, LITERAL are passed to `replace-match' (which see).  After
>   possibly editing it, NEWTEXT is also passed to `replace-match'.

Fixed on trunk.

> 3. The next-to-last sentence is unclear.  NOEDIT is *always* "passed
> in".  The doc should say that the return value is nil iff NOEDIT is nil
> or NEWTEXT was edited.

This seems to have been edited already.

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





      reply	other threads:[~2014-02-08  3:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 15:48 bug#15632: 24.3.50; doc string of `replace-match-maybe-edit' Drew Adams
2014-02-08  3:55 ` 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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=8738ju8dh0.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=15632@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).