bug#71554: 29.3; eshell-command async buffer behavior

[Thierry Volpiatto]

Christopher Howard <christopher@librehacker.com> writes:

> Hello, I run a lot of async commands a lot with eshell-command,
> preferring it over shell-command. However, there is a difference
> between shell-command and eshell-command behavior which is a little
> bothersome and does not make sense to me. If I run an async command
> with shell-command, e.g. `sleep 60 &', and then run another one while
> the first one is still running, shell-command will ask me if I want to
> create a new buffer for the output, and I usually do. However, if I do
> the same thing with eshell-command, eshell command will give me only
> two options, either (1) kill the currently running command, or (2)
> don't create an output buffer, which also throws an error. I was
> wondering if it would be possible to add the "create a new buffer"
> option to eshell-command as well, for the upcoming 30 release.

Please do not add a "ask to create a new buffer" option to fix this
issue, just do not ask and create a new buffer, modifying eshell-command
with something like this should be enough:

@@ -305,6 +305,5 @@
-            (bufname (if (eq (car-safe proc) :eshell-background)
-                         "*Eshell Async Command Output*"
-                       (setq intr t)
-                       "*Eshell Command Output*")))
-       (if (buffer-live-p (get-buffer bufname))
-           (kill-buffer bufname))
+            (bufname (generate-new-buffer-name
+                       (if (eq (car-safe proc) :eshell-background)
+                          "*Eshell Async Command Output*"
+                        (setq intr t)
+                        "*Eshell Command Output*"))))


-- 
Thierry