I do not have the problem using emacs built on cygwin either.
> On 6/26/2013 2:53 PM, g wrote:
> >
> >
> >
> > Daniel Barclay fgm.com> writes:
> >
> >>
> >> Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
&g
On 6/26/2013 2:53 PM, g wrote:
Daniel Barclay fgm.com> writes:
Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
files with a simple name of "NUL"?
Thanks,
Daniel
This has been driving me nuts for years. Finally tracked it down.
These are cre
Daniel Barclay fgm.com> writes:
>
> Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
> files with a simple name of "NUL"?
>
> Thanks,
> Daniel
>
>
This has been driving me nuts for years. Finally tracked it down.
These are c
On Mon, Nov 15, 2010 at 05:11:46AM +, TryingToHelp wrote:
>This is a known DOS/Windows bug. I'm fairly sure that DOS used NUL as a null
>device, and that Windows kept it around (not sure why, guess it's for
>backward-compatibility).
This thread is more than a month old. Th
This is a known DOS/Windows bug. I'm fairly sure that DOS used NUL as a null
device, and that Windows kept it around (not sure why, guess it's for
backward-compatibility).
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Doc
Den 2010-10-01 02:49 skrev Al:
>>
>> cd /dev
>> rm -f nul
Someone, somewhere, has done
echo crap > /dev/nul
instead of the intended
echo crap > /dev/null
If the /dev/nul file is still around it should be possible to
examine it and possible identify the culprit.
It
>
> cd /dev
> rm -f nul
>
I havn't seen that, but simliar. There remained setup.log and
setup.log.ful on my Desktop and I couldn't delete them.
>From another Cygwin installation I was able to remove them with your receipe.
rm -rf /cygdrive/c/Users/prefix/Desktop/set
Greetings, Max Funk!
> If I delete the folder cygwin on my PC (Windows 7, 32 bit),
> as described in the FAQ "Cygwin uninstall", then there is
> remaining a special file
> C:\cygwin\dev\nul
> This file cannot be deleted afterwards from windows
> (at least, I
On Thu, Sep 30, 2010 at 5:26 PM, Max Funk wrote:
> Hello,
>
> I wanted to report a problem with the cygwin uninstallation:
>
> If I delete the folder cygwin on my PC (Windows 7, 32 bit),
> as described in the FAQ "Cygwin uninstall", then there is
> remaining a spe
Hello,
I wanted to report a problem with the cygwin uninstallation:
If I delete the folder cygwin on my PC (Windows 7, 32 bit),
as described in the FAQ "Cygwin uninstall", then there is
remaining a special file
C:\cygwin\dev\nul
This file cannot be deleted afterwards from windows
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 re
Corinna Vinschen wrote:
...
Note: Don't use DOS device names in Cygwin!
Wrong:
$ echo foo> NUL
$ echo foo> nul
$ echo foo> nul:
Right:
$ echo foo> /dev/null
Yes, I know. I'm not using NUL (or nul or nul:, etc.), but something
is.
On Sep 17 11:22, Eric Blake wrote:
> On 09/17/2010 11:12 AM, Daniel Barclay wrote:
> >Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
It's Cygwin, not CygWin.
files with a simple name of "NUL"?
>
> Windows automagically maps the file
On 09/17/2010 11:12 AM, Daniel Barclay wrote:
Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
files with a simple name of "NUL"?
Windows automagically maps the file named "NUL", in any directory, to
the equivalent of Unix' /dev/null. Cygw
Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
files with a simple name of "NUL"?
Thanks,
Daniel
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
U
On 6/1/06, Robert McKay wrote:
Does anyone know what can go wrong with the windows NUL device? :-)
Do you need any kind of special permissions to use NUL?
You could download winobj from sysinternals.com.
Check that \GLOBAL??\NUL is a symbolic link to \Device\Null
Check that \Device\Null
On Thu, Jun 01, 2006 at 10:57:30AM +0100, Robert McKay wrote:
>I guess my next question is.. how hard would it be to simply replace
>the cygwin /dev/null with one that doesn't use the NUL device? If I
>could remove the /dev/null device and replace it with a second
>/dev/zero
t; Then I found this post:
>
> http://www.cygwin.com/ml/cygwin/2003-10/msg01017.html
>
> which shed some light on what might be the issue. Cygwin /dev/null is
> implemented on top of the windows NUL device. Sure enough when I try
> this from cmd.exe :
>
> Microsoft Windows XP
ssue in the mailing list
archives, however there it was happening to people running on embedded
windows.
Then I found this post:
http://www.cygwin.com/ml/cygwin/2003-10/msg01017.html
which shed some light on what might be the issue. Cygwin /dev/null is
implemented on top of the windows NUL device
fergus wrote:
> grep $'\x0d' # e.g. equivalent to grep "^M"
Using that method you're passing the literal character to grep through a
bash quoting mechanism. You can't pass a literal NULL as part of a
command line because argv[] consists of NULL-delimited strings, as do
most C string func
e.g. equivalent to grep "^M"
> grep $'\x1a' # e.g. equivalent to grep "^Z"
>
> and found this to work for all \x01 to \xff, that's 255 of the 256 one
> might be interested in looking for. (Well, I haven't tried them all, but
> a lot o
quot;^Z"
and found this to work for all \x01 to \xff, that's 255 of the 256 one might
be interested in looking for. (Well, I haven't tried them all, but a lot of
them.) What I still can't do (actually, what I most wanted to do) is search
for the NUL \x00. Nothing in info bash indi
t;>>>>Would it be appreciated if coreutils rm would be able to
>>>>>remove special windows files, like nul, aux, com and such, if it's
>>>>>really a file and no device?
>>>>>
>>>>>I'm working on such a coreutils pa
Christopher Faylor schrieb:
On Fri, Oct 29, 2004 at 08:05:40PM +0200, Reini Urban wrote:
Christopher Faylor schrieb:
On Fri, Oct 29, 2004 at 06:57:40PM +0200, Reini Urban wrote:
Would it be appreciated if coreutils rm would be able to
remove special windows files, like nul, aux, com and such, if
On Fri, Oct 29, 2004 at 08:05:40PM +0200, Reini Urban wrote:
>Christopher Faylor schrieb:
>>On Fri, Oct 29, 2004 at 06:57:40PM +0200, Reini Urban wrote:
>>>Would it be appreciated if coreutils rm would be able to
>>>remove special windows files, like nul, aux, com and
Christopher Faylor schrieb:
On Fri, Oct 29, 2004 at 06:57:40PM +0200, Reini Urban wrote:
Would it be appreciated if coreutils rm would be able to
remove special windows files, like nul, aux, com and such, if it's
really a file and no device?
I'm working on such a coreutils patch for
On Fri, Oct 29, 2004 at 06:57:40PM +0200, Reini Urban wrote:
>Would it be appreciated if coreutils rm would be able to
>remove special windows files, like nul, aux, com and such, if it's
>really a file and no device?
>
>I'm working on such a coreutils patch for rm(1) on
Would it be appreciated if coreutils rm would be able to
remove special windows files, like nul, aux, com and such, if it's
really a file and no device?
I'm working on such a coreutils patch for rm(1) only, not mv(1), ln(1)
or unlink(3) from cygwin1.dll.
Should it go to unlink(3) in
Markus Schönhaber wrote:
[snip]
nor from cygwin shell. Not a big problem, but annoying. Any ideas on
how to
get rid of it?
Assuming you created
C:\some\path\nul
using
del \\.\C:\some\path\nul
in the Windows console might help you to get rid of it.
I think even that will fail.
The trick I
Mironov, Leonid {PBG} wrote:
Once when I felt particulary stupid, I've added redirection to 'nul' instead
of '/dev/null' to a program run from cygwin cron. Now I've got a file called
'nul' on NTFS disk and can do nothing about it neither with windows tools
> Once when I felt particulary stupid, I've added redirection to 'nul'
> instead of '/dev/null' to a program run from cygwin cron. Now I've got a
> file called 'nul' on NTFS disk and can do nothing about it neither with
> windows tools nor fro
Once when I felt particulary stupid, I've added redirection to 'nul' instead
of '/dev/null' to a program run from cygwin cron. Now I've got a file called
'nul' on NTFS disk and can do nothing about it neither with windows tools
nor from cygwin shell. Not a
Hi,
I would like to declare this the NUL-est thread ever, and would like to thank you
NUL-experts for
your NUL-help.
Seriously I've now learnt how to delete those pesky undeletable windows files namely
DEL \\.\c:\somedir\nul
or delinvfile.exe (google for this utility)
And also the conu
> -Original Message-
> From: cygwin-owner On Behalf Of Larry Hall
> Sent: 22 July 2004 03:01
> You can use '.' in place of '?'.
[ Insert here quick discussion of difference between a UNC path to the local
host's redirector and a softlink in the root of the object namespace
hierarchy to t
Hi,
I would like to declare this the NUL-est thread ever, and would like to thank you
NUL-experts for
your NUL-help.
Seriously I've now learnt how to delete those pesky undeletable windows files namely
DEL \\.\c:\somedir\nul
or delinvfile.exe (google for this utility)
And also the conu
I just use a freeware tool...
http://www.purgeie.com/delinv.htm
Trevor
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
At 01:50 PM 7/21/2004, you wrote:
>On Wed, 21 Jul 2004 13:28:30 -0400, wrote:
>
>>At 01:32 PM 7/21/2004, you wrote:
>>>On Wed, 21 Jul 2004 18:14:45 +0100, wrote:
>>>
>>>
>>>>>
>>>>> I recently seem to be leaving nul fil
On Wed, Jul 21, 2004 at 09:58:37PM +, Jan Engelhardt wrote:
>>I've been using this:
>
>Interesting. I would have booted Linux and removed 'nul' with its
>tools. :)
Hmm. I would have taken a very tiny magnet, pried open the cover of
the hard drive, and run t
> I've been using this:
Interesting. I would have booted Linux and removed 'nul' with its tools. :)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin
On Wed, 21 Jul 2004, Chuck McDevitt wrote:
> While it's not hard to delete the rouge "nul" files, it is a recent change
> to cygwin that allows them to be created at all.
>
> 1.5.9 seemed to treat "NUL" in the normal windows way (equivalent of
>
While it's not hard to delete the rouge "nul" files, it is a recent change
to cygwin that allows them to be created at all.
1.5.9 seemed to treat "NUL" in the normal windows way (equivalent of
/dev/null), so didn't create these files.
1.5.10 changed so Cygwi
On Wed, 21 Jul 2004 19:05:05 +0100, wrote:
>> -Original Message-
>> From: cygwin-owner On Behalf Of zzapper
>> Sent: 21 July 2004 18:51
>
>> >>>> I recently seem to be leaving nul files around my file system
>> >>>> which I can
At Wednesday, July 21, 2004 1:51 PM, zzapper wrote:
> On Wed, 21 Jul 2004 13:28:30 -0400, wrote:
>
>> At 01:32 PM 7/21/2004, you wrote:
>>> On Wed, 21 Jul 2004 18:14:45 +0100, wrote:
>>>>>
>>>>> I recently seem to be leaving nul files around
> -Original Message-
> From: cygwin-owner On Behalf Of zzapper
> Sent: 21 July 2004 18:51
> >>>> I recently seem to be leaving nul files around my file system
> >>>> which I cannot delete from Cyg or Win
> >>>DEL \\.\c:\somedir\nul
&g
On Wed, 21 Jul 2004 13:28:30 -0400, wrote:
>At 01:32 PM 7/21/2004, you wrote:
>>On Wed, 21 Jul 2004 18:14:45 +0100, wrote:
>>
>>
>>>>
>>>> I recently seem to be leaving nul files around my file system
>>>> which I cannot delete from C
> -Original Message-
> From: cygwin-owner On Behalf Of zzapper
> Sent: 21 July 2004 18:33
> On Wed, 21 Jul 2004 18:14:45 +0100, wrote:
> >> I recently seem to be leaving nul files around my file system
> >> which I cannot delete from Cyg or Win
> >&g
On Wed, 21 Jul 2004 10:26:41 -0700, wrote:
Eric I tried
#!/usr/bin/env perl
my $filename='nul';
if (unlink $filename) {
print "Removed $filename.\n";
} else {
warn "Can't unlink $filename: $!";
}
Said it had deleted file but that was lie!!
zzapper (vim,
At 01:32 PM 7/21/2004, you wrote:
>On Wed, 21 Jul 2004 18:14:45 +0100, wrote:
>
>
>>>
>>> I recently seem to be leaving nul files around my file system
>>> which I cannot delete from Cyg or Win
>>>
>>> Hilfe mich!
>>
>
>>
On Wed, 21 Jul 2004 18:14:45 +0100, wrote:
>>
>> I recently seem to be leaving nul files around my file system
>> which I cannot delete from Cyg or Win
>>
>> Hilfe mich!
>
>
>DEL \\.\c:\somedir\nul
>
>cheers,
> DaveK
no luck
C:\in
I've been using this:
#!/usr/bin/env perl
use warnings;
use strict;
use Data::Dumper;
die "This program is only useful on Cygwin.\n"
unless ($^O eq "cygwin");
my $filename = shift;
$filename =~ s(/nul$)()i;
$filename = qx(realp
> -Original Message-
> From: cygwin-owner On Behalf Of zzapper
> Sent: 21 July 2004 17:13
> Hi,
>
> I recently seem to be leaving nul files around my file system
> which I cannot delete from Cyg or Win
>
> Hilfe mich!
http://www.google.com/sear
Hi,
I recently seem to be leaving nul files around my file system which I cannot delete
from Cyg or Win
Hilfe mich!
zzapper (vim, cygwin, wiki & zsh)
--
vim -c ":%s/^/WhfgTNabgureRIvzSUnpxre/|:%s/[R-T]/ /Ig|:normal ggVGg?"
http://www.vim.org/tips/tip.php?tip_id=305 Be
error.
HTH,
Igor
On Fri, 2 Jul 2004, PLAN Frédéric URS Lyon wrote:
> Hello,
>
> try this way :
>
> cd my_folder
> find ./ -name "nul" -exec rm {} /;
>
> Fred
>
>
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED
On Fri, Jul 02, 2004 at 01:16:07PM +0200, Pfeiffer Michael wrote:
>thanks a lot for the tip!
>
>Btw sorry for posting the question on the mailing list.
There is no reason to apologize. Cygwin should not be creating files that
cygwin cannot easily delete. Your question was entirely appropriate.
Hello,
try this way :
cd my_folder
find ./ -name "nul" -exec rm {} /;
Fred
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part
de Michael Pfeiffer
Envoye : vendredi 2 juillet 2004 11:29
A : [EMAIL PROTECTED]
Objet : How to delete file &q
Hi ZARAZA
thanks a lot for the tip!
Btw sorry for posting the question on the mailing list.
Have a nice weekend,
Michael
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
F
del \\.\d:\nul
--
~/ZARAZA
http://www.security.nnov.ru/
--Friday, July 2, 2004, 1:29:02 PM, you wrote to [EMAIL PROTECTED]:
MP> Hi
MP> bash allows to pipe to a file named "nul" e.g.:
MP> echo test > nul
MP> bash-2.05b$ ls -l
MP> total 1
MP> -rwxrwxrwx1 pf
Please search the list archives before asking for something:
http://cygwin.com/ml/cygwin/2004-06/msg01235.html
(it's a message of 3 days ago).
Ciao,
Danilo
Michael Pfeiffer wrote:
Hi
bash allows to pipe to a file named "nul" e.g.:
echo test > nul
bash-2.
Hi
bash allows to pipe to a file named "nul" e.g.:
echo test > nul
bash-2.05b$ ls -l
total 1
-rwxrwxrwx1 pfeiffer mkgroup-4 Jul 2 10:00 nul
The problem is that this file can not be deleted.
I was not able to delete it using the "rm" command in
bash, or &qu
> Hi,
>>
>> I have recognized that files named "aux", "lpt1", "nul", "prn" ... (old
DOS
>> devices) generated under Cygwin on a XP OS cannot be deleted anymore:
>>
>> rm: cannot unlink `prn': Permission denied
>&
On Jun 30 11:46, Guettich, Ulrich, OPM2 wrote:
> Hi,
>
> I have recognized that files named "aux", "lpt1", "nul", "prn" ... (old DOS
> devices) generated under Cygwin on a XP OS cannot be deleted anymore:
>
> rm: cannot unlink `prn
Hi,
I have recognized that files named "aux", "lpt1", "nul", "prn" ... (old DOS
devices) generated under Cygwin on a XP OS cannot be deleted anymore:
rm: cannot unlink `prn': Permission denied
Why? How to get rid of them?
Best regards
Ulrich
-
On Thu, 27 May 2004, Christopher Faylor wrote:
> On Thu, May 27, 2004 at 11:39:22AM -0400, Volker Quetschke wrote:
> >Igor wrote:
> >>A couple more datapoints:
> >>
> >>- You can also create "nul" by "touch nul".
> >>- You can us
On Thu, May 27, 2004 at 11:39:22AM -0400, Volker Quetschke wrote:
>Igor wrote:
>>A couple more datapoints:
>>
>>- You can also create "nul" by "touch nul".
>>- You can use forward slashes, so "rm //./c:/somedir/nul" works.
>>- For me
Hi Igor,
A couple more datapoints:
- You can also create "nul" by "touch nul".
- You can use forward slashes, so "rm //./c:/somedir/nul" works.
- For me (on Win2k SP3), "rm nul" doesn't hang, but doesn't do anything
either.
Here neither, but
On Thu, 27 May 2004, Volker Quetschke wrote:
> Just FYI and for the archives:
>
> > Any ideas how to remove the nul files? Really, I don't want to
> > format my disk because of this.
> You can fool NTFS into not doing reserve-word checking with:
>
> DEL \\.\c:\some
> -Original Message-
> From: cygwin-owner On Behalf Of Dave Korn
> Sent: 27 May 2004 15:43
> How about
>
> cmd /c 'del nu?.*'
>
> Does that get it?
Nope, it doesn't. Volker's technique is the right answer.
cheers,
DaveK
--
Can't think of a witty .sigline today..
> -Original Message-
> From: cygwin-owner On Behalf Of Volker Quetschke
> Sent: 27 May 2004 15:32
> Vince Hoffman wrote:
> >>>I somehow managed to create a file named nul (further investigation
> >>>pending), and now rm -rf hangs when trying to remo
Just FYI and for the archives:
Any ideas how to remove the nul files? Really, I don't want to
format my disk because of this.
You can fool NTFS into not doing reserve-word checking with:
DEL \\.\c:\somedir\nul
You propably have to use the correct quotes, or use cmd.exe,
like I did.
Volker
-
Hi Dave,
I somehow managed to create a file named nul (further investigation
pending), and now rm -rf hangs when trying to remove the
directory with
this file.
Known ('doze) problem. Also occurs with filenames like aux, com1, lpt
etc. The workaround is WDDTT.
No, wrong, the problem a
Vince Hoffman wrote:
I somehow managed to create a file named nul (further investigation
pending), and now rm -rf hangs when trying to remove the
directory with
this file.
Known ('doze) problem. Also occurs with filenames like aux, com1, lpt
etc. The workaround is WDDTT.
umm is that anothe
On Thu, 27 May 2004, Dave Korn wrote:
> > -Original Message-
> > From: cygwin-owner On Behalf Of Volker Quetschke
> > Sent: 27 May 2004 14:25
> > To: [EMAIL PROTECTED]
> > Subject: rm hangs on illegal filename nul
> >
> > Hi,
> >
> -Original Message-
> From: cygwin-owner On Behalf Of Volker Quetschke
> Sent: 27 May 2004 14:25
> To: [EMAIL PROTECTED]
> Subject: rm hangs on illegal filename nul
>
> Hi,
>
> I somehow managed to create a file named nul (further investigation
> pendi
Hi,
I somehow managed to create a file named nul (further investigation
pending), and now rm -rf hangs when trying to remove the directory with
this file.
I just upgraded to cygwin 1.5.10-3, I will try with 1.5.9 later.
[EMAIL PROTECTED]/cygdrive/e/w1/OOo/expat/wntgcci.pro/misc/build/expat:{505
74 matches
Mail list logo
