This is the mail archive of the
mailing list for the Cygwin project.
Re: where was mention of what creates NUL files?
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Date: Thu, 27 Jun 2013 14:57:16 -0400
- Subject: Re: where was mention of what creates NUL files?
- References: <4C93A171 dot 4040402 at fgm dot com> <loom dot 20130626T202645-269 at post dot gmane dot org>
On 6/26/2013 2:53 PM, g wrote:
Daniel Barclay <daniel <at> fgm.com> writes:
Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
files with a simple name of "NUL"?
This has been driving me nuts for years. Finally tracked it down.
These are created by emacs' man.el code when you get a man page.
In emacs, do:
M-x man <ret>
<enter anything, valid ('ls') or not>
Now, you'll see a NUL file in the directory.
I can't reproduce this with Cygwin emacs. You must be using native
construction of the 'man' command that is passed to the shell includes:
(concat " %s 2>" null-device)
The variable `null-device' is platform specific and defaults to a pure-copy
of "/dev/null" which, apparently, becomes "NUL" on windows.
It is a defvar in files.el and 'set' again in dos-w32.el.
In your .emacs file, do:
(require 'dos-w32) ;; load this first to avoid it undo'ing the next line
(setq null-device "c:/tmp/emacs-dev-null.txt") ;; set to anything
Just to be clear, users of Cygwin emacs should *not* do this.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple