From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: 26925@debbugs.gnu.org, stephen.berman@gmx.net
Subject: bug#26925: Improve /doc/lispref/strings.texi (split-string) documentation
Date: Sat, 03 Jun 2017 12:59:18 +0300 [thread overview]
Message-ID: <83o9u5bde1.fsf@gnu.org> (raw)
In-Reply-To: <3D9A3600-CF3D-4DD9-866C-CBEE8F692B25@gmail.com> (message from Jean-Christophe Helary on Sat, 3 Jun 2017 17:50:27 +0900)
> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
> Date: Sat, 3 Jun 2017 17:50:27 +0900
> Cc: Eli Zaretskii <eliz@gnu.org>,
> 26925@debbugs.gnu.org
>
> -If the optional argument @var{trim}
> →
> +If @var{trim}
>
> just to adapt the text to the description of the other arguments.
Thanks, but I see no problem with the current text. We use both
styles intermittently.
next prev parent reply other threads:[~2017-06-03 9:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 15:45 bug#26925: Improve /doc/lispref/strings.texi (split-string) documentation Jean-Christophe Helary
2017-05-19 11:47 ` Eli Zaretskii
2017-05-19 12:23 ` Jean-Christophe Helary
2017-05-19 12:56 ` Eli Zaretskii
2017-05-19 13:02 ` Jean-Christophe Helary
2017-05-19 13:30 ` Stephen Berman
2017-06-03 8:50 ` Jean-Christophe Helary
2017-06-03 9:59 ` Eli Zaretskii [this message]
2017-06-03 13:50 ` Jean-Christophe Helary
2017-06-03 14:46 ` Eli Zaretskii
2017-06-03 23:45 ` Jean-Christophe Helary
2017-06-04 2:38 ` Eli Zaretskii
2017-06-04 7:49 ` Michael Albinus
2017-06-04 9:19 ` Jean-Christophe Helary
2017-06-04 13:57 ` Eli Zaretskii
2017-06-04 15:14 ` Jean-Christophe Helary
2017-06-04 15:46 ` Eli Zaretskii
2017-06-05 0:33 ` Jean-Christophe Helary
2017-06-05 2:46 ` Eli Zaretskii
2017-06-05 3:31 ` Jean-Christophe Helary
2017-06-05 5:15 ` Jean-Christophe Helary
2017-06-05 15:09 ` Eli Zaretskii
2017-06-05 21:24 ` Jean-Christophe Helary
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=83o9u5bde1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26925@debbugs.gnu.org \
--cc=jean.christophe.helary@gmail.com \
--cc=stephen.berman@gmx.net \
/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.