I think I may not write it clear in my previous email. I run the command as
mtxrun --noquotes bin:vim -u NONE -c \set tabstop=8\ \test.tex\
which got the mtxrun output has spurious before test.tex. if omit the \
around the test.tex, like this,
mtxrun --noquotes bin:vim -u NONE -c \set
On Fri, 10 Apr 2009, Andy Wong wrote:
I think I may not write it clear in my previous email. I run the command as
mtxrun --noquotes bin:vim -u NONE -c \set tabstop=8\ \test.tex\
If you quote the filename, then it should be
mtxrun --noquotes bin:vim -u NONE -c \set tabstop=8\ \test.tex\
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,
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
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. :)
Andy
On Fri, Apr 10, 2009 at 3:32 PM, Aditya Mahajan adit...@umich.edu wrote:
On Fri, 10 Apr 2009, Andy Wong wrote:
Yes,