It may be windows has problem to handle the space in quoted parameters? write those commands to a batch file then call by mtxrun works right. May be it is a solution. :)
On Fri, Apr 10, 2009 at 3:32 PM, Aditya Mahajan
<adityam@umich.edu> wrote:
On Fri, 10 Apr 2009, Andy Wong wrote:
Yes, if leave a space between the last two quotes, mtx output seems ok.
MTXrun |
MTXrun | executing: vim -u NONE -c "set tabstop=8" "test.tex"
MTXrun |
But it still cause vim open two file named "tabstop=8" and "test.tex" to
edit. So it seems vim treat tabstop=8 as a file? that still a quotes
problem, right? I also test if there no space in quoted arguments, such as
I am beginning to suspect that it is a shell problem rather than a mtxrun problem. Mtxrun passes the correct commands and quotes to the shell, but the shell for some reason ignores that.