GNU bug report logs - #16005
inferior-lisp and filenames with spaces

Previous Next

Package: emacs;

Reported by: Steven Litvintchouk <sdlitvin <at> earthlink.net>

Date: Fri, 29 Nov 2013 23:20:02 UTC

Severity: minor

Tags: moreinfo

Found in version 24.3

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 16005 <at> debbugs.gnu.org, sdlitvin <at> earthlink.net
Subject: bug#16005: inferior-lisp and filenames with spaces
Date: Thu, 15 Jul 2021 10:25:19 +0300
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: sdlitvin <at> earthlink.net,  16005 <at> debbugs.gnu.org
> Date: Thu, 15 Jul 2021 09:10:33 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >>       (let ((cmdlist (split-string cmd)))
> >> 	(set-buffer (apply (function make-comint)
> >> 			   "inferior-lisp" (car cmdlist) nil (cdr cmdlist)))
> 
> [...]
> 
> > If we prompt the users for a shell command, we should expect the users
> > to quote it as they would when they type at the shell's prompt.  is
> > this prompt for the complete shell command, or is it only for the name
> > of the program's executable file?  If the latter, we should run the
> > result through shell-quote-argument before using it; if the former,
> > the user should do the quoting, and there's no bug in Emacs.
> 
> It's the former.  The problem is that there is no way for the user to
> quote the command, since we do a `split-string' on what they typed in
> before executing it.

Then how about using split-string-and-unquote instead of split-string?




This bug report was last modified 4 years and 31 days ago.

Previous Next


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