[Vim-latex-devel] Re: Your compiler/tex.vim plugin
Brought to you by:
srinathava,
tmaas
From: Srinath A. <sr...@fa...> - 2003-01-20 05:08:53
|
Hello Artem, I am forwarding this to the vim-latex-devel group also because it is of interest. On Sun, 19 Jan 2003, Artem Chuprina wrote: > SA> i found out that the %f flag actually looks for a valid file, i.e if its > SA> not readable then it doesnt match. therefore the 'haha' thingie broke > SA> the parsing. however, sometimes things like this do happen in actual > SA> compilation: > > SA> [10] (file1 (badness 1000) file3 ( > > For badness such a message is impossible, because it is always a part of > underfull warning message. But I tried to fit other such possibilities > (actually unknown for me). Diff is attached. I'll send it to Bram after a > little more testing, so I'll thank you if you test this patch too and send me > a bugreport if you find bugs. > > SA> where the badness warnings occur because of improber \hbox placements. > SA> the following simple thing therefore seems to work around the problem: > > SA> > 1 \%+O(%f)%r, > > SA> %O(%*[^()])%r > > as is this does not help, because in this situation it was not this O who eats > closing parenthesis (line does not begin with opening parenthesis, so O does > not match). See the diff. > Thanks! I will test this. > SA> also, another thing which you might want to do in your makeprg setting > SA> is the following: > > SA> if has('win32') > SA> set &makeprg = 'latex -interaction=nonstopmode $*' > SA> endif > > SA> this is how miktex likes it. > > Well, I discovered that teTeX likes this too, so I changed makeprg to this > version. > This might be of quite a bit of interest to the vim-latex-devel people. Benji was concerned that the -interaction=nonstopmode (I thought it was --interaction but it looks like -interaction works too for miktex) will break tex compilers and that the \\nonstopmode is a better alternative. If it is true that most if not all latex compilers can handle -interaction style syntax, it will take care of the old backslash escaping problem once and for all.. > SA> yet another thingie which broke when i used it with bash/cygwin is that > SA> external programs get executed as following: > > SA> !bash -c "latex \\nonstopmode \\input\{thesis.tex\}" > > why not > > !bash -c 'latex \\nonstopmode \\input\{thesis.tex\}' > Yes... I guess I could have changed the value of shellquote. Vim guesses 'shellquote' to be " when I do :set shell=bash in my .vimrc... Srinath |