You should also learn to use the autocompletion. Most shells can do it when you press the TAB key. For example, if you are at your promp and you have written this part of the command:
Code:
rpa@rpaco-pc:~$ wine /.wine/drive_c/Program
You could then press TAB, and the shell will autocomplete the path to the next slash conveniently. This is a good habit for two reasons:
- you have to write much less.
- you ensure that the paths are correct, autocompletion can't misstype, and if you can't autocomplete, then something is already wrong.
- autocompletion takes care of escaping the spaces in the middle of paths, preventing problems like the one you are having
So, instead of the whole path, this is what I would have done:
Code:
rpa@rpaco-pc:~$ wine ~/.win[TAB]dr[TAB]Prog[TAB]Tax[TAB]/Tax[TAB]
You just need to type enough letters so the TAB autocompletion can complete the rest, enough letters to ensure that there's only one match available. Other shells, like zfs, cycle between the available matches, so you can use it even if there's more than one match. Note also that completion is configurable via /etc/bash_completion (in bash), so, if you use a command, like "wine", the autocompletion will only consider to autocomplete directories and files of the type that "wine" can open (exe, scr...). If, for example, you use mplayer, then the TAB autocompletion will only autocomplete considering media files, so, the rest of files in the directory don't get in the middle nor interfere with the autocompletion function.
It's a good thing to get familiar with this mechanism.
Linear Mode
