From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>,
1212@emacsbugs.donarmstrong.com, emacs-devel@gnu.org,
emacs-pretest-bug@gnu.org
Subject: Re: bug#1212: 23.0.60; split-string-and-unquote problems
Date: Mon, 20 Oct 2008 21:11:10 -0400 [thread overview]
Message-ID: <jwvljwiu5g4.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <u63nmj2tx.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 21 Oct 2008 00:53:30 +0200")
> *** `split-string-and-unquote' does (what?)
> *** `combine-and-quote-strings' does (what?)
AFAIK, these two functions are meant to:
- provide a way to specify any list of strings within a single string
(i.e. it needs to provide some separators and some way to quote the
separators), using a format that's simple to type for the end user.
- be inverse of each other; more precisely
(equal STR (split-string-and-unquote (combine-and-quote-strings STR)))
this is also stipulated in the docstring of split-string-and-unquote.
As the docstring of split-string-and-unquote explains, the quoting used
is the same as the one used for ELisp strings.
I could have used sh-style quoting or csh-style, or any other style, but
csh-style is nasty, sh-style is too powerful (what should we do with
backquotes and $(...)), and ELisp is what Emacs uses already and it's
reasonably simple and we know it handles all cases reasonably well, so
it seemed like an OK choice.
Stefan
next prev parent reply other threads:[~2008-10-21 1:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 16:04 bug#1212: 23.0.60; split-string-and-unquote problems Eli Zaretskii
2008-10-20 17:01 ` Andreas Schwab
2008-10-20 19:06 ` Eli Zaretskii
2008-10-20 21:30 ` Andreas Schwab
2008-10-20 22:36 ` Eli Zaretskii
2008-10-21 9:25 ` Andreas Schwab
2008-10-21 10:18 ` Eli Zaretskii
2008-10-21 11:00 ` Andreas Schwab
2008-10-21 11:33 ` Eli Zaretskii
2008-10-21 11:49 ` Andreas Schwab
2008-10-21 12:25 ` Eli Zaretskii
2008-10-21 12:50 ` Andreas Schwab
2008-10-21 12:58 ` Eli Zaretskii
2008-10-21 13:24 ` Andreas Schwab
2008-10-21 13:36 ` Eli Zaretskii
2008-10-21 13:44 ` Andreas Schwab
2008-10-21 15:13 ` Eli Zaretskii
2008-10-20 17:08 ` Andreas Schwab
2008-10-20 19:16 ` Eli Zaretskii
2008-10-20 21:28 ` Andreas Schwab
2008-10-20 22:53 ` Eli Zaretskii
2008-10-20 22:53 ` Eli Zaretskii
2008-10-21 1:11 ` Stefan Monnier [this message]
2008-10-21 6:27 ` Eli Zaretskii
2008-10-21 15:43 ` Stefan Monnier
2008-10-21 16:05 ` Eli Zaretskii
2008-10-22 2:04 ` Stefan Monnier
2008-10-22 4:31 ` Eli Zaretskii
2008-10-22 14:58 ` Stefan Monnier
2008-10-22 19:43 ` Eli Zaretskii
2008-10-22 21:42 ` Stefan Monnier
2008-10-22 22:11 ` Eli Zaretskii
2008-10-23 1:18 ` Stefan Monnier
2008-10-23 4:29 ` Eli Zaretskii
2008-10-23 4:39 ` Miles Bader
2008-10-23 13:55 ` Stefan Monnier
2008-10-21 1:11 ` Stefan Monnier
2008-10-21 1:11 ` Stefan Monnier
2008-10-20 22:53 ` Eli Zaretskii
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=jwvljwiu5g4.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1212@emacsbugs.donarmstrong.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=schwab@suse.de \
/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.