GNU bug report logs - #25025
python-shell-calculate-command is wrong

Previous Next

Package: emacs;

Reported by: Fabrice Popineau <fabrice.popineau <at> gmail.com>

Date: Fri, 25 Nov 2016 06:26:01 UTC

Severity: normal

Tags: confirmed, fixed

Merged with 20744

Found in version 25.1

Fixed in version 26.1

Done: npostavs <at> users.sourceforge.net

Bug is archived. No further changes may be made.

Full log


Message #34 received at 25025 <at> debbugs.gnu.org (full text, mbox):

From: npostavs <at> users.sourceforge.net
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25025 <at> debbugs.gnu.org, clement.pit <at> gmail.com
Subject: Re: bug#25025: python-shell-calculate-command is wrong
Date: Sun, 27 Nov 2016 11:06:03 -0500
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Noam Postavsky <npostavs <at> users.sourceforge.net>
>> Date: Sat, 26 Nov 2016 19:50:40 -0500
>> Cc: Clément Pit--Claudel <clement.pit <at> gmail.com>, 
>> 	25025 <at> debbugs.gnu.org
>> 
>> >> I think the whole command should be quoted with
>> >> combine-and-quote-strings to balance the call to
>> >> split-string-and-unquote.
>> >
>> > Why not remove both of those calls?  Do you understand why they are
>> > needed in that case?
>> 
>> Well, CMD can also come from user input, so we would need some way for
>> the user to specify a list of arguments. Currently that can work by
>> entering a string that would be split by split-string-and-unquote.
>
> Why does it need to be split?  A shell command can (even should) be
> handed to the shell as a single string.

Currently it's not a shell command, because a shell isn't being used.
My other suggestion was to use a shell:

>> It might be more intuitive to actually use a shell and then the user
>> would enter a shell command (though inserting a shell into things
>> might bring more complications).




This bug report was last modified 7 years and 276 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.