title: Getting bash to ignore bash keywords in a script
body: <p>I have a script in <code>bash</code> which uses the <code>HTK toolkit</code>. One of the files that the HTK tool uses is called <code>do</code> and is present within a directory called <code>hmm_1/</code>. Now, when I need to call a particular tool from within the HTK toolkit, I do it like so:  </p>
  
  <p><code>some HTK command -H hmm_1/do -H hmm_1/&lt;something else&gt;</code> and so on. I just noticed that <code>gvim</code> highlights the <code>do</code> <em>file name</em> in the above command, thinking it is a keyword. However, it is a file name. My question is:  </p>
  
  <ol>
  <li>Will bash interpret it as a keyword or does bash know better (it is just a gvim quirk).  </li>
  <li>How can I get bash to "know" that some variable names, though innocuously named like keywords are not that and are instead filenames?  </li>
  </ol>
  
  <p>Note: I cannot change the name of the file now. I will have to backtrack through a large number of steps.</p>
  
  <p>I just don't know how to phrase this question. Help in editing the question line is most welcome.</p>