GNU bug report logs - #59545
29.0.50; Eshell fails to redirect output of sourced eshell file

Previous Next

Full log

Message #23 received at 59545 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: 59545 <at> debbugs.gnu.org, milan.zimmermann <at> gmail.com, michael.albinus <at> gmx.de
Subject: Re: bug#59545: 29.0.50; Eshell fails to redirect output of sourced
 eshell file
Date: Wed, 21 Dec 2022 21:26:48 +0200

> Date: Wed, 21 Dec 2022 10:48:18 -0800
> Cc: 59545 <at> debbugs.gnu.org, eliz <at> gnu.org,
>  Milan Zimmermann <milan.zimmermann <at> gmail.com>
> From: Jim Porter <jporterbugs <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.