`touch' created wrong file without giving error

[Peter J. Acklam]

I tried creating a file named " foo ", i.e., with two leading and
two trailing blanks using "touch".  It turned out that "touch"
created the file, but without the two trailing blanks.  It might
be that a file name with trailing blanks can't be created on an
NTFS file system, but "touch" shouldn't create the wrong file but
rather give an error telling that it failed.  Silently creating
the wrong name is generally bad:

   $ touch '  foo  '
   $ echo $?
   0
   $ for file in *foo*; do echo "|$file|"; done
   |  foo|
        ^^

"touch" returned exit status 0, but failed to create the file.
"ls" also shows that the file only has the leading blanks:

   $ ls -b *foo*
   \ \ foo

Should "touch" return an error when it fails?

Peter

-- 
Peter J. Acklam - pjacklam@online.no - http://home.online.no/~pjacklam



--
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/