unofficial mirror of emacs-devel@gnu.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: Fri, 19 May 2023 18:51:59 +0300	[thread overview]
Message-ID: <83fs7stj34.fsf@gnu.org> (raw)
In-Reply-To: <764021684507963@mail.yandex.com> (message from Lycomedes 1814 on Fri, 19 May 2023 16:54:44 +0200)

> From: Lycomedes 1814 <lycomedes1814@yandex.com>
> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Fri, 19 May 2023 16:54:44 +0200
> 
> Sure, here's a diff:

Thanks.

> diff -u /home/jal/Code/emacs-patch/dired-aux.el /home/jal/Code/emacs-patch/dired-aux-new.el
> --- /home/jal/Code/emacs-patch/dired-aux.el    2023-05-19 14:45:53.360586128 +0000
> +++ /home/jal/Code/emacs-patch/dired-aux-new.el    2023-05-19 14:46:39.880476896 +0000
> @@ -945,7 +945,7 @@
>           ;; "&" instead.
>           (cmd-sep (if (and (or (not w32-shell) file-remote)
>                 (not parallel-in-background))
> -              ";" "&"))
> +              ";" "& "))

Here "&" is used only on MS-Windows, where I don't expect to see fish
as the shell.  Are you sure this is relevant to the problem?

> @@ -969,7 +969,7 @@
>                 ;; Add 'wait' to force those POSIX shells to wait until
>                 ;; all commands finish.
>                 (or (and parallel-in-background (not w32-shell)
> -                        "&wait")
> +                        "& wait")

This is the one we've been talking about from the beginning.

> @@ -977,7 +977,7 @@
>           (when (cdr file-list)
>             (setq files (concat dired-mark-prefix files dired-mark-postfix)))
>           (funcall stuff-it files))))
> -     (or (and in-background "&") ""))))
> +     (or (and in-background "& ") ""))))

This AFAIU is just appended to the end of the command, with nothing
after it.  Are you sure this one is needed?  If so, can you describe a
reproduction recipe where "&" here causes a problem and "& " doesn't?



  reply	other threads:[~2023-05-19 15:51 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 [this message]
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

  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=83fs7stj34.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 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).