Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I use the command line frequently to navigate my files so I try not to have spaces in file names. Typically I have used an underscore to connect words but it was recently suggested that I should use a dash. Are there any disadvantages to using an underscore in file names? Should I switch to a dash? My system is running Xubuntu and I almost exclusively use the bash shell.

Thanks

share|improve this question

4 Answers 4

up vote 11 down vote accepted

As far as the operating system is concerned they both are as usable as each other.

One thing I would note - some software (such as some video playing systems - XBMC etc) will automatically replace underscores with spaces when displaying files to make them look nicer.

For that reason alone I'd be tempted to stick to underscores.

Also, hyphens are used for switches to commands, so it may be a little confusing having hyphens in you filenames as well as in your command switches.

Other than that it's purely down to personal choice.

share|improve this answer
1  
I use hythens, but that's because I like the look better. To technical reason behind it. –  tjameson Apr 4 '11 at 17:36
    
Thanks! Thats what I suspected but I have also found that going on my suspicions alone can get me into trouble. –  KennyPeanuts Apr 4 '11 at 18:34

Dash doesn't require you to press SHIFT, meaning you type faster. That is the only other benefit I can think of above what Mr. Jenkins has suggested.

Likely the person making that suggestion is an avid Vim user and wishes to do everything with the least amount of keyboard movement.

share|improve this answer
3  
If that were the case they'd use vi instead - one less keystroke ;) –  Majenko Apr 4 '11 at 17:39
1  
@Matt it's alias'ed to v anyway ;-) –  Daniel Beck Apr 4 '11 at 18:24

The only reason you should consider using hyphens instead of underscores is for basic readability. Frequent underscores tend to distort reading, as it changes the line of your vision from the center of the y-axis to the bottom. Hyphens however make it easier on the eye.

As far as the operating system is concered, both characters are equally valid, and don't require escaping (which spaces do, and hence are a pain to work with).

share|improve this answer

My recommendation is to use underscores instead of spaces. Underscores are usually the convention that people use when replacing spaces, although hyphens are fine too I'd say. But since hyphens might show up in other ways such as hyphenated words, you'll have more success in preserving a name value by using underscores. For instance, if you have a file called "A picture taken in Winston-Salem, NC.jpg" and you want to convert the spaces to underscores, then you can preserve the hyphen in the name and retain its meaning.

Spaces cause problems for people who want to use the command line in advanced ways such as in for loops like this:

for file in *.mp3 ; do mpg321 $file -w - | oggenc -o ${file%%.mp3}.ogg - ; done

If any of the mp3 files matched by that wildcard have spaces in their name, it will cause the filename to be broken up into sections instead of the whole. You can get around this by changing the BASH shell's IFS variable or using the find command, but its an annoyance and a lot of people don't know this, so it can cause problems.

I doubt this or even a bumper sticker campaign would prevent people from putting spaces in filenames, but if you want to help yourself, more power to you and thank you on behalf of those of us who care.

share|improve this answer
1  
I agree totally. A well constructed filename needs no spaces. –  KennyPeanuts Apr 4 '11 at 18:33
2  
@KennyPeanuts - but a well written program doesn't choke on spaces. –  detly Apr 5 '11 at 5:27
1  
@detly - touche' –  KennyPeanuts Apr 5 '11 at 10:03
1  
@detly No, a good programmer understands that there have to be limits in what you can do and should do. If you say it shouldn't choke on spaces, then someone could one up that and say it shouldn't choke on end of line, then someone would say it shouldn't choke on /, then someone could say it shouldn't choke on end of file. There is an old saying "Formula for failure: try to please everyone". –  deltaray Apr 5 '11 at 15:11
1  
The filesystem spec tells you what to code to, no more, no less. On Ext2/3/4, for example, a filename may contain any character except \0 or \\\`. Coding to anything less than that is broken by design. So, no, it shouldn't choke on spaces, or EOL, or non-ASCII characters, or anything that isn't \0` or `\`. Using library functions for file path manipulation is the way to go, because many other people have already solved these problems. –  detly Apr 6 '11 at 0:55

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.