GNU bug report logs - #71554
29.3; eshell-command async buffer behavior

Previous Next

Full log

View this message in rfc822 format

From: Thierry Volpiatto <thievol <at> posteo.net>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: Thierry Volpiatto <thievol <at> posteo.net>, christopher <at> librehacker.com, Eli Zaretskii <eliz <at> gnu.org>, 71554-done <at> debbugs.gnu.org
Subject: bug#71554: 29.3; eshell-command async buffer behavior
Date: Sat, 06 Jul 2024 04:12:57 +0000

[Message part 1 (text/plain, inline)]

Jim Porter <jporterbugs <at> gmail.com> writes:

> On 7/5/2024 1:23 PM, Jim Porter wrote:
>> If an Eshell command is running in the "...<2>" buffer, then running
>> another Eshell command in "*Eshell Async Command Output*" at the
>> same time should be ok. As such, I don't think it's necessary to
>> prompt the user in this case: the two async commands can happily run
>> side-by-side.
>
> I've now merged this to the master branch with a few fixes (including
> an obscure bug in Eshell's process sentinel - Eshell's always full of
> surprises), plus a regression test and a NEWS entry as
> 7f631a3e2ac. Closing this bug now, but if I've missed anything, just
> let me know.

            (cond
             ((with-current-buffer bufname
                (and (null eshell-foreground-command)
                     (null eshell-background-commands)))
              ;; The old buffer is done executing; kill it so we can
              ;; take its place.
              (kill-buffer bufname))

What if user ran a serie of commands and want to see the output of each
one?

-- 
Thierry

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.