From: Oleksandr Gavenko <gavenko@bifit.com.ua>
To: cygwin@cygwin.com
Subject: Re: where was mention of what creates NUL files?
Date: Mon, 20 Sep 2010 10:22:00 -0000 [thread overview]
Message-ID: <i77a5a$30t$1@dough.gmane.org> (raw)
In-Reply-To: <4C93A171.4040402@fgm.com>
On 17.09.2010 20:12, Daniel Barclay wrote:
> Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
> files with a simple name of "NUL"?
>
I also use native Emacs and after some operation I got file with name NUL.
I have a lot NUL files in many dirs, which can be removed only from Cygwin:
$ rm NUL
I don't fully debug but think this come from 'null-device' variable
(which has 'NUL' value by default).
To friend native GNU Emacs with Cygwin (and stop creating NUL) I use:
(when (eq system-type 'windows-nt)
(setq shell-file-name "bash")
;; Workaround for Cygwin shell, when set 'CYGWIN=noglob'. By default
'shell-quote-argument'
;; quoted by double '\' chars this cause failure.
(defun shell-quote-argument (argument)
(concat "'" argument "'")
)
;; Workaround for Cygwin when 'shell-file-name' is 'bash'.
(setq null-device "/dev/null")
)
--
Happy hacking!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2010-09-20 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 18:01 Daniel Barclay
2010-09-17 18:02 ` Eric Blake
2010-09-17 22:46 ` Corinna Vinschen
2010-09-18 3:37 ` Daniel Barclay
2010-09-20 10:22 ` Oleksandr Gavenko [this message]
2013-06-27 18:35 ` g
2013-06-27 19:00 ` Ken Brown
2013-06-27 22:32 ` wynfield
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='i77a5a$30t$1@dough.gmane.org' \
--to=gavenko@bifit.com.ua \
--cc=cygwin@cygwin.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.
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).