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 20:50:34 +0200 [thread overview]
Message-ID: <83tyikta85.fsf@gnu.org> (raw)
In-Reply-To: <524EC395-B36D-4678-AF93-43C24C9E9745@boostpro.com>
> Cc: "7563-done@debbugs.gnu.org" <7563-done@debbugs.gnu.org>,
> "1212-done@debbugs.gnu.org" <1212-done@debbugs.gnu.org>
> From: Dave Abrahams <dave@boostpro.com>
> Date: Sat, 11 Dec 2010 12:57:30 -0500
>
> Sorry, let me precise: your fix is correct inasmuch as it fulfills your intention, but the text you were working on is still wrong because it says quite clearly that backslash escaping is supported, but as I have shown, it is not.
Quoting with backslashes _is_ supported, in the Lisp string style.
Try this, for example:
(split-string-and-unquote "\"foo\\\"bar\" bar") => ("foo\"bar" "bar")
> Specifically it specifically states they handle backslashes, and strongly implies that they have generally-useful semantics for interacting with arbitrary shells, when in fact they are essentially implementation details of call-/start-process whose semantics are only appropriate to an undocumented set of conditions set up in those two functions.
I tried to make it more clear that these functions are mainly for
working with command-line arguments of call-/start-process.
> >> * The functions' design still has nothing to do with shell quoting;
> >> they are hard-coded to work with double-quotes and only
> >> double-quotes, which is not guaranteed to work for an arbitrary
> >> definition of "shell."
> >
> > I believe the manual says precisely that. If the problem is with
> > mentioning "shell", would removing that solve this difficulty?
>
> It would certainly help
Done.
next prev parent reply other threads:[~2010-12-11 18:50 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 [this message]
2010-12-11 19:41 ` Dave Abrahams
2010-12-11 20:42 ` Eli Zaretskii
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
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=83tyikta85.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 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).