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: 59545@debbugs.gnu.org, milan.zimmermann@gmail.com
Subject: bug#59545: 29.0.50; Eshell fails to redirect output of sourced eshell file
Date: Wed, 21 Dec 2022 14:01:30 +0200	[thread overview]
Message-ID: <83h6xpartx.fsf@gnu.org> (raw)
In-Reply-To: <9f56f995-c03d-a10e-ac18-b873af8589dc@gmail.com> (message from Jim Porter on Tue, 20 Dec 2022 16:29:31 -0800)

> Date: Tue, 20 Dec 2022 16:29:31 -0800
> From: Jim Porter <jporterbugs@gmail.com>
> Cc: eliz@gnu.org
> 
> On 12/20/2022 4:18 PM, Jim Porter wrote:
> > Attached is a patch series to fix this, with a bunch of new tests. I 
> > also fixed a related issue where redirecting to /dev/null could clobber 
> > your other redirects. (There's *also* an issue that should be fixed for 
> > the release branch; I'll send that in a separate message.)
> 
> Eli, this is the patch for the release branch (it corresponds to part 
> 0003 of the patch series for master). Is this ok to merge? It's a 
> regression that was introduced in Emacs 28.1, and the fix is pretty simple.

Yes, OK to install this on the release branch.

Thanks.





      parent reply	other threads:[~2022-12-21 12:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 15:49 bug#59545: 29.0.50; Eshell fails to redirect output of sourced eshell file Milan Zimmermann
2022-12-21  0:18 ` Jim Porter
2022-12-21  0:29   ` Jim Porter
2022-12-21  9:54     ` Michael Albinus
2022-12-21 18:48       ` Jim Porter
2022-12-21 19:26         ` Eli Zaretskii
2022-12-22  1:20           ` Jim Porter
2022-12-22 20:02             ` Jim Porter
2022-12-24  7:29               ` Jim Porter
2022-12-25  1:36                 ` Jim Porter
2022-12-25 21:49                   ` Jim Porter
2022-12-26 19:50                     ` Jim Porter
2022-12-30  6:40                       ` Jim Porter
2022-12-21 12:01     ` Eli Zaretskii [this message]

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=83h6xpartx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59545@debbugs.gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=milan.zimmermann@gmail.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).