From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
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 21:26:48 +0200 [thread overview]
Message-ID: <83h6xoa77r.fsf@gnu.org> (raw)
In-Reply-To: <fe12fb04-f12a-dd0a-95b2-d625acc5e796@gmail.com> (message from Jim Porter on Wed, 21 Dec 2022 10:48:18 -0800)
> Date: Wed, 21 Dec 2022 10:48:18 -0800
> Cc: 59545@debbugs.gnu.org, eliz@gnu.org,
> Milan Zimmermann <milan.zimmermann@gmail.com>
> From: Jim Porter <jporterbugs@gmail.com>
>
> However, I would have thought that you could write to NUL on MS Windows
> without any special handling. The Emacs manual has this to say:
>
> "[On MS Windows,] referencing any file whose name matches a DOS
> character device, such as NUL or LPT1 or PRN or CON, with or without any
> file-name extension, will always resolve to those character devices, in
> any directory. Therefore, only use such file names when you want to use
> the corresponding character device."
>
> I'd expect that to mean that if you opened a buffer and tried to save it
> as "NUL", it would just work, but instead I get:
>
> Write error: Bad file descriptor, c:/NUL
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.
next prev parent reply other threads:[~2022-12-21 19:26 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 [this message]
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
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=83h6xoa77r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59545@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--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).