Re: [Vim-latex-devel] Re: Your compiler/tex.vim plugin

[Artem C. <ra...@ra...>]

On 2003.01.20 at 09:01:56 -0500, Benji Fisher wrote:

> >>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..
> 
>      Just yesterday, I updated teTeX on my Linux system, with the 
> latest RPM's from Red Hat, and now tex understands the -interaction 
> option.  I still think that a lot of people are using older 
> distributions of tex.  It has been a long time since there was an 
> official release of teTeX.  True, a lot of people have switched to the 
> beta version, which supportsd this option; in fact, I am not sure which 
> version is in the RPM I downloaded.  If this is the only place where 
> escaping backslashes is an issue, and that is still causing problems, 
> then it is a judgment call.
> 
>      For someone using an old version of tex, how hard will it be to 
> fix the problem if the default is changed?

I hope that this compiler was in vim not so much time that this is an issue.
But I know many people who use old emTeX under Win32. So I am going to support
\nonstopmode as a fallback for them, but I need to resolve backslash escaping
issues.

> >>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
> 
>      Is there any way to guess which is more common:  ancient versions 
> of tex or cygwin installations?

Both are rare. Ancient TeX with vim 6.1 seems to be more rare.

-- 
Artem Chuprina (Ran)
RFC2822: <ra...@ra...>, FIDO: 2:5020/358.49