To avoid the problems you noted with the spaces it seems always a good practice to NOT use spaces in file or directory names. You also should also avoid any other special characters that the shell interprets as other than literal.
I noted that in the post above you even have a directory name that ends in a whitespace character 'Typora ' which would make it difficult to understand why a command such as rsync -av Typora <destination> would not work.
Yes your right I’ll take that onboard from now on that a better way to file docs thanks for the tip. Interesting though I didn’t specify those quotation dashes on the typora folder, in bash that symbolises something I believe
Any time you use ‘ls’, the output of file & directory names containing white space or other non-printable characters will be automatically quoted. Thus you can easily see those file names that require special handling for other commands.
Those of us that have been using linux and other unix like systems for 20+ years are very aware of these issues. Those coming from windows have been spoiled by the relaxed way that windows has for file names with white space and are not habitually trained to avoid the white spaces. The bash shell sees a white space as a word separator and the code below will fail with file names containing spaces.
for file in *.mpeg ; do
mv $file $file.mpg
done
This shows it clearly
$ touch file1.mpeg 'file 2.mpeg'
$ ls
file1.mpeg 'file 2.mpeg'
$ for file in *.mpeg; do mv $file $file.mpg; done
mv: target '2.mpeg.mpg' is not a directory
$ ls
file1.mpeg.mpg 'file 2.mpeg'
I’m embarrassed to ask but it there a recommended literature in the Fedora documentation or somewhere I can learn the proper syntax’s for BASH. I know this is assumed knowledge so its probably better to do a short course perhaps
Even with a bit of experience I use this. It covers everyone, from the novice through the expert, and is an excellent reference for us all to have on our bookshelf. https://tldp.org/LDP/abs/html/
