Re: shell-command - missing shell-quote-argument for program?

[Kim F. Storm]

Slawomir Nowaczyk <address@hidden> writes:

> On Tue, 10 Oct 2006 09:02:24 +0200
> Lennart Borgman <address@hidden> wrote:
>
> #> > I am not entirely sure it is needed, but the following shouldn't
> #> > hurt in any case.
> #> > <snip>
> #> 
> #> Thanks, but it looks to me that this should not be quoted.
> #> `python-command' is not just a file.
> #> 
> #> My mistake. Sorry.
>
> Right, it looks like python-command may include arguments that should be
> passed to the interpreter. My patch is obviously wrong.
>
> Seems like it is up to a user customising this variable to make sure any
> meta characters are escaped properly... Does anyone think it would make
> sense to add some information about it to the doc string? Or are
> problems with that too unlikely to worry about them?

If the user messes up the variable, he will notice immediately the next
time he tries the related command.

We only need to focus on getting things right for arguments which
are problematic, e.g. when user enters a file name with spaces or
a file name read from a directory contains spaces...

-- 
Kim F. Storm <address@hidden> http://www.cua.dk