From: Alex Riesen <raa.lkml@gmail.com>
Date: Sat, 08 Oct 2005 06:45:55 GMT
Subject: Re: [RFC] embedded TAB and LF in pathnames
Message-ID: <20051008064555.GA3831@steel.home>
In-Reply-To: <7vpsqgyjrj.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano, Sat, Oct 08, 2005 01:44:48 +0200:
> > Junio C Hamano, Fri, Oct 07, 2005 21:35:19 +0200:
> >> I have not made up my mind on the exact choice of the quoting
> >> convention.  We could say '///' instead of '//', for example, or
> >> even '//{LF}//' instead of '//0A' proposed above.  One thing I
> >> am trying to avoid is "foo\nbar", which I suspect would be
> >> unfriendly to the Cygwin folks.
> >
> > Being unhappy one of them, I think I'd better manage (even if by
> > postprocessing the output).
> >
> > Please, don't make the common case ugly just because of that platform
> > (insanely broken anyway).
> 
> You really have to realize that having LF and TAB in filenames
> are *NOT* the common case, no matter which platform you are
> talking about.
> 

Yes, but "//" in a path is quite common. Even "///" is not uncommon.

How about copy ls' approach were possible?

   -b, --escape, --quoting-style=escape
          Quote  nongraphic  characters in file names using alphabetic and
          octal backslash sequences like those used in C. This  option  is
          the  same as -Q except that filenames are not surrounded by dou-
          ble-quotes.