vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

[Vim-latex-devel] [vim-latex - Help] RE: Errors with vim-latex in windows

[<no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=1780165
By: srinathava


Hello,

We would definitely love to support other locales. However, I do not have any
idea what this involves... If you could help us do it, it would be great.

For example, how do you go about getting vim to work with a chinese locale setting
on a win2k computer?

Thanks,

Srinath

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] RE: Errors with vim-latex in windows

[<no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=1780140
By: tangyuq

Thank you.

I do not change anything of gvim since I installed it(form
ftp://ftp.vim.org/pub/vim/pc/gvim61.exe, dowloaded on Dec 2, 2002)

I got it now. It is a internationalization problem.
When I change my region(locale) setting of win2k from "Chinese(PRC)" to
English(United States)", it works.

Is vim-latex supposed to support internationalization? 

Thank you.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] RE: Errors with vim-latex in windows

[<no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=1780003
By: srinathava


The vim-latex devel mailing list was incorrectly spelled. its 

vim...@li...

Thanks,
Srinath

PS: sorry to the list members for the noise.


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] RE: Errors with vim-latex in windows

[<no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=1780001
By: srinathava


Hello,

I do not get these messages at all. I have a similar set up. gvim61 on windows
2000 (no patches applied). I tested with the following minimal .vimrc:

filetype plugin on
filetype indent on
syntax on

I installed a fresh latex-suite (the same version you mention) in a new temporary
directory while testing... (maybe some other plugins are interfering?)

Could you please email a copy of your .vimrc to vim...@li....
Hopefully one of us will be able to duplicate your problem with that.

Thanks,

Srinath


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] Errors with vim-latex in windows

[<no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=1779936
By: tangyuq

I use gvim61 and Latest stable version of latexSuite zip (127.5 Kb; December
2, 2002).
I install a brand new gvim61 and extract the zip file to c:\vim\vimfiles.

When I edit a tex file, I got the following errors:
(I get them with ":messages")

Error detected while processing function <SNR>21_SafeLet:
line    6:
E15: Invalid expression:  'Underfull¡'.'Overfull¡'.'specifier changed to¡'.'You
have requested¡'.'Missing number, treated as
zero.¡'.'There were undefined references¡'.'Citation %.%# undefined¡'
E115: Missing quote: '«'
E15: Invalid expression:  '«'
E115: Missing quote: '»'
E15: Invalid expression:  '»'
Error detected while processing C:\Vim\vimfiles\compiler\tex.vim:
line   82:
E15: Invalid expression: 'Underfull¡'.'Overfull¡'.'specifier changed to¡'.'You
have requested¡'.'Missing number, treated as z
ero.'
Error detected while processing function
<SNR>33_SetLatexEfm..<SNR>33_IgnoreWarnings:
line    2:
E121: Undefined variable: g:Tex_IgnoredWarnings
E15: Invalid expression: s:Strntok(g:Tex_IgnoredWarnings, '¡', i) != '' && i
<= g:Tex_IgnoreLevel
Tear off this menu
Tear off this menu
Tear off this menu
Tear off this menu


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

[Vim-latex-devel] win32 error

[Fabio S. <fab...@ti...>]

OK, here it is the output of :messages

Error detected while processing function <SNR>22_SetTexOptions:
line 4:
unknown option

and, I'm sure about that, it DIFFERS from the real message in the last
line that includes an "and":

unknown option: and


Hope this help. Sorry for being so inaccurate before.

-- 
  Fabio Spelta
  
   email: fab...@ti...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

[Vim-latex-devel] More infos about that error

[Fabio S. <fab...@ti...>]

Too bad I've read your suggestion too late and I have launched vim 
many times to catch the whole message piece by piece. :)
It is:

Error detected while processing function: <SNR>21_SetTexOptions:

Unknown option: and


Sorry for the previous message, it does not fit a bit :)
 
-- 
  Fabio Spelta
  
   email: fab...@ti...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

[Vim-latex-devel] latex-suite and vim in utf8 (fwd)

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

Hello,

I am forwarding this to the group hoping that someone has a better idea
than I about whats going on...

The problem Andrey reports below is quite a show-stopper imo. I tried
telling him to set g:Imap_PlaceHolderStart =3D '<', but even that doesn't
work... The reason is that vim seems to do strange things with
encoding... (or I dont understand encoding very well).

Please try out the following steps:

1. open a new .vim file with encoding set to latin1.
2. type in the following stuff:

    let MyVar =3D '=AB'

    if MyVar =3D~ '=AB'
        echo 'does contain quotes'
    else
        echo 'no quotes here'
    endif

3. trying sourcing it (:so %)
    you will see 'does contain quotes'

4. now set encoding to utf8. (:set encoding=3Dutf8)

5. source it again.
    this time you will see 'no quotes here'

Could someone explain?

Thanks,

Srinath

---------- Forwarded message ----------
Date: Thu, 28 Nov 2002 15:51:49 +0600
From: Andrey R. Urazov <co...@ng...>
To: sr...@fa..., mi...@wp...
Subject: latex-suite and vim in utf8

Dear Srinath and Mikolaj,

I'm using the wonderful package latex-suite (many thanks for it) with
vim 6.1 in utf8 mode.  And I have some problems with diversified
abbreviations.  For example, when I type {} I got {=E4}=AB=BB
({<a umlaut>}<opening double quote><closing double quote>) instead.
I think the expected behavior would be typing {} and putting the cursor
between the braces, but in utf8 mode all the control sequences have lost
their special meaning and I get what I get. Think, this won't be a rare
problem since with the issue of Red Hat 8.0 many users will use utf8.

I wonder whether these macros could be rewritten avoiding control
sequences. Is it really possible?

P.S. And again thanks a lot for the package. It makes preparation of
LaTeX documents so handy!

Best regards,
  Andrey Urazov
--=20
Remember the good old days, when CPU was singular?
--
jeudi 28 novembre, 2002, 15:45:10 +0600 - Andrey R. Urazov (mailto:coola@ng=
s.ru)

Re: [Vim-latex-devel] Strange error in win32 version

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

Hello,

One way of getting the see the error again is doing:

	:messages

from the vim command prompt. That usually shows up the errors which
scrolled by too quickly.

Please let us know what the error was. You can cut and paste what
:messages shows you and we can work on it.

Thanks,

Srinath

On 1 Dec 2002, Fabio Spelta wrote:

> If I try to run vim-latex from windows XP I got an error message that
> quickly expires and I got very little time to read it.
> There is a way to make it persistent?
>
> This is what I got:  25_SetTex
>
> This pehraps tells you something? I run different versions of vim:
> 6.1.263 in Linux (where it works well) and 6.1 in winXP.
>
> Bye
> --
>   Fabio Spelta
>
>    email: fab...@ti...
>    jabber: fe...@ja...
>    ecdl project: http://ecdllibre.sf.net
>

-- 
Srinath Avadhanula
Dec 1 12:00pm
"Well, if you can't believe what you read in a comic book, what *___can*
you believe?!"
		-- Bullwinkle J. Moose [Jay Ward]

[Vim-latex-devel] Strange error in win32 version

[Fabio S. <fab...@ti...>]

If I try to run vim-latex from windows XP I got an error message that
quickly expires and I got very little time to read it.
There is a way to make it persistent?

This is what I got:  25_SetTex

This pehraps tells you something? I run different versions of vim: 
6.1.263 in Linux (where it works well) and 6.1 in winXP.

Bye
-- 
  Fabio Spelta
  
   email: fab...@ti...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

Re: [Vim-latex-devel] dvi search

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

Hello,

I have started work on a new version of the vim-latex homepage which
includes a FAQ. Most of these issues can be addressed there.

Take a look:

http://vim-latex.sourceforge.net/new/

This web-page has been made into a cvs module called htdocs. So if you
want, you can make changes to it. This question has been asked enough
times that it warrants being a FAQ.

Srinath

On Wed, 27 Nov 2002, Benji Fisher wrote:

> Mikolaj Machowski wrote:
> > Tip in the file also works for xdvi but s:CompileFlags for non-win32
> > systems is empty. You have to change line 81 in your personal texrc and
> > from '' to '--src-specials'. It works great with xdvi.
> >
> > I'd like to change it in system texrc. Any contras?
>
>       I think the default should work on almost all systems, and I am
> afraid that users with old versions of teTeX will not be able to compile
> with the --src-specials flag.  I think it is better to force the user to
> override the default in order to implement a cool feature than in order
> to fix something that does not work.
>
> 					--Benji
>

-- 
Srinath Avadhanula
Nov 27 10:27am
All programmers are playwrights and all computers are lousy actors.

Re: [Vim-latex-devel] dvi search

[Benji F. <be...@me...>]

Mikolaj Machowski wrote:
> Tip in the file also works for xdvi but s:CompileFlags for non-win32
> systems is empty. You have to change line 81 in your personal texrc and
> from '' to '--src-specials'. It works great with xdvi.
> 
> I'd like to change it in system texrc. Any contras?

      I think the default should work on almost all systems, and I am 
afraid that users with old versions of teTeX will not be able to compile 
with the --src-specials flag.  I think it is better to force the user to 
override the default in order to implement a cool feature than in order 
to fix something that does not work.

					--Benji

Re: [Vim-latex-devel] dvi search

[Mikolaj M. <mi...@wp...>]

On Fri, Nov 22, 2002 at 03:29:37PM +0000, Fabio Spelta wrote:

Sorry for lag but here are your answers :)


> Is dvi search vith \ls impossible? xdvi tells "No source specials in
> this .dvi file - couldn't perform reverse search".
> What's wrong? The help file talks only about windows and MikTex :(.

Tip in the file also works for xdvi but s:CompileFlags for non-win32
systems is empty. You have to change line 81 in your personal texrc and
from '' to '--src-specials'. It works great with xdvi.

I'd like to change it in system texrc. Any contras?

> Also, while I select "ps" as target format and all works fine (gv is
> opened as a viewer), "pdf" does not works. I got "xpdf" installed, it
> isn't the default choice?

No. Default choice is acroread which is not very popular on Linux.
I will change it for xpdf (but IMO gv is the best choice but I have to
try xpdf2).

m.
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim:
 http://vim.sourceforge.net/script.php?script_id=461

[Vim-latex-devel] xdvi -> gvim searching

[Mikolaj M. <mi...@wp...>]

Hello,

I had problem with xdvi->gvim searching (linux)
In this line:

exec '!'.s:viewer.' -editor "gvim --servername '.v:servername.'
--remote-silent +%l %f" '.mainfname.'.dvi &'

Percent signs were expanded into filenames. Was it a common thing or
only specific to me and I should not commit this:

exec '!'.s:viewer.' -editor "gvim --servername '.v:servername.'
--remote-silent +\%l \%f" '.mainfname.'.dvi &'
                 ^   ^

Second thing: IMO all calls to xdvi (or other dvi viewer) should give
possibility to back-searching. Now xdvi->gvim searching works only after
\lv, IMO it should work also after \ls. Are any contras?

Mikolaj

Re: [Vim-latex-devel] Undo

[Mikolaj M. <mi...@wp...>]

On Fri, Nov 22, 2002 at 03:02:23PM +0000, Fabio Spelta wrote:
> I got the impression that using 'u' inside latex-suite works as 'U',
> that is, undo all changes in the whole line.
> I am wrong?
> Is that a feature?
> Thank you :)

For me it works correctly ('u' as 'u' and 'U' as 'U').

Mikolaj
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim:
 http://vim.sourceforge.net/script.php?script_id=461

Re: [Vim-latex-devel] dvi search

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

Hey Fabio,

I dont really have too much experience with latex on unix. I am going to
install latex on cygwin now and see if this problem happens. But in any
case, I am pretty busy nowadays with coursework/research, so please dont
count on this being immediately taken care of unless someone else takes
care of this...

Srinath

On Fri, 22 Nov 2002, Fabio Spelta wrote:

> Is dvi search vith \ls impossible? xdvi tells "No source specials in
> this .dvi file - couldn't perform reverse search".
> What's wrong? The help file talks only about windows and MikTex :(.
>
> Also, while I select "ps" as target format and all works fine (gv is
> opened as a viewer), "pdf" does not works. I got "xpdf" installed, it
> isn't the default choice?
>
> Beg my pardon 'cause feel astonished looking at the sources and
> discovering it all by myself:)
> --
>   Fabio Spelta
>
>    email: fab...@ti...
>    jabber: fe...@ja...
>    ecdl project: http://ecdllibre.sf.net
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

[Vim-latex-devel] dvi search

[Fabio S. <fab...@ti...>]

Is dvi search vith \ls impossible? xdvi tells "No source specials in
this .dvi file - couldn't perform reverse search".
What's wrong? The help file talks only about windows and MikTex :(.

Also, while I select "ps" as target format and all works fine (gv is
opened as a viewer), "pdf" does not works. I got "xpdf" installed, it
isn't the default choice?

Beg my pardon 'cause feel astonished looking at the sources and
discovering it all by myself:)
-- 
  Fabio Spelta
  
   email: fab...@ti...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

[Vim-latex-devel] Undo

[Fabio S. <fab...@ti...>]

I got the impression that using 'u' inside latex-suite works as 'U',
that is, undo all changes in the whole line.
I am wrong?
Is that a feature?
Thank you :)
-- 
  Fabio Spelta
  
   email: fab...@ti...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

[Vim-latex-devel] ``''

[Fabio S. <fab...@ti...>]

Hi!
Now that I discovered hot to use <<>> I get addiccted. :)
Why don't add it to "" (alias ``'') too?
I will find it very confortable.

Thank you
-- 
  Fabio Spelta
  
   email: fab...@ti...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

[Vim-latex-devel] contribution

[Gabriel Z. <za...@cs...>]

Hi Srinath, Mikolaj, and Benji,

your vim-latex project is a very good idea.
Actually, I've been hacking my onw little scripts and vim macros
over the past few years myself, but, of course, they are nowhere is
comprehensive as yours.

But maybe you can steal one or the other useful piece from my scripts
and/or vim stuff, so I include them with this email.
Feel free to with it as you like.

HTH,
Gabriel.

--=20
 ________________________________________________________________________=
____

  Dr. Gabriel Zachmann              email: za...@cs...
  University Bonn                   tel. : +49 (0)228-73-4125 / -4191
  Institut fuer Informatik II       fax  : +49 (0)228-73-4212
  Roemerstra=DFe 164                  http://web.informatik.uni-bonn.de/~=
zach
  D-53117 Bonn                      http://www.gabrielzachmann.org/
 ________________________________________________________________________=
____

--=20
/---------------------------------------------------------------------\
| Unix is user-friendly  --                                           |
| it is just a bit selective about who it makes friends with.         |
|                                                                     |
| za...@cs...                 __@/'  Gab...@gm... |
| web.informatik.uni-bonn.de/~zach    __@/'   www.gabrielzachmann.org |
\---------------------------------------------------------------------/

Re: [Vim-latex-devel] running latex

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

Dear Carl,

Here's an update about the compiler part... I just had a go at adding
the kind of functionality you wanted. As I previously mentioned, I like
the quickfix window because it gives us a nice overview of the errors
and also allows us to fix the errors out of sequence. You and Benji seem
to prefer looking at the log file. Hence I made a compormize. Show both!
So here's what happens in the latest version:

-----------------------------------%<-----------------------------------
When you press \ll, then the quickfix window with one error on each line
opens up. Beneath the quickfix window, the log file is opened in a
"preview" window. The display within the preview window is adjusted to
match with the error currently being examined by the user. When the user
moves around within the quickfix window, this display is automatically
adjusted to keep in sync.

When the user presses <enter> in the quickfix window, then he is taken to
the correct line and column number of the .tex file. The column number is
computed either from the length of the broken line after l.\d\+ in the log
file or if we have a undefined citation, then search for the missing
citation word...

TODO:
1. multiple errors on the same line dont work. the preview window gets
   stuck on the first error.
2. test more robustly.
3. Ask people about various formats of LaTeX warnings, so we can guess
   column numbers in other situations too. As of now, only undefined
   citations and errors are caught well. For all other kinds, we goto the
   first column of the correct line number.
-----------------------------------%<-----------------------------------

Please try it out when you get a chance.

http://vim-latex.sourceforge.net/download/latexSuite-beta.zip

(Note: Its still "slightly" beta, but should be fixed up soon).

BTW, Mikolaj and I have also included most of your suggestions about the
environment macros. Right now, pressing <F5> in insert mode prompts for
an environment to insert... We will soon also implement a customizable
way to have <S-F1...4> map to common environments.

The bracketing polymorphic functions have been merged into latex-suite
(thanks!) as well as the ReadLine() function for splitting a line
keeping $$ in the same line...

All in all, almost all your suggestions so far have been incorporated :)
Please remind us if we have forgotten something.

Have a look,

Srinath


On Tue, 19 Nov 2002, Srinath Avadhanula wrote:

>
> Hello Carl,
>
> > I prefer automatic updating of xdvi.
> >
> Firstly, the thing where you prefer to update the xdvi thing is a
> setting problem rather than having to rewrite code. You could set
>
> g:Tex_CompileRule_dvi =3D 'xterm -bg ivory -fn 7x14 -e latex $* &'
>
> if you want the xdvi to be updated. Thats why there are all these
> customization options in latex-suite... so each person can be happy. I
> dont think its a good idea to hardcode something like this in
> latex-suite. As of now, I think this complaint/preference of yours can
> be handled completeley within the existing structure.
>
> [ NOTE: I just found out that there is bug in latex-suite which makes
>         this suggestion of mine not true... see the post-script. The bug
>         is very easy to fix and I am on it now ]
>
> Also, when you say the .log file is not updated when you have the above
> setting, thats obviously because you run the latex command in the
> background and immediately look at the log file. What about doing
> something like:
>
> g:Tex_CompileRule_dvi=3D 'xterm -bg ivory -fn 7x14 -e latex \nonstopmode =
\input{$*}; cat $*.log'
>
> That will get the xterm to quit as soon as latex finishes and you get
> the automatically updated quickfix window.
>
> I tried this out on my cygwin/xdvi/latex/xterm setup and it does work
> pretty well... (there were a few problems with  characters in the
> quickfix window, but that doesn't seem like a big deal. A matter of
> passing it through sed or something to chomp lines...)
>
> > I know people have put in a lot of work on the quickfix way of
> > displaying tex errors.  Could my suggestions be considered as
> > an option?
> >
> Also, the quickfix window does not give you as little information as you
> think... In fact, the line which you see in the quick-fix window is a
> concatenation of all lines in the log file starting from the one
> starting with '!' to the first blank line after that... I have never
> found any information about the error beyond that...
>
> About the going to the exact location thing...
>
> I personally do not like :cnext but the :cwindow method, because it lets
> me go to some arbitrary error without having to go in order. Therefore,
> the method proposed here of indenting the .log file seems not the optmal
> one. I think a solution which fits in better with the existing setup
> (and which I think will be more elegant) is to first list things in
> cwindow and if the user wants open a preview window or something... This
> should be not hard to do at all... Just a matter of having something
> like:
>
> map p :pedit ^l.10<CR>:wincmd w<CR>
>
> Anyway, setting up the compiler and making it as customizable as it
> presently is has been a continuing challenge... I would really prefer a
> solution which either everyone likes or is customizable...
>
> Thanks,
>
> Srinath
>
> PS: I just noticed that there is a bug (again) in the compiler 'makeprg'
> setup. If the user sets g:Tex_CompileRule_dvi directly in his ~/.vimrc,
> that setting is ignored until the first time he does :TCTarget dvi.
> Which is ofcourse because g:Tex_CompileRule_dvi is never used in
> compiler/tex.vim...
>
>
> N=18=AC=B1=F9=DE=B5=E9=9A=8AX=AC=B2=9A'=B2=8A=DEu=BC=BEN=89^j=B9=ED=85=E6=
=DA=B2',=A1=FB=1Er=EA=E2=9E=0C=A8=BA=BC=1En=C8=AD{=08=AD=85$=8BrX=9C=92=17=
=ABz=DA z=D6=85DA=13D=80=0B=A1=F6=93=85=AC-y'=AB=BD=EA=C2z=BBb~'

Re: [Vim-latex-devel] About folding, again

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

Hey Fabio,

Please have a short look at ftplugin/latex-suite/folding.vim if you get
some time.

Specifically, the portion in MakeTexFolds() where all the folds are
defined... I have put up a fairly comprehensive documentation there
about how to add new folding items etc. The problem right now is that
latex-suite doesn't know about the existence of \appendix as a foldable
environment... What we will need is to have all the sections/subsections
etc also end at \appendix... I will do that now.

However, I am beginning to become afraid that there is no end in sight
to this :) Do you have an idea of a "correct" way to define section
folds? For example, you might define some new command called

\myappendix

or something and put that after a \section. In this case again,
latex-suite will fold it up with the previous seciton/chapter etc... Do
you have any ideas how something like this could be avoided...

Thanks,
Srinath

On 19 Nov 2002, Fabio Spelta wrote:

> Well, the trouble is similar to the previous one.
> This time, after the last
>
> \section{title}
> blah
> blah
> blah
>
> ...I start Appendixes this way:
>
> \appendix
> \input{a1}
> \input{a2}

Re: [Vim-latex-devel] minor bug

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

Hey Fabio,

On 19 Nov 2002, Fabio Spelta wrote:

> Hi.
> Latex-suite changes the color into brackets in a different way between
> \ref and \pageref. Is that right?
>
I dont quite understand this. Could you elaborate? The curly braces
after \ref and \pageref are the same color for me... (latex-suite does
not have any syntax highlighting stuff in it...).

> Also, [OT], does anybody knows about package "nameref" ? It bring some
> trouble to me.

Sorry. I dont know anything about this.

Srinath

Re: [Vim-latex-devel] running latex

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

DQpIZWxsbyBDYXJsLA0KDQo+IEkgcHJlZmVyIGF1dG9tYXRpYyB1cGRhdGlu
ZyBvZiB4ZHZpLg0KPg0KRmlyc3RseSwgdGhlIHRoaW5nIHdoZXJlIHlvdSBw
cmVmZXIgdG8gdXBkYXRlIHRoZSB4ZHZpIHRoaW5nIGlzIGENCnNldHRpbmcg
cHJvYmxlbSByYXRoZXIgdGhhbiBoYXZpbmcgdG8gcmV3cml0ZSBjb2RlLiBZ
b3UgY291bGQgc2V0DQoNCmc6VGV4X0NvbXBpbGVSdWxlX2R2aSA9ICd4dGVy
bSAtYmcgaXZvcnkgLWZuIDd4MTQgLWUgbGF0ZXggJCogJicNCg0KaWYgeW91
IHdhbnQgdGhlIHhkdmkgdG8gYmUgdXBkYXRlZC4gVGhhdHMgd2h5IHRoZXJl
IGFyZSBhbGwgdGhlc2UNCmN1c3RvbWl6YXRpb24gb3B0aW9ucyBpbiBsYXRl
eC1zdWl0ZS4uLiBzbyBlYWNoIHBlcnNvbiBjYW4gYmUgaGFwcHkuIEkNCmRv
bnQgdGhpbmsgaXRzIGEgZ29vZCBpZGVhIHRvIGhhcmRjb2RlIHNvbWV0aGlu
ZyBsaWtlIHRoaXMgaW4NCmxhdGV4LXN1aXRlLiBBcyBvZiBub3csIEkgdGhp
bmsgdGhpcyBjb21wbGFpbnQvcHJlZmVyZW5jZSBvZiB5b3VycyBjYW4NCmJl
IGhhbmRsZWQgY29tcGxldGVsZXkgd2l0aGluIHRoZSBleGlzdGluZyBzdHJ1
Y3R1cmUuDQoNClsgTk9URTogSSBqdXN0IGZvdW5kIG91dCB0aGF0IHRoZXJl
IGlzIGJ1ZyBpbiBsYXRleC1zdWl0ZSB3aGljaCBtYWtlcw0KICAgICAgICB0
aGlzIHN1Z2dlc3Rpb24gb2YgbWluZSBub3QgdHJ1ZS4uLiBzZWUgdGhlIHBv
c3Qtc2NyaXB0LiBUaGUgYnVnDQogICAgICAgIGlzIHZlcnkgZWFzeSB0byBm
aXggYW5kIEkgYW0gb24gaXQgbm93IF0NCg0KQWxzbywgd2hlbiB5b3Ugc2F5
IHRoZSAubG9nIGZpbGUgaXMgbm90IHVwZGF0ZWQgd2hlbiB5b3UgaGF2ZSB0
aGUgYWJvdmUNCnNldHRpbmcsIHRoYXRzIG9idmlvdXNseSBiZWNhdXNlIHlv
dSBydW4gdGhlIGxhdGV4IGNvbW1hbmQgaW4gdGhlDQpiYWNrZ3JvdW5kIGFu
ZCBpbW1lZGlhdGVseSBsb29rIGF0IHRoZSBsb2cgZmlsZS4gV2hhdCBhYm91
dCBkb2luZw0Kc29tZXRoaW5nIGxpa2U6DQoNCmc6VGV4X0NvbXBpbGVSdWxl
X2R2aT0gJ3h0ZXJtIC1iZyBpdm9yeSAtZm4gN3gxNCAtZSBsYXRleCBcbm9u
c3RvcG1vZGUgXGlucHV0eyQqfTsgY2F0ICQqLmxvZycNCg0KVGhhdCB3aWxs
IGdldCB0aGUgeHRlcm0gdG8gcXVpdCBhcyBzb29uIGFzIGxhdGV4IGZpbmlz
aGVzIGFuZCB5b3UgZ2V0DQp0aGUgYXV0b21hdGljYWxseSB1cGRhdGVkIHF1
aWNrZml4IHdpbmRvdy4NCg0KSSB0cmllZCB0aGlzIG91dCBvbiBteSBjeWd3
aW4veGR2aS9sYXRleC94dGVybSBzZXR1cCBhbmQgaXQgZG9lcyB3b3JrDQpw
cmV0dHkgd2VsbC4uLiAodGhlcmUgd2VyZSBhIGZldyBwcm9ibGVtcyB3aXRo
IA0gY2hhcmFjdGVycyBpbiB0aGUNCnF1aWNrZml4IHdpbmRvdywgYnV0IHRo
YXQgZG9lc24ndCBzZWVtIGxpa2UgYSBiaWcgZGVhbC4gQSBtYXR0ZXIgb2YN
CnBhc3NpbmcgaXQgdGhyb3VnaCBzZWQgb3Igc29tZXRoaW5nIHRvIGNob21w
IGxpbmVzLi4uKQ0KDQo+IEkga25vdyBwZW9wbGUgaGF2ZSBwdXQgaW4gYSBs
b3Qgb2Ygd29yayBvbiB0aGUgcXVpY2tmaXggd2F5IG9mDQo+IGRpc3BsYXlp
bmcgdGV4IGVycm9ycy4gIENvdWxkIG15IHN1Z2dlc3Rpb25zIGJlIGNvbnNp
ZGVyZWQgYXMNCj4gYW4gb3B0aW9uPw0KPg0KQWxzbywgdGhlIHF1aWNrZml4
IHdpbmRvdyBkb2VzIG5vdCBnaXZlIHlvdSBhcyBsaXR0bGUgaW5mb3JtYXRp
b24gYXMgeW91DQp0aGluay4uLiBJbiBmYWN0LCB0aGUgbGluZSB3aGljaCB5
b3Ugc2VlIGluIHRoZSBxdWljay1maXggd2luZG93IGlzIGENCmNvbmNhdGVu
YXRpb24gb2YgYWxsIGxpbmVzIGluIHRoZSBsb2cgZmlsZSBzdGFydGluZyBm
cm9tIHRoZSBvbmUNCnN0YXJ0aW5nIHdpdGggJyEnIHRvIHRoZSBmaXJzdCBi
bGFuayBsaW5lIGFmdGVyIHRoYXQuLi4gSSBoYXZlIG5ldmVyDQpmb3VuZCBh
bnkgaW5mb3JtYXRpb24gYWJvdXQgdGhlIGVycm9yIGJleW9uZCB0aGF0Li4u
DQoNCkFib3V0IHRoZSBnb2luZyB0byB0aGUgZXhhY3QgbG9jYXRpb24gdGhp
bmcuLi4NCg0KSSBwZXJzb25hbGx5IGRvIG5vdCBsaWtlIDpjbmV4dCBidXQg
dGhlIDpjd2luZG93IG1ldGhvZCwgYmVjYXVzZSBpdCBsZXRzDQptZSBnbyB0
byBzb21lIGFyYml0cmFyeSBlcnJvciB3aXRob3V0IGhhdmluZyB0byBnbyBp
biBvcmRlci4gVGhlcmVmb3JlLA0KdGhlIG1ldGhvZCBwcm9wb3NlZCBoZXJl
IG9mIGluZGVudGluZyB0aGUgLmxvZyBmaWxlIHNlZW1zIG5vdCB0aGUgb3B0
bWFsDQpvbmUuIEkgdGhpbmsgYSBzb2x1dGlvbiB3aGljaCBmaXRzIGluIGJl
dHRlciB3aXRoIHRoZSBleGlzdGluZyBzZXR1cA0KKGFuZCB3aGljaCBJIHRo
aW5rIHdpbGwgYmUgbW9yZSBlbGVnYW50KSBpcyB0byBmaXJzdCBsaXN0IHRo
aW5ncyBpbg0KY3dpbmRvdyBhbmQgaWYgdGhlIHVzZXIgd2FudHMgb3BlbiBh
IHByZXZpZXcgd2luZG93IG9yIHNvbWV0aGluZy4uLiBUaGlzDQpzaG91bGQg
YmUgbm90IGhhcmQgdG8gZG8gYXQgYWxsLi4uIEp1c3QgYSBtYXR0ZXIgb2Yg
aGF2aW5nIHNvbWV0aGluZw0KbGlrZToNCg0KbWFwIHAgOnBlZGl0IF5sLjEw
PENSPjp3aW5jbWQgdzxDUj4NCg0KQW55d2F5LCBzZXR0aW5nIHVwIHRoZSBj
b21waWxlciBhbmQgbWFraW5nIGl0IGFzIGN1c3RvbWl6YWJsZSBhcyBpdA0K
cHJlc2VudGx5IGlzIGhhcyBiZWVuIGEgY29udGludWluZyBjaGFsbGVuZ2Uu
Li4gSSB3b3VsZCByZWFsbHkgcHJlZmVyIGENCnNvbHV0aW9uIHdoaWNoIGVp
dGhlciBldmVyeW9uZSBsaWtlcyBvciBpcyBjdXN0b21pemFibGUuLi4NCg0K
VGhhbmtzLA0KDQpTcmluYXRoDQoNClBTOiBJIGp1c3Qgbm90aWNlZCB0aGF0
IHRoZXJlIGlzIGEgYnVnIChhZ2FpbikgaW4gdGhlIGNvbXBpbGVyICdtYWtl
cHJnJw0Kc2V0dXAuIElmIHRoZSB1c2VyIHNldHMgZzpUZXhfQ29tcGlsZVJ1
bGVfZHZpIGRpcmVjdGx5IGluIGhpcyB+Ly52aW1yYywNCnRoYXQgc2V0dGlu
ZyBpcyBpZ25vcmVkIHVudGlsIHRoZSBmaXJzdCB0aW1lIGhlIGRvZXMgOlRD
VGFyZ2V0IGR2aS4NCldoaWNoIGlzIG9mY291cnNlIGJlY2F1c2UgZzpUZXhf
Q29tcGlsZVJ1bGVfZHZpIGlzIG5ldmVyIHVzZWQgaW4NCmNvbXBpbGVyL3Rl
eC52aW0uLi4NCg0KDQo=

Re: [Vim-latex-devel] running latex

[Carl M. <cm...@ma...>]

Dear Benji,

On Tue, Nov 19, 2002 at 04:52:08PM -0500, Benji Fisher wrote:
>      I am sorry, I do not have time to look at these now.  (Maybe not
> for a while ...)  Are your two scripts exclusive?  That is, can you not
> get both improvements at the same time?
> 
> 					--Benji
> 

I didn't know that one could update xdvi from within vim.
If that is possible, then one could combine the scripts.
The only differences are in the RunLatex and NextTexError
functions.

Best wishes,
Carl