unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59545@debbugs.gnu.org, milan.zimmermann@gmail.com,
	michael.albinus@gmx.de
Subject: bug#59545: 29.0.50; Eshell fails to redirect output of sourced eshell file
Date: Wed, 21 Dec 2022 17:20:58 -0800	[thread overview]
Message-ID: <c2c66d13-d2ec-abd5-93d5-9f64a2aafe66@gmail.com> (raw)
In-Reply-To: <83h6xoa77r.fsf@gnu.org>

On 12/21/2022 11:26 AM, Eli Zaretskii wrote:
> It's a bug, unrelated to the actual writing.  I fixed it now on the
> emacs-29 branch.  You should be able now to save "NUL" on MS-Windows.

Ah, good that we caught that bug then. With that change, my original 
patches should be sufficient. I've merged my patch for the emacs-29 
branch as d6c8d5dbc9fc4786e91b76654058e904c96f0e11 (with some additional 
improvements to the comment/commit message).

I'll wait to merge my changes to master for a couple days to give others 
time to comment though, since those changes are more extensive.





  reply	other threads:[~2022-12-22  1:20 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 [this message]
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

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=c2c66d13-d2ec-abd5-93d5-9f64a2aafe66@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=59545@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    --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).