DO NOT REPLY [Bug 35592] - [net] Unix parser not handling filenames beginning with whitespace

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35592>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35592


scohen@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Unix parser not handling    |[net] Unix parser not
                   |filenames beginning with    |handling filenames beginning
                   |whitespace                  |with whitespace




------- Additional Comments From scohen@apache.org  2005-07-04 14:57 -------
Gaaaaaahhhh.

I'm a little reluctant to adopt your solution since I suppose there might be an
FTP implementation somewhere that might insert spaces before the file name to
keep the filenames lined up in a column.

You may be right, but why would anyone ever want to name files beginning with a
whitespace? I can't ever remember seeing such a filename.  I've just now
verified that unix allows it, although you have to go a little out of your way
to achieve it.    echo  cat > " cat"

I'd like to hear more about your use case before I introduce code that assumes
that no FTP server would ever insert whitespaces in the list output before the
filename.




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org