From: Richard Stallman <rms@gnu.org>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: shell-command - missing shell-quote-argument for program?
Date: Sun, 15 Oct 2006 06:12:09 -0400 [thread overview]
Message-ID: <E1GZ2yX-0003ra-5N@fencepost.gnu.org> (raw)
In-Reply-To: <ubqofro5g.fsf@gnu.org> (message from Eli Zaretskii on Sat, 14 Oct 2006 16:02:35 +0200)
If we quote emerge-command and the various emerge-*-program, we in
effect disallow them to be shell commands with switches. Is that
reasonable? If it is, then we should quote the programs.
If that's what these variables do, their values should not be quoted,
so that they can include some arguments.
> - defcustom explicit-bash-args
Since that exists only to be sent as arguments,
it should not be quoted. The user will put in whatever
quoting is called for.
next prev parent reply other threads:[~2006-10-15 10:12 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 14:34 shell-command - missing shell-quote-argument for program? Lennart Borgman
2006-10-05 14:53 ` Lennart Borgman
2006-10-06 11:38 ` Lennart Borgman
2006-10-06 12:34 ` Andreas Schwab
2006-10-06 12:43 ` Kim F. Storm
2006-10-06 12:49 ` David Kastrup
2006-10-06 13:34 ` Kim F. Storm
2006-10-07 1:07 ` Richard Stallman
2006-10-07 13:11 ` Andreas Schwab
2006-10-08 3:30 ` Richard Stallman
2006-10-08 15:43 ` Andreas Schwab
2006-10-08 22:27 ` Richard Stallman
2006-10-08 22:36 ` Andreas Schwab
2006-10-09 20:08 ` Richard Stallman
2006-10-09 9:12 ` Kim F. Storm
2006-10-06 12:49 ` Kim F. Storm
2006-10-06 13:20 ` Lennart Borgman
2006-10-12 14:56 ` Kim F. Storm
2006-10-12 22:38 ` Richard Stallman
2006-10-13 21:26 ` Lennart Borgman
2006-10-13 23:16 ` Lennart Borgman
2006-10-14 7:13 ` Thomas Link
2006-10-13 18:13 ` Thomas Link
2006-10-13 19:55 ` Lennart Borgman
2006-10-13 21:20 ` [Bulk] " Thomas Link
2006-10-14 10:07 ` Richard Stallman
2006-10-14 14:11 ` Eli Zaretskii
[not found] ` <4526434B.9010606@student.lu.se>
[not found] ` <rzqr6xhf9l9.fsf@loveshack.ukfsn.org>
2006-10-09 22:14 ` Lennart Borgman
2006-10-10 6:46 ` Slawomir Nowaczyk
2006-10-10 7:02 ` Lennart Borgman
2006-10-12 13:52 ` Slawomir Nowaczyk
2006-10-12 14:18 ` Kim F. Storm
2006-10-15 13:50 ` Dave Love
2006-10-15 19:08 ` Lennart Borgman
2006-10-16 22:33 ` Dave Love
2006-10-16 22:37 ` Lennart Borgman
2006-10-14 14:02 ` Eli Zaretskii
2006-10-14 15:33 ` Lennart Borgman
2006-10-14 17:50 ` Andreas Schwab
2006-10-14 18:15 ` Eli Zaretskii
2006-10-15 9:30 ` Lennart Borgman
2006-10-15 20:43 ` Kim F. Storm
2006-10-14 18:22 ` Eli Zaretskii
2006-10-14 23:02 ` Kim F. Storm
2006-10-15 9:00 ` Lennart Borgman
2006-10-15 9:35 ` Lennart Borgman
2006-10-15 20:42 ` Kim F. Storm
2006-10-15 10:12 ` Richard Stallman
2006-10-15 14:14 ` Slawomir Nowaczyk
2006-10-15 10:12 ` Richard Stallman [this message]
2006-10-15 19:13 ` Lennart Borgman
2006-10-15 20:43 ` Kim F. Storm
2006-10-05 19:36 ` Stefan Monnier
2006-10-05 19:58 ` Eli Zaretskii
2006-10-05 20:21 ` Lennart Borgman
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=E1GZ2yX-0003ra-5N@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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).