|
|
IMPORTANT: Spaces need to be escaped!
Whenever you have spaces in path names you need to escape them if you work in the Terminal.
For example, the command
It doen't matter much for the cd command as you will simply get an error message, but when you are creating symbolic links things can get a little messy if you don't properly escape the spaces in the path name.
PS:
IMPORTANT: Spaces need to be escaped!
Re: I have a feeling that this behavior of the forum software is what is responsible for the absence of backslashes in the original hint.
IMPORTANT: Spaces need to be escaped!
Very weird, I could have sworn the backslash was in my post after I had posted it...
Yes, single quotes would also work. I usually avoid them as I think that they tend to make thinks more messy but that might be a subjective thing.
Just out of curiosity, a quick test:
Forum software is fixed now
Looks like the backslash eating behavior of the forum software has been fixed now. Excellent. :)
Forum software is NOT fixed
Looks like I need some sleep, I confused slashes with backslashes in my earlier test.
backslashes vs. quotes
Yes, single quotes would also work. I usually avoid them as I think that they tend to make thinks more messy but that might be a subjective thing.
Yep, personal preference is subjective; backslash-quoted text looks sloppier to me. I'll sometimes use them in interactive shells but avoid unnecessary usage in scripts. And I think experienced shell programmers (those I respect most anyway :-)) recommend using single- or double-quoted strings. Anyway, viewing filenames that contain backslash-quoting is more inefficiently unreadable to me than simply dropping any quotes from each end. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|