From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: bug#1212: 23.0.60; split-string-and-unquote problems
Date: Thu, 23 Oct 2008 06:29:07 +0200 [thread overview]
Message-ID: <uabcwdje4.fsf@gnu.org> (raw)
In-Reply-To: <jwvr668w1oh.fsf-monnier+emacsbugreports@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Wed, 22 Oct 2008 21:18:20 -0400
>
> >> >> I do not understand: what makes you think it could be a properly quoted
> >> >> shell command?
> >> > Because you said that working with shell commands was why these
> >> > functions were invented in the first place. And that is how they are
> >> > used in Emacs as of now.
> >> No, they're used to run commands. Without going through a shell.
> > Then why would one need quoting?
>
> Because when you run a command with start-process or call-process, you
> need to specify a list of strings (each being an argument), but the user
> usually wants to enter the list within a single minibuffer. So from the
> string returned by the read-string (or equivalent) function, we need to
> get a list of strings.
If I am prompted for a command in the minibuffer, as in "M-x compile",
I will type a command that uses shell quoting (assuming I need
quoting). That is the natural thing to do, so I expect most users to
do the same. I don't expect many of them to use Lisp string quoting
for commands.
next prev parent reply other threads:[~2008-10-23 4:29 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-21 1:11 ` Stefan Monnier
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 [this message]
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
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=uabcwdje4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.