Contents
Why do I have spaces in my bash script?
The crux of your issue is actually taking place at the mv command, which should be written as because these days, you never know when a variable representing a path will have spaces in it. Once again, note the avoidance of braces for a simple variable expansion.
Why are there no spaces in the shell?
Once again, note the avoidance of braces for a simple variable expansion. The reason you got a problem is because of the process the shell uses to construct command lines. If you read the shell manual carefully, it basically says that variables (and a few other things) get expanded THEN it goes looking for spaces.
How to handle spaces and newlines in Bash without quotes?
Without quotes, bash doesn’t handle spaces and newlines ( ) well at all… This works and is simpler: Credit to Rupa ( https://github.com/rupa/z) for this answer. In addition to proper quoting, you can tell find to use a NULL separator, and then read and process the results in a while loop
Is there a default value for IFS in Bash?
If only there was a variable whose value is a space… Or more generally, contains a space. The default value of IFS is space, tab, newline. All of these characters are whitespace. If you need a single space, you can use $ {IFS%??}. More precisely, the reason this works has to do with how word splitting works.
How are spaces and tabs divided in Bash?
1 In the operation of the shell, spaces and tabs divide text into separate words in two related but distinct ways. First, when a command is initially parsed, unquoted spaces and tabs separate lexical tokens.
Why do you use space as a delimiter in Bash?
Usually if you use space as delimiter, you want to treat multiple spaces as one, because you parse the output of a command aligning some columns with spaces. (and the google search for that lead me here)
What is the argument for some-command in Bash?
Instead, it runs some-command with foo bar as argument 1 and baz as argument 2. (There is also an argument 0, which tells a program how it was run; the shell passes some-command for that.) Using quotes enables you to tell the shell where arguments begin and end.
Are you sure the problem isn’t that your shell script is changing directory in its subshell, but then you’re back in the main shell (and original dir) when done? I avoided that by using . to run the script in the current shell, though most folks would just use an alias for this. The spaces could be a red herring.
How to change bash file path to another directory?
I’m using Bash on macOS X and I’d like to create a simple executable script file that would change to another directory when it’s run. However, the path to that directory has spaces in it. How the heck do you do this?
How to CD to directory with spaces in pathname?
Bash script to cd to directory with spaces in pathname. 1 1. Use double quotes ( “”) with your variables. Easiest way just double quotes your variables as pointed in previous answer: cd 2 2. Make use of eval.
Is there a problem with escaping bash script?
I hope that helps. Are you sure the problem isn’t that your shell script is changing directory in its subshell, but then you’re back in the main shell (and original dir) when done? I avoided that by using . to run the script in the current shell, though most folks would just use an alias for this.