From:	orre AT nada DOT kth DOT se (Roland Orre)
Subject:	Re: rm -i not working
24 Oct 1996 23:55:38 -0700 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199610250554.HAA06367.cygnus.gnu-win32@sans07.nada.kth.se>
Reply-To:	orre AT nada DOT kth DOT se (Roland Orre)
Original-To:	gnu-win32 AT cygnus DOT com
Original-CC:	Colman Curtin <ccurtin AT trintech DOT com>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Colman Curtin wrote:
>>Has any one noticed the following problem:
>>  ~/mydir> rm -i foo.bar
>>doesn't work!
>>
>>--
>>Weiqi Gao
>>weiqigao AT crl DOT com
>>
>Yes I saw this too but if you type
>~/mydir> rm -i foo.*
>it will work for the 2nd and successive files found.
>after that I don't know.
>
>Coley.

Yes, I noticed this when I downloaded beta16. This seem to be some kind of
CR-LF file handling (EOL?) problem.

If you do:
~/mydir> rm -i foo.*
and end with a linefeed (Cntrl-J) instead of CR it works fine. The problem is
probably within bash because if you do the same in a DOS shell it works fine.

	Roland
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -