From: Jim Porter <jporterbugs@gmail.com>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: christopher@librehacker.com, Eli Zaretskii <eliz@gnu.org>,
71554-done@debbugs.gnu.org
Subject: bug#71554: 29.3; eshell-command async buffer behavior
Date: Fri, 5 Jul 2024 19:48:18 -0700 [thread overview]
Message-ID: <a61c5787-1b04-c72f-ed2f-02aedf4e5c42@gmail.com> (raw)
In-Reply-To: <dcc061db-beb2-917f-24cd-db449f6248b7@gmail.com>
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.
next prev parent reply other threads:[~2024-07-06 2:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 13:57 bug#71554: 29.3; eshell-command async buffer behavior Christopher Howard
2024-06-14 18:53 ` Thierry Volpiatto
2024-06-14 18:56 ` Eli Zaretskii
2024-06-14 20:32 ` Thierry Volpiatto
2024-06-14 22:49 ` Jim Porter
2024-06-15 5:13 ` Thierry Volpiatto
2024-06-20 7:30 ` Thierry Volpiatto
2024-06-24 5:36 ` Jim Porter
2024-06-24 6:23 ` Thierry Volpiatto
2024-06-24 12:33 ` Eli Zaretskii
2024-07-05 4:09 ` Thierry Volpiatto
2024-07-05 5:46 ` Eli Zaretskii
2024-07-05 6:24 ` Thierry Volpiatto
2024-07-05 11:11 ` Eli Zaretskii
2024-07-05 12:21 ` Thierry Volpiatto
2024-07-05 14:34 ` Thierry Volpiatto
2024-07-05 17:41 ` Jim Porter
2024-07-05 18:44 ` Thierry Volpiatto
2024-07-05 20:23 ` Jim Porter
2024-07-06 2:48 ` Jim Porter [this message]
2024-07-06 3:34 ` Thierry Volpiatto
2024-07-06 4:12 ` Thierry Volpiatto
2024-07-06 5:28 ` Jim Porter
2024-07-06 6:10 ` Thierry Volpiatto
2024-06-24 14:15 ` Christopher Howard
2024-07-06 15:13 ` Christopher Howard
2024-07-06 17:06 ` Thierry Volpiatto
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=a61c5787-1b04-c72f-ed2f-02aedf4e5c42@gmail.com \
--to=jporterbugs@gmail.com \
--cc=71554-done@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=eliz@gnu.org \
--cc=thievol@posteo.net \
/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.