From: Po Lu <luangruo@yahoo.com>
To: Lycomedes 1814 <lycomedes1814@yandex.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [Small change] Issue with dired-do-async-shell-command and certain shells
Date: Fri, 19 May 2023 15:23:10 +0800 [thread overview]
Message-ID: <875y8o4wf5.fsf@yahoo.com> (raw)
In-Reply-To: <528571684452080@mail.yandex.com> (Lycomedes's message of "Fri, 19 May 2023 01:22:04 +0200")
Lycomedes 1814 <lycomedes1814@yandex.com> writes:
> Clarification: it works when "&wait" is changed to "& wait" and the two instances of "&" are changed to "& ".
>
> 18.05.2023, 23:28, "Lycomedes 1814" <lycomedes1814@yandex.com>:
>
> Indeed, "& wait" works with fish. For the function to work with multiple files selected, "&" must be changed to "& ".
>
> 18.05.2023, 20:40, "Eli Zaretskii" <eliz@gnu.org>:
>
> From: Lycomedes 1814 <lycomedes1814@yandex.com>
> Date: Thu, 18 May 2023 20:12:45 +0200
>
> 1. Use fish as your system shell.
> 2. Use dired-do-async-shell-command on any file, and type e.g. mpv.
>
> Fish interprets "&wait" as part of the file name, so mpv returns: "[file] Cannot open file '027.wav&wait':
> No such file or directory."
>
> Solution:
>
> In the function dired-shell-stuff-it, replace "&wait" with "& ". Then fish interprets the command
> correctly.
>
> But the "wait" part is there for a reason, so simply removing it is
> hardly TRT.
>
> What if we use " & wait" instead, i.e. add a space between & and
> "wait"? does the command then work correctly with fish?
Is fish a Bourne shell?
next prev parent reply other threads:[~2023-05-19 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 18:12 [Small change] Issue with dired-do-async-shell-command and certain shells Lycomedes 1814
2023-05-18 18:40 ` Eli Zaretskii
2023-05-18 21:28 ` Lycomedes 1814
2023-05-18 23:22 ` Lycomedes 1814
2023-05-19 6:29 ` Eli Zaretskii
2023-05-19 14:54 ` Lycomedes 1814
2023-05-19 15:51 ` Eli Zaretskii
2023-05-19 17:15 ` Lycomedes 1814
2023-05-19 18:26 ` Eli Zaretskii
2023-05-19 19:01 ` Lycomedes 1814
2023-05-19 19:11 ` Eli Zaretskii
2023-05-20 14:29 ` Eli Zaretskii
2023-05-19 7:23 ` Po Lu [this message]
2023-05-19 15:01 ` Lycomedes 1814
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=875y8o4wf5.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lycomedes1814@yandex.com \
/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).