From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16005@debbugs.gnu.org, sdlitvin@earthlink.net
Subject: bug#16005: inferior-lisp and filenames with spaces
Date: Thu, 15 Jul 2021 10:45:05 +0300 [thread overview]
Message-ID: <835yxc6mwu.fsf@gnu.org> (raw)
In-Reply-To: <87y2a8kp9h.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 15 Jul 2021 09:30:34 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: sdlitvin@earthlink.net, 16005@debbugs.gnu.org
> Date: Thu, 15 Jul 2021 09:30:34 +0200
>
> Eli Zaretskii <eliz@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).
next prev parent reply other threads:[~2021-07-15 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:27 bug#16005: 24.3; function inferior-lisp needs patch to work with certain filenames in Windows-NT Steven Litvintchouk
2013-11-30 22:12 ` Glenn Morris
2021-07-15 5:33 ` bug#16005: inferior-lisp and filenames with spaces Lars Ingebrigtsen
2021-07-15 6:58 ` Eli Zaretskii
2021-07-15 7:10 ` Lars Ingebrigtsen
2021-07-15 7:25 ` Eli Zaretskii
2021-07-15 7:30 ` Lars Ingebrigtsen
2021-07-15 7:45 ` Eli Zaretskii [this message]
2021-07-15 8:00 ` Lars Ingebrigtsen
2021-07-15 8:19 ` Eli Zaretskii
2021-07-15 8:30 ` Lars Ingebrigtsen
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=835yxc6mwu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16005@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=sdlitvin@earthlink.net \
/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).