how to resurrect a file
in [General Linux]
|
From: Chris F.A. Johnson on 12 Apr 2010 00:18 On 2010-04-12, Uno wrote: > Sidney Lambe wrote: >> On comp.os.linux.misc, Keith Keller >> <kkeller-usenet(a)wombat.san-francisco.ca.us> wrote: >> >>> On 2010-04-11, Sidney Lambe <sidneylambe(a)nospam.invalid> wrote: >>> >>>> Filenames with whitespaces is a Windows idiocy. >>> Not all of us are fortunate enough not to work with Windows >>> idiots. >>> >>>> I don't allow them on my box. >>> What, you have a badly-written shell script that scans every >>> filename as it's written? Either that or you have no friends >>> and therefore don't need any way of enforcing no spaces in >>> filenames. >> >> Another dickless punk who takes cheap shots at people while >> he hides behind the Internet. >> >> In the real world this loser would call me "sir" when he >> was finished mowing my lawn. >> >> <plonk> > > I'll thank you not to make remarks like the above on my threads. Sidney is the laughing stock of this and other newsgroups, but the amusement wore off long ago. Everyone else has him killfiled; I suggest you do the same. -- Chris F.A. Johnson, <http://cfajohnson.com> Author: Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress) Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
From: David Brown on 12 Apr 2010 03:31 Harald Meyer wrote: > Sidney Lambe wrote: > >> Filenames with whitespaces is a Windows idiocy. > /Forcing/ people to use filenames with whitespaces (or other awkward characters) is a windows thing (like calling standard directories "Program Files" or "Documents and Settings"). But Linux lets you call files exactly what you want to call them - it's up to the /user/ to choose whether or not they use white space in their filenames. *nix supported whitespace in filenames while DOS/Windows was still stuck at 8.3 names. > Yes. But sometimes one has to exchange files with Windows users, > or a Linux box is a fileserver for Windows clients, so every script > should be able to handle filenames with spaces. > >> (Another technocrat trying to turn Linux into Windows.) > > No, just somebody who takes care.
From: unruh on 12 Apr 2010 11:04 On 2010-04-12, David Brown <david.brown(a)hesbynett.removethisbit.no> wrote: > Harald Meyer wrote: >> Sidney Lambe wrote: >> >>> Filenames with whitespaces is a Windows idiocy. >> > > /Forcing/ people to use filenames with whitespaces (or other awkward > characters) is a windows thing (like calling standard directories > "Program Files" or "Documents and Settings"). But Linux lets you call > files exactly what you want to call them - it's up to the /user/ to > choose whether or not they use white space in their filenames. Well, rarely. It is usually some program that decides to dump white space into filenames, and it is a real pain for the command line. Since in Windows, essentially nothing gets done on the command line, it is not a real problem. On Linux, with command line, the ambiguity between separator and character for whitespace means it is a pain. Some people like whitespace. "My Recipie File" is a bit more intuitive than My_Recipie_File ( and easier to type). > > *nix supported whitespace in filenames while DOS/Windows was still stuck > at 8.3 names. Yes, but that whitespace had to be escaped somehow.
From: The Natural Philosopher on 12 Apr 2010 11:10 unruh wrote: > On 2010-04-12, David Brown <david.brown(a)hesbynett.removethisbit.no> wrote: >> Harald Meyer wrote: >>> Sidney Lambe wrote: >>> >>>> Filenames with whitespaces is a Windows idiocy. >> /Forcing/ people to use filenames with whitespaces (or other awkward >> characters) is a windows thing (like calling standard directories >> "Program Files" or "Documents and Settings"). But Linux lets you call >> files exactly what you want to call them - it's up to the /user/ to >> choose whether or not they use white space in their filenames. > > Well, rarely. It is usually some program that decides to dump white > space into filenames, and it is a real pain for the command line. Since > in Windows, essentially nothing gets done on the command line, it is not > a real problem. On Linux, with command line, the ambiguity between > separator and character for whitespace means it is a pain. > Some people like whitespace. "My Recipie File" is a bit more intuitive > than My_Recipie_File ( and easier to type). > >> *nix supported whitespace in filenames while DOS/Windows was still stuck >> at 8.3 names. > > Yes, but that whitespace had to be escaped somehow. > Only in the shells (of the time), that used whitespace to separate arguments. fp=fopen("/home/John Doe/My Documents/A load of unadulterated wombat turds.txt" "r"); has always worked.:-)
From: David Brown on 12 Apr 2010 15:18
unruh wrote: > On 2010-04-12, David Brown <david.brown(a)hesbynett.removethisbit.no> wrote: >> Harald Meyer wrote: >>> Sidney Lambe wrote: >>> >>>> Filenames with whitespaces is a Windows idiocy. >> /Forcing/ people to use filenames with whitespaces (or other awkward >> characters) is a windows thing (like calling standard directories >> "Program Files" or "Documents and Settings"). But Linux lets you call >> files exactly what you want to call them - it's up to the /user/ to >> choose whether or not they use white space in their filenames. > > Well, rarely. It is usually some program that decides to dump white > space into filenames, and it is a real pain for the command line. Since > in Windows, essentially nothing gets done on the command line, it is not > a real problem. On Linux, with command line, the ambiguity between > separator and character for whitespace means it is a pain. Lots of people use Linux without ever using the command line. If you use a gui file manager for file management tasks, white space is just another character. > Some people like whitespace. "My Recipie File" is a bit more intuitive > than My_Recipie_File ( and easier to type). > That's a good example (creatively spelt, but good nonetheless). If you have a word processor file which you create, edit, copy, print, email, etc., with gui applications, then what would be the advantage of using command-line friendly names? I use command-line friendly names for files that I access from the command line (such as programming files), and I'm freer with the characters when the files are only going to be used with gui applications. Incidentally, whitespace is only one form of character that can be a bit awkward from the command line. A far more relevant one for many people is non-ASCII characters. >> *nix supported whitespace in filenames while DOS/Windows was still stuck >> at 8.3 names. > > Yes, but that whitespace had to be escaped somehow. > Escaping is easy and consistent in *nix shells, so such names with spaces are not really /that/ hard to handle from the command line. It's much worse in the windows world on the command line (a preference for using the command line is independent of the choice of operating system, contrary to what many people believe). |