From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: worley@world.std.com, t.link@gmx.at, briot@gnat.com,
Emacs Devel <emacs-devel@gnu.org>,
Holger.Schauer@gmx.de, storm@cua.dk, pbreton@cs.umb.edu,
pk_at_work@yahoo.com, dominik@science.uva.nl
Subject: Re: shell-command - missing shell-quote-argument for program?
Date: Tue, 10 Oct 2006 00:14:46 +0200 [thread overview]
Message-ID: <452AC9D6.9030602@student.lu.se> (raw)
In-Reply-To: <rzqr6xhf9l9.fsf@loveshack.ukfsn.org>
Dave Love wrote:
> Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
>
>
>> Hi all Authors,
>>
>> I mail you all directly about the possible bugs below in case you do
>> not read the Emacs Devel list. It would be very nice if you could fix
>> these bugs. (There was another such bug in ediff which I mailed
>> Michael Kifer seperately earlier.)
>>
>
> I'm sorry, but I don't know why you're sending this to me -- I can't
> get things fixed in Emacs. Anyhow, I don't understand what you're
> talking about, so I suspect others won't. You need to be explicit in
> a bug report and send it to the maintainer(s) who can deal with it.
>
> By the way, as far as I know, emerge is obsoleted by ediff. It should
> be in lisp/obsolete so as not have time wasted on it. rms demurred on
> that, but for no good reason as far as I remember.
>
Hi Dave,
Thanks for responding. I am sorry if I were not clear enough about the
problem. The problem is that when you call shell-command (or
shell-command-to-string) the arguments may need to be quoted so that the
shell does not mistreat them. A common example is file names with spaces
in them. If a file name with spaces are used as argument to
shell-command it must be quoted. Otherwise the shell will treat it as
several arguments.
I found examples of what I suspected was missing quoting in the files I
mentioned and I therefore mailed you as authors (since there is no
maintainer mentioned in the files).
So far Kim Storm has responded and fixed the problem in ido.el. I would
be very glad if you (I mean the authors here) tried to point out where
the call to shell-quote-argument should be inserted to avoid the
problem. It seems much simpler if you do it. However if you do not do
that I will try to do that myself in a couple of days.
Kind regards,
L
Here are the files again:
- emerge.el
According to Dave it is probably obsolete and replaced by ediff. Then I
will just leave emerge.el as it is.
- filesets.el
- shell.el: defcustom explicit-bash-args <- never used?
This was a misunderstanding on my side. Resolved on the devel list.
- progmodes/python.el: python-after-info-look: python-command
- progmodes/flymake.el: flymake-get-project-include-dirs-imp: basedir
should perhaps be quoted?
- progmodes/ada-xref.el: ada-find-in-src-path
- ido.el: ido-wide-find-dirs-or-files: several examples of missing quoting
Kim has fixed ido.el.
- locate.el: locate-update-command shoue perhaps be quoted? (But
probably not, since it may include more than the program name. Bad
structure?)
- fortune.el
- org.el
- reftex-global.el: reftex-create-tags-file
next prev parent reply other threads:[~2006-10-09 22:14 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 [this message]
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
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=452AC9D6.9030602@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=Holger.Schauer@gmx.de \
--cc=briot@gnat.com \
--cc=dominik@science.uva.nl \
--cc=emacs-devel@gnu.org \
--cc=pbreton@cs.umb.edu \
--cc=pk_at_work@yahoo.com \
--cc=storm@cua.dk \
--cc=t.link@gmx.at \
--cc=worley@world.std.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).