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


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

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: Re: bug#16005: inferior-lisp and filenames with spaces
Date: Thu, 15 Jul 2021 10:45:05 +0300
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: sdlitvin <at> earthlink.net,  16005 <at> debbugs.gnu.org
> Date: Thu, 15 Jul 2021 09:30:34 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Then how about using split-string-and-unquote instead of split-string?
> 
> That would be an improvement, certainly.  It'd take care of
> "\"foo bar\" zot".  However, it doesn't do "foo\\ bar zot", and both are
> equivalent in shells.

Users will have to use quoting "like this".  We can document that.
It's a relatively rare use case, so I don't think the partial support
for quoting is such a bad idea.

> Which is why I wondered whether we had a function to split based on
> shell(ish) syntax, which would be the optimal solution here...

I think split-string-and-unquote is the only one that comes close.  If
someone wants to emulate the shells we support, patches are welcome
(and then there will still be the problem to know the exact shell
which is being targeted in each use case).




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.