Bernard Dautrevaux <[EMAIL PROTECTED]> writes: > In fact Windows not exactly ignores periods at the end of file names: > writing a filename as "foo." asks windows NOT to search for "foo.exe" or > "foo.bat" IF it needs to execute the file... This is allows to execute "foo" > instead of "foo.exe" if both exist, just to add some more fun :-) That's not windows, that's command.com or cmd.exe. If you put "." at the end, it [wrongly] thinks there's and extension, and only searches for that extension, which in this case is blank. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
- Re: Trailing Periods on File Names Christopher Faylor
- Re: Trailing Periods on File Names Larry Hall (RFK Partners, Inc)
- OT pondering (WAS: Re: Trailing Period... Jonathon Merz
- Re: OT pondering (WAS: Re: Trailin... DJ Delorie
- Re: OT pondering (WAS: Re: Trailin... Andrew Markebo
- Re: OT pondering (WAS: Re: Trailin... Earnie Boyd
- Re: OT pondering (WAS: Re: Trailin... Larry Hall (RFK Partners, Inc)
- Re: OT pondering (WAS: Re: Trailin... Mark Gordon
- Re: OT pondering (WAS: Re: Trailin... Robert Collins
- RE: Trailing Periods on File Names Bernard Dautrevaux
- RE: Trailing Periods on File Names DJ Delorie
- RE: Trailing Periods on File Names Bernard Dautrevaux