unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-26 aecbbd5: * src/fns.c (Fmapconcat): Doc fix. (Bug#35710)
Date: Mon, 10 Jun 2019 18:33:11 +0300	[thread overview]
Message-ID: <838su9bglk.fsf@gnu.org> (raw)
In-Reply-To: <m2imtd20sc.fsf@gmail.com> (message from Robert Pluim on Mon, 10 Jun 2019 12:27:15 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Mon, 10 Jun 2019 12:27:15 +0200
> 
> Eli, those whitespace changes look a little suspicious to me, they
> result in a docstring like this:
> 
>     Apply FUNCTION to each element of SEQUENCE, and concat the results as strings.
>     In between each pair of results, stick in SEPARATOR.  Thus, " " as
>       SEPARATOR results in spaces between the values returned by FUNCTION.
>     SEQUENCE may be a list, a vector, a bool-vector, or a string.
>     SEPARATOR must be a string.
>     FUNCTION must be a function of one argument, and must return a value
>       that is a sequence of characters: either a string, or a vector or
>       list of numbers that are valid character codepoints.

Why is this suspicious?  Text has been indented to allow easily
finding the beginning of the description of each argument.  We do that
in many other places.



      parent reply	other threads:[~2019-06-10 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190607130041.24281.64279@vcs0.savannah.gnu.org>
     [not found] ` <20190607130043.327B520536@vcs0.savannah.gnu.org>
2019-06-10 10:27   ` emacs-26 aecbbd5: * src/fns.c (Fmapconcat): Doc fix. (Bug#35710) Robert Pluim
2019-06-10 13:46     ` Juanma Barranquero
2019-06-10 14:17       ` Robert Pluim
2019-06-10 15:33     ` Eli Zaretskii [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=838su9bglk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@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 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).