I have a script in bash which uses the HTK toolkit. One of the files that the HTK tool uses is called do and is present within a directory called hmm_1/. Now, when I need to call a particular tool from within the HTK toolkit, I do it like so:
some HTK command -H hmm_1/do -H hmm_1/<something else> and so on. I just noticed that gvim highlights the do file name in the above command, thinking it is a keyword. However, it is a file name. My question is:
- Will bash interpret it as a keyword or does bash know better (it is just a gvim quirk).
- How can I get bash to “know” that some variable names, though innocuously named like keywords are not that and are instead filenames?
Note: I cannot change the name of the file now. I will have to backtrack through a large number of steps.
I just don’t know how to phrase this question. Help in editing the question line is most welcome.
As part of a path, keywords will be ignored. They will only be interpreted as a keyword at the beginning of a command. It would be best to simply consider
gvim‘s highlighting to be a minor annoyance and ignore it.