Linux – Using underscore in file names

command linefile managementlinux

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

Best Answer

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.

Related Solutions

Windows – How to use Cmd’s tab autocomplete effectively

1 year update: I came to the conclusion that Cmd's autocomplete is unusable, and stopped using it.

I installed Clink which gives you Bash-style autocompletion in Cmd.

Clink combines the native Windows shell cmd.exe with the powerful command line editing features of the GNU Readline library, which provides rich completion, history, and line-editing capabilities

It's brilliant.

Linux – Using a shell script but it fails with spaces on directory or name

You are quoting one of the $1 's but not the other. If your path contains spaces, quoting is essential. To be safe, it's best to assume that every path a script receives contains problematic characters, and quote every path.

Here's my suggestion:

gs  -q -dNOPAUSE -dBATCH -dSAFER \
    -sDEVICE=pdfwrite \
    -dCompatibilityLevel=1.3 \
    -dPDFSETTINGS=/screen \
    -dEmbedAllFonts=true \
    -dSubsetFonts=true \
    -dColorImageDownsampleType=/Bicubic \
    -dColorImageResolution=72 \
    -dGrayImageDownsampleType=/Bicubic \
    -dGrayImageResolution=72 \
    -dMonoImageDownsampleType=/Bicubic \
    -dMonoImageResolution=72 \
    "-sOutputFile=Compressed$1" \
    "$1"

In case you are wondering, it's fine to quote options like this; it's no different from quoting other kinds of arguments. gs -q and gs "-q" look exactly the same to gs when gs receives them.

We just use them here to make sure the entire path is made part of the -sOutputFile option , rather than what was previously the case: the fragment before the space was correctly assigned to the option argument, and the fragment after the space was an independent argument, that gs may well have treated as if it were the input file argument.

Best Answer

Related Solutions

Windows – How to use Cmd’s tab autocomplete effectively

Linux – Using a shell script but it fails with spaces on directory or name

Related Question