> I have three different machines with a score-writing package on, and
> on two of the three I can run the "compile" equivalent to create
> PostScript output with
> !mup -F %
>
> On the third, I hit the following snag:
>
> !mup {fname} reports /bin/bash: mup: command not found
>
>> which mup reports "/usr/local/bin/mup-5.7/bin"
> /usr/local/bin/mup-5.7/bin is the last entry in $PATH
Strange: "which mup" should include mup at the end, something like
/usr/local/bin/mup-5.7/bin/mup
If that's the case, check what $PATH are set to in the shell and
from within Vim. The same command works in both:
bash$ echo $PATH
:echo $PATH
They *should* be the same, but perhaps for some reason it's
getting tweaked before you go into vim.
Also, make sure that you can execute an unqualified "mup" on the
command-line, removing vim from the picture.
Lastly, if it works unqualified from the command-line, I'd check
for any aliases that are silently interfering.
At least that's where I'd start...
-tim
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment