Ok, but maybe you're asking - but what good is that? How can you tell which is which? How can you even be sure you linked the right inode number to the right filename? Now I'm going to mirror this directory: set - * mkdir. Here, I'll do some crazy stuff:įirst I'll create 20 files, and name them with nothing but spaces, each filename containing one more space than the last: until The filename is a thing for human consumption - if you wanna make it a crazy thing, well, it's your filesystem. instead), and add -name ' ' to the find command to skip files that dont have spaces, and add either -i or -n to the mv command to avoid data loss if theres a filename conflict. The perfect solution, aside from threatening the guillotine for those who insist on using spaces in such places (not to mention the guys who put this in operating systems code), might be a routine that 'escapes' the file and directory names for us, kind of like how cygwin has routines to convert from unix to dos filename formats. name \. Also, I recommend adding double-quotes around (pwd) in case it contains spaces (or just use. name \.xml -print0 xargs -0 grep -lZ ' It does carry some weight as a file attribute in that you typically need a filename to open a file, but a file's name only points to the actual file. But it needs to be said that a filename is not a file. So yes, as is stated many times elsewhere, a filename can contain nearly any character. In a shell/command line context, wrap the filename in single or double quotes (but note they are not the same WRT other issues), or escape the spaces with \, e.g.: > foo my\ file\ with\ spaces\ in\ the\ name How do you use or deal with a space in a filename correctly? But this is inevitable, since spaces are allowed, so. However, if you make any use of the shell, you may realize that there are some characters that will create a hassle, most significantly *, which is a POSIX globbing operator.ĭepending on how you want to define "hassle", you could include whitespace (spaces, tabs, newlines, etc.) in there, as this creates the need for quoting with "". "Null" refers to a zero byte, but these are not allowed in text data anyway. The only forbidden characters are / and "null". We can subsume 7-bit ASCII under this umbrella too, since it is a subset of various 8-bit sets and is always implemented using 8 bit bytes. If you look at the "most UNIX filesystems" entry in this chart in wikipedia, you'll notice:Īny 8-bit character set is allowed.
n :space: It will not report hidden files.
0 kommentar(er)
