all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lycomedes 1814 <lycomedes1814@yandex.com>
Cc: emacs-devel@gnu.org
Subject: Re: [Small change] Issue with dired-do-async-shell-command and certain shells
Date: Thu, 18 May 2023 21:40:32 +0300	[thread overview]
Message-ID: <837ct5v5y7.fsf@gnu.org> (raw)
In-Reply-To: <5571181684433204@mail.yandex.com> (message from Lycomedes 1814 on Thu, 18 May 2023 20:12:45 +0200)

> 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?



  reply	other threads:[~2023-05-18 18:40 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837ct5v5y7.fsf@gnu.org \
    --to=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.