From: Eli Zaretskii <eliz@gnu.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: 7563@debbugs.gnu.org
Subject: bug#7563: 23.2; `split-string-and-unquote' mis-documented / purpose unclear
Date: Sat, 11 Dec 2010 22:42:06 +0200 [thread overview]
Message-ID: <83r5dot529.fsf@gnu.org> (raw)
In-Reply-To: <781E581B-DE27-4C7E-B97A-DF133D7AD38E@boostpro.com>
> Cc: "7563@debbugs.gnu.org" <7563@debbugs.gnu.org>
> From: Dave Abrahams <dave@boostpro.com>
> Date: Sat, 11 Dec 2010 14:41:52 -0500
>
> Thanks. I'm away from the docs ATM but IIRC this stuff is documented in a section on interacting with the shell but it seems from the way you describe the behavior that this function is all about Emacs string processing and should be elsewhere or it will mislead people
We cannot have a separate section for every possible sub-class of
features. The description of these functions is in the section named
"Shell Arguments", indeed, but this section is part of a chapter named
"Processes", and it deals with a specialized kind of quoting, so I
don't see how this will mislead, given the explicit references to
call-process and start-process.
If naming sections is important, we could rename the section to
something like "Command Arguments".
next prev parent reply other threads:[~2010-12-11 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 21:28 bug#7563: 23.2; `split-string-and-unquote' mis-documented / purpose unclear Dave Abrahams
2010-12-05 21:38 ` bug#7563: related bug Dave Abrahams
2010-12-06 0:37 ` bug#7563: one more detail Dave Abrahams
2010-12-11 9:51 ` Eli Zaretskii
2010-12-11 9:50 ` bug#7563: 23.2; `split-string-and-unquote' mis-documented / purpose unclear Eli Zaretskii
[not found] ` <m2fwu477ch.wl%dave@boostpro.com>
[not found] ` <834oakux25.fsf@gnu.org>
[not found] ` <524EC395-B36D-4678-AF93-43C24C9E9745@boostpro.com>
2010-12-11 18:50 ` Eli Zaretskii
2010-12-11 19:41 ` Dave Abrahams
2010-12-11 20:42 ` Eli Zaretskii [this message]
2010-12-11 22:27 ` Dave Abrahams
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=83r5dot529.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7563@debbugs.gnu.org \
--cc=dave@boostpro.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.