unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: thievol@posteo.net, 71554@debbugs.gnu.org, christopher@librehacker.com
Subject: bug#71554: 29.3; eshell-command async buffer behavior
Date: Mon, 24 Jun 2024 15:33:46 +0300	[thread overview]
Message-ID: <86o77qbjv9.fsf@gnu.org> (raw)
In-Reply-To: <3ed3832f-e874-ab89-52c3-c0c32650cb33@gmail.com> (message from Jim Porter on Sun, 23 Jun 2024 22:36:47 -0700)

> Date: Sun, 23 Jun 2024 22:36:47 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, 71554@debbugs.gnu.org,
>  christopher@librehacker.com
> From: Jim Porter <jporterbugs@gmail.com>
> 
> Eli, what do you think about merging this into the Emacs 30 branch? I 
> have no strong preference myself, but I think it's small enough that it 
> should be safe, and it fixes an annoyance with Eshell today. (I can also 
> write a regression test or two if that would help matters.)

Why do we have to make this change in Emacs 30?  AFAIU, it isn't a
bug, just inconsistency between shell-mode and Eshell, and we have
lived with it for quite some time.  Right?

I'd like to have as short a pretest for Emacs 30.1 as possible, and
that means no changes we don't absolutely have to make.  Please
consider the necessity of this change from that POV.





  parent reply	other threads:[~2024-06-24 12:33 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 [this message]
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
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

  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=86o77qbjv9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71554@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    --cc=jporterbugs@gmail.com \
    --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 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).