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

[Srinath A. <sr...@fa...>]

Hello,

On Mon, 20 Jan 2003, Artem Chuprina wrote:

> >      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.
>
Hmm... If you are going to have to support escape backslashing, then you
might as well support only that since all compilers accept that syntax
as best as I know...

As far as escape backslashing goes, although the compiler in latex-suite
tries to do a fair bit of guessing, it still fails in the situation
where cygwin is used in a win32 environment.

You can see the latest compiler/tex.vim for latex-suite at:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vim-latex/vimfiles/compiler/tex.vim

And how to hack around the second issue at:

http://vim-latex.sourceforge.net/index.php?subject=faq#faq-2

I think that we could have improved the guesswork if we had somehow
detected whether 'shellquote' was " or '

What happens in win32 is:

- if &shell='' then cmd.exe is used and things should be called like:

    cmd.exe /c latex \nonstopmode \input{$*}

  This is because cmd.exe doesn't see \ as an escape character and it is
  passed verbatim to latex.

- if &shell=bash, then vim guesses &shellquote = '"', so that things
  need to be called like:

    bash -c "latex \\\\nonstopmode \\\\input\\{$*\\}

  Somehow there are 2 levels of escaping before this finally gets to
  latex. I know that bash will do one level. I do not know what does the
  second... (is it vim itself?)

So just to be complete, I think we'll need to also check for &shellquote
in addition to &shell. See
    :help dos-shell
for all the gory details. I might spend a little more time on this next
time I get a chance.

Ofcourse, if we just use the --interaction sytnax, we instantly take
care of all these problems. Also, in the standard compiler/tex.vim it
might be a good idea to provide an option to let the use specify the
complete command line for calling the compiler.

>
> Both are rare. Ancient TeX with vim 6.1 seems to be more rare.
>
I do not think cygwin is too rare. If its not cygwin, then its some
other winutils kind of a shell... On windows cygwin provides a great
terminal and all the familiar unix tools.

Artem:
You are welcome to join the mailing list:
    http://lists.sourceforge.net/lists/listinfo/vim-latex-devel
If you wish, take a look at the archives to get an idea of the activity
level.

Srinath