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

Re: [Vim-latex-devel] Changing the makeindex program to another

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

On Sat, 5 Jun 2004, Berta Milan wrote:

> Hi! I am going to be short: How can I change the program
> 'makeindex' to another program (I want to use program
> 'csindex' instead)?

As of now, this is unfortunately, not customizable. In the future, this
will be a settable thing. for now, how about making a copy of csindex
and call it makeindex?

Srinath

[Vim-latex-devel] Changing the makeindex program to another

[Berta M. <ber...@ar...>]

Hi! I am going to be short: How can I change the program
'makeindex' to another program (I want to use program
'csindex' instead)?

Milan

[Vim-latex-devel] [Contact] one letter words and \"~\"

[Vladimir <vim...@so...>]

Can you add support for automatic placing of  

\"~\" after one-letter words ?  

  

[Vim-latex-devel] [Contact] Thanks!

[David T. <vim...@so...>]

I just wanted to say thanks for this plugin - it makes latex editing a complete joy. Keep 
up the great work!



-David  

Re: [Vim-latex-devel] [Contact] Word Completion

[Berta M. <ber...@ar...>]

I think that the one solution is the use of ^n (ctrl-n)and
^p (ctrl-p) in insert mode (vim command, not latex-suite).

:help i_^n
:help i_^p

Milan

On Wed, Jun 02, 2004 at 07:50:14AM -0700, LiYang wrote:
> 
> I want to know how to complete a word or a LaTeX command, e.g. \\mathbf.  
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] [Contact] Word Completion

[LiYang <vim...@so...>]

I want to know how to complete a word or a LaTeX command, e.g. \\mathbf.  

Re: [Vim-latex-devel] grep

[Berta M. <ber...@ar...>]

On Tue, Jun 01, 2004 at 12:46:50PM -0700, Srinath Avadhanula wrote:
> On Tue, 1 Jun 2004, Berta Milan wrote:
> 
> > On Sun, May 30, 2004 at 02:54:05PM +0200, Berta Milan wrote:
> > the lower ones after
> >
> > :call Tex_PrintDebug('view')
> >
> > immediately after <F9>
> >
> > <begin of output of :call Tex_PrintDebug('view')>
> >
> > s:type = ref, typeoption =
> > silent! grep! '\\label{' *.tex
> > +Tex_SetupCWindow
> > +Tex_SyncPreviewWindow
> > Tex_SyncPreviewWindow: got error E32, no matches found, quitting
> > not in quickfix window, quitting
> >
> 
> This is strange! In yesterday's email you said that you had the latest
> version of latex-suite, but this debug message seems to imply that you
> have a pretty old version. I meant to download the latest developement
> version, not the latest 1.5 release.
> 
> When I try this, I see something like:
> 
> -----------------------%<-----------------------
> texviewer.vim: Catching LatexSuiteFileType event
> Tex_Complete: s:type = ref, typeoption =
> Tex_Complete: calling Tex_GrepHelper
> +Tex_ScanFileForLabels: grepping in file [b.tex]
> +Tex_SetupCWindow
> +Tex_SyncPreviewWindow
> -----------------------%<-----------------------
> 
> Please make sure you have the latest version!
> 
> Srinath

I downloaded the latest version [2004/05/24] finally. Now
I can see the similar output as yours (after :call
Tex_PrintDebug('view')).  And also the completition (<F9>)
works the way that I want (so I get the windows with all
\label{...}s). Thanks You very much!

I send additional information about the error output after
pressing <F9>:

The first run of <F9>:

<begin>

Error running function Tex_Complete..Tex_GrepHelper..Tex_ScanFileForLabels..Tex_ScanFileForLabels:
line 28:
E121: Variable not defined: foundCiteFile
E121: Variable not defined: foundCiteFile
E15: Bad expression: foundCiteFile

<end>

All other runs of <F9>:

<begin>

E121: Variable not defined: foundCiteFile
E121: Variable not defined: foundCiteFile
E15: Bad expression: foundCiteFile

<end>

Now (if there is some \label{}) the window with \label{}s
open.

Milan

Re: [Vim-latex-devel] grep

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

On Tue, 1 Jun 2004, Berta Milan wrote:

> On Sun, May 30, 2004 at 02:54:05PM +0200, Berta Milan wrote:
> the lower ones after
>
> :call Tex_PrintDebug('view')
>
> immediately after <F9>
>
> <begin of output of :call Tex_PrintDebug('view')>
>
> s:type = ref, typeoption =
> silent! grep! '\\label{' *.tex
> +Tex_SetupCWindow
> +Tex_SyncPreviewWindow
> Tex_SyncPreviewWindow: got error E32, no matches found, quitting
> not in quickfix window, quitting
>

This is strange! In yesterday's email you said that you had the latest
version of latex-suite, but this debug message seems to imply that you
have a pretty old version. I meant to download the latest developement
version, not the latest 1.5 release.

When I try this, I see something like:

-----------------------%<-----------------------
texviewer.vim: Catching LatexSuiteFileType event
Tex_Complete: s:type = ref, typeoption =
Tex_Complete: calling Tex_GrepHelper
+Tex_ScanFileForLabels: grepping in file [b.tex]
+Tex_SetupCWindow
+Tex_SyncPreviewWindow
-----------------------%<-----------------------

Please make sure you have the latest version!

Srinath

[Vim-latex-devel] Change of s:smartBS_pat

[Berta M. <ber...@ar...>]

I have changed the s:smartBS_pat in my
ftplugin/latex-suite/main.vim. I think that this extension
is better. It includes deleting (as one character) the
following accents (in brackets are examples): \H{}
(Hungarian =FB=DB=F5=D5), \r{} (Czech =F9=D9), \c{} (=E7=C7=BA=AA=FE=DE),=
 \u{} (=E3=C3),
\k{} (=B1=A1=EA=CA) and \.{} (=BF=AF).

The way that I changed it:

let s:smartBS_pat =3D '\(' .
	\ "\\\\[\"^'=3D.ckHruv]{\\S}"      . '\|' .
	\ "\\\\[\"^'=3D.]\\S"         . '\|' .
	\ '\\[vurkHc] \S'                 . '\|' .
	\ "\\\\[\"^'=3Dv]{\\\\[iI]}" . '\|' .
	\ '\\v \\[iI]'             . '\|' .
	\ '\\q \S'                 . '\|' .
	\ '\\-'                    .
	\ '\)' . "$"

(Note: The old definition was:

let s:smartBS_pat =3D '\(' .
		\ "\\\\[\"^'=3Dv]{\\S}"      . '\|' .
		\ "\\\\[\"^'=3D]\\S"         . '\|' .
		\ '\\v \S'                 . '\|' .
		\ "\\\\[\"^'=3Dv]{\\\\[iI]}" . '\|' .
		\ '\\v \\[iI]'             . '\|' .
		\ '\\q \S'                 . '\|' .
		\ '\\-'                    .
		\ '\)' . "$"

)

And my question is: Is there any way to change s:smartBS_pat
(to define it) except changing the mentioned
ftplugin/latex-suite/main.vim? For example, to write it in
my .vimrc file?

Milan

Re: [Vim-latex-devel] grep

[Berta M. <ber...@ar...>]

On Sun, May 30, 2004 at 02:54:05PM +0200, Berta Milan wrote:
> On Sat, May 29, 2004 at 11:44:35PM -0700, Srinath Avadhanula wrote:
> > Could you please let me know when was the last time you downloaded
> > latex-suite? If it was a while ago, try with the latest release.
> > Infact try with the latest release just to make sure we are all on the
> > same page.
> 
> OK, I downloaded the (newest) version 1.5 of LaTeX-Suite.
> I am using gvim 6.2 on WinXP.
> 
> > On Sat, 29 May 2004, Berta Milan wrote:
> > 
> > > 1) I have problem with completition, <F9>. I use grep
> > >    program mentioned in FAQ. I installed it, it works on
> > > command-line (DOS console) from every directory in my
> > > computer with path "c:\progra~1\gnuwin32\bin\grep" and
> > > option "-nH" very well, I used to compare the grep output on
> > > the same file(s) using
> > > Linux, they were totally identical.
> > >
> > > In my _vimrc there stays
> > >
> > > 	set grepprg=c:\progra~1\gnuwin32\bin\grep.exe\ -nH\ $*
B
> > >
> > > But nothing happens if I stay in \ref{}, in INSERT mode of
> > > course.
> > 
> > Try putting:
> >     :let g:Tex_Debug = 1
> > 
> > And after pressing <F9> from between the braces of a \ref{} tell me what
> >     :call Tex_PrintDebug('view')
> > 
> > says. That should give a clue as to what latex-suite is trying to do and
> > what is not working.
> 
> My gvim automatically use czech language (probably because
> of czech WinXP :) so I try to translate the output:
> 
> <begin of output>
> 
> Error processing function TeX_Complete..<SNR>45_Tex_SetupCWindow..Tex_Debug:
> line 13:
> E121: Variable not defined: s:debugString_
> E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
> Error processing function TeX_Complete..<SNR>45_Tex_SetupCWindow..<SNR>45_Tex_SyncPreviewWindow..Tex_Debug:
> line 13:
> E121: Variable not defined: s:debugString_
> E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
> No bibkey, label or word begging with ""
> E121: Variable not defined: s:debugString_
> E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
> Error processing function TeX_Complete..<SNR>45_Tex_SetupCWindow..Tex_Debug:
> line 13:
> E121: Variable not defined: s:debugString_
> E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
> Press ENTER....
> 
> <end of output>
> 
> Hopping this is the mirror of my output and no line wrap
> (error output should contains 15 lines, 16th is "Press
> ENTER...").  Some lines are the same, so it was not a hard
> work :) Than I press ENTER and nothing happens.
> 
> Milan

I've misunderstood Your message. So the upper several lines
are written by gvim only after pressing 

<F9>

the lower ones after

:call Tex_PrintDebug('view')

immediately after <F9>

<begin of output of :call Tex_PrintDebug('view')>

s:type = ref, typeoption =
silent! grep! '\\label{' *.tex
+Tex_SetupCWindow
+Tex_SyncPreviewWindow
Tex_SyncPreviewWindow: got error E32, no matches found, quitting
not in quickfix window, quitting

<end of output of :call Tex_PrintDebug('view')>

My mistake, sorry.

As I mentioned, I use 'grep.exe', same output as grep on
Linux with the same file(s). The latest test I made with
grep within the directory with
	set grepprg=grep\ -nH\ $*
in my _vimrc file.

Milan

Re: [Vim-latex-devel] Ignore undefined font warnings

[Aditya M. <adi...@al...>]

>>> On May 31, Vaidotas Zemlys wrote

> Hi,
>
>>  Is there some way to ignore the undefined font warnings like
>> 
>> LaTeX Font Warning: Font shape `OT1/cmss/m/it' in size <9> not available
>> 
>> from appearing in the error list. I know that there is an option of 
>> setting the ignore level, but font warnings are not included in it. How 
>> can I add them to the ignore list. I want them between the Overfull and 
>> specifier changed to levels.
>> 
>
> I have such lines in my texrc file:
> TexLet g:Tex_IgnoredWarnings =
> 	\'Underfull'."\n".
> 	\'Overfull'."\n".
> 	\'specifier changed to'."\n".
> 	\'You have requested'."\n".
> 	\'Missing number, treated as zero.'."\n".
> 	\'There were undefined references'."\n".
> 	\'LaTeX Font Warning:'."\n".
> 	\'Citation %.%# undefined'
> " the 'ignore level' of the 'efm'. A value of 4 says that the first 4 kinds 
> of
> " warnings in the list above will be ignored. Use the command TCLevel to set 
> a
> " level dynamically.
> TexLet g:Tex_IgnoreLevel = 7
>
> And I do not see LaTeX font warnings you mentioned.
>

Thank you. This works perfectly.

Aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

Re: [Vim-latex-devel] Ignore undefined font warnings

[Vaidotas Z. <v.z...@po...>]

Hi,

>  Is there some way to ignore the undefined font warnings like
>=20
> LaTeX Font Warning: Font shape `OT1/cmss/m/it' in size <9> not available
>=20
> from appearing in the error list. I know that there is an option of setti=
ng =20
> the ignore level, but font warnings are not included in it. How can I add=
 =20
> them to the ignore list. I want them between the Overfull and specifier =
=20
> changed to levels.
>

I have such lines in my texrc file:
TexLet g:Tex_IgnoredWarnings =3D
	\'Underfull'."\n".
	\'Overfull'."\n".
	\'specifier changed to'."\n".
	\'You have requested'."\n".
	\'Missing number, treated as zero.'."\n".
	\'There were undefined references'."\n".
	\'LaTeX Font Warning:'."\n".
	\'Citation %.%# undefined'
" the 'ignore level' of the 'efm'. A value of 4 says that the first 4 kinds=
 of
" warnings in the list above will be ignored. Use the command TCLevel to se=
t a
" level dynamically.
TexLet g:Tex_IgnoreLevel =3D 7

And I do not see LaTeX font warnings you mentioned.

Mpiktas

[Vim-latex-devel] Ignore undefined font warnings

[Aditya M. <adi...@al...>]

Hi,
  Is there some way to ignore the undefined font warnings like

LaTeX Font Warning: Font shape `OT1/cmss/m/it' in size <9> not available

from appearing in the error list. I know that there is an option of 
setting the ignore level, but font warnings are not included in it. 
How can I add them to the ignore list. I want them between the 
Overfull and specifier changed to levels.

Thanks
Aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

Re: [Vim-latex-devel] grep, and bug(?)

[Berta M. <ber...@ar...>]

On Sat, May 29, 2004 at 11:44:35PM -0700, Srinath Avadhanula wrote:
> Could you please let me know when was the last time you downloaded
> latex-suite? If it was a while ago, try with the latest release.
> Infact try with the latest release just to make sure we are all on the
> same page.

Ok, I downloaded the (newest) version 1.5 of LaTeX-Suite.
I am using gvim 6.2 on WinXP.

> On Sat, 29 May 2004, Berta Milan wrote:
> 
> > 1) I have problem with completition, <F9>. I use grep
> >    program mentioned in FAQ. I installed it, it works on
> > command-line (DOS console) from every directory in my
> > computer with path "c:\progra~1\gnuwin32\bin\grep" and
> > option "-nH" very well, I used to compare the grep output on
> > the same file(s) using
> > Linux, they were totally identical.
> >
> > In my _vimrc there stays
> >
> > 	set grepprg=c:\progra~1\gnuwin32\bin\grep.exe\ -nH\ $*
> >
> > But nothing happens if I stay in \ref{}, in INSERT mode of
> > course.
> 
> Try putting:
>     :let g:Tex_Debug = 1
> 
> And after pressing <F9> from between the braces of a \ref{} tell me what
>     :call Tex_PrintDebug('view')
> 
> says. That should give a clue as to what latex-suite is trying to do and
> what is not working.

My gvim automatically use czech language (probably because
of czech WinXP :) so I try to translate the output:

<begin of output>

Error processing function TeX_Complete..<SNR>45_Tex_SetupCWindow..Tex_Debug:
line 13:
E121: Variable not defined: s:debugString_
E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
Error processing function TeX_Complete..<SNR>45_Tex_SetupCWindow..<SNR>45_Tex_SyncPreviewWindow..Tex_Debug:
line 13:
E121: Variable not defined: s:debugString_
E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
No bibkey, label or word begging with ""
E121: Variable not defined: s:debugString_
E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
Error processing function TeX_Complete..<SNR>45_Tex_SetupCWindow..Tex_Debug:
line 13:
E121: Variable not defined: s:debugString_
E15: Bad expression:  s:debugString_.pattern.' : '.a:str."\n"
Press ENTER....

<end of output>

Hopping this is the mirror of my output and no line wrap
(error output should contains 15 lines, 16th is "Press
ENTER...").  Some lines are the same, so it was not a hard
work :) Than I press ENTER and nothing happens.

Milan

Re: [Vim-latex-devel] grep, and bug(?)

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

Could you please let me know when was the last time you downloaded
latex-suite? If it was a while ago, try with the latest release.
Infact try with the latest release just to make sure we are all on the
same page.

On Sat, 29 May 2004, Berta Milan wrote:

> 1) I have problem with completition, <F9>. I use grep
>    program mentioned in FAQ. I installed it, it works on
> command-line (DOS console) from every directory in my
> computer with path "c:\progra~1\gnuwin32\bin\grep" and
> option "-nH" very well, I used to compare the grep output on
> the same file(s) using
> Linux, they were totally identical.
>
> In my _vimrc there stays
>
> 	set grepprg=c:\progra~1\gnuwin32\bin\grep.exe\ -nH\ $*
>
> But nothing happens if I stay in \ref{}, in INSERT mode of
> course.

Try putting:
    :let g:Tex_Debug = 1

And after pressing <F9> from between the braces of a \ref{} tell me what
    :call Tex_PrintDebug('view')

says. That should give a clue as to what latex-suite is trying to do and
what is not working.

> 2) I write
>
> <begin writting>
> \begin{array}
> <end writting>
>
> <begin writting>
> \begin{array}
> \end{<++>}
> <end writting>

This is a bug. I can reproduce it. I'll let you know as soon as I find
a fix. In the meanwhile, the recommended way of entering environments in
latex-suite is to type

array<F5>

This will automatically get converted to

\begin{array}[<+position+>]{<+format+>}
<++>
\end{array}<++>

Srinath

[Vim-latex-devel] grep, and bug(?)

[Berta M. <ber...@ar...>]

1) I have problem with completition, <F9>. I use grep
   program mentioned in FAQ. I installed it, it works on
command-line (DOS console) from every directory in my
computer with path "c:\progra~1\gnuwin32\bin\grep" and
option "-nH" very well, I used to compare the grep output on
the same file(s) using
Linux, they were totally identical.

In my _vimrc there stays

	set grepprg=c:\progra~1\gnuwin32\bin\grep.exe\ -nH\ $*

But nothing happens if I stay in \ref{}, in INSERT mode of
course.

Has anybody an idea where's my mistake?


2) I write

<begin writting>
\begin{array}
<end writting>

than I want to close environment so I continue

<begin writting>
\begin{array}
	\end{
<end writting>

The tab appears, it's ok, but when I close curly brackets, such
thing happens:

<begin writting>
\begin{array}
\end{<++>}
<end writting>

and the cursor is on the end of line. I am awaiting

<begin writting>
\begin{array}
\end{}<++>
<end writting>

with the cursor between curly brackets
Is this a bug?


Milan Berta

Re: [Vim-latex-devel] minor bug in compiler.vim

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

Hi Vaidotas,

On Mon, 24 May 2004, Vaidotas Zemlys wrote:

> syntax error: the condition in if sentence misses &&. When vim parses the
> function it chokes. This results in not setting up dvi viewer properly, so you
> can not view dvi's in latexsuite. It affects only Linux.
>
Thanks for catching this. Its fixed in CVS and should also be released
very soon.

-- 
Srinath

[Vim-latex-devel] minor bug in compiler.vim

[Vaidotas Z. <v.z...@po...>]

Hi,

There is a minor bug in compiler.vim in TeX_ViewLateX function in 20040521
latexsuite version. I have attached a patch which fixes it. It's a simple
syntax error: the condition in if sentence misses &&. When vim parses the
function it chokes. This results in not setting up dvi viewer properly, so you
can not view dvi's in latexsuite. It affects only Linux.

Mpiktas

PS Resending with addres subscribed to list, if you get 2 copies ignore one,  
if you don't ignore this ps.

Re: [Vim-latex-devel] [Contact] Save before compilation?

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

On Fri, 21 May 2004, Michael Scharkow wrote:

>
> compilation with \\ll . In fact, I don\'t know why I would want my document not to be
> saved before it\'s latexed. Is there a simple way to add a save hook before
> compilation?
>

Yes... Add the following to your ~/.vim/ftplugin/tex.vim

nmap <buffer> <leader>ll :w<cr><Plug>Tex_Compile

Srinath

[Vim-latex-devel] [Contact] Save before compilation?

[Michael S. <vim...@so...>]

Hi *,

I just started using vimLaTeX and I am pretty impressed so far, but one simple 
feature I am currently missing is that I\'d like my document to be saved BEFORE 
compilation with \\ll . In fact, I don\'t know why I would want my document not to be 
saved before it\'s latexed. Is there a simple way to add a save hook before 
compilation?



Greets,

Michael  

Re: [Vim-latex-devel] Opening file with acrord in windows

[Aditya M. <adi...@al...>]

>>> On May 20, Srinath Avadhanula wrote

> On Thu, 20 May 2004, Aditya Mahajan wrote:
>
>> On May 20, Srinath Avadhanula wrote
>>> I never really like acroread. It seems to lock the file so that you
>>> cannot update the pdf file while its being viewed by acrord. That is too
>>> much of a pain...
>>>
>>
>> I managed to find the solution of both the problems in a single shot.
>> fptex distributes pdfopen.exe and pdfclose.exe as part of its
>> bin-pdftools package. What one can do is ALWAYS open a file with
>>
>>    pdfopen --file filename.pdf
>>
> That seems like a useful tool. I'll take a look at it sometime.
>
> In the meanwhile, it looks like this...
>
>> closing transparent to me. So I tried something like this
>>
>> TexLet g:Tex_CompileRule_pdf = 'pdfclose --file $*.pdf & pdflatex -interaction=nonstopmode $* &pdfopen --file $*.pdf'
>>
>> but when the latex file has some errors, I do not see them in the
>> error window.
>
> ...has an easy solution. What latex-suite does (via gvim's :make
> mechanism) is to redirect the output of the Tex_CompileRule_pdf command
> to a temporary file and then parse then according to the 'efm' setting.
> Since you string a series of commands via cmd.exe's & mechanism, only
> the output from the last command is piped to the temporary file. This
> means that gvim is never able to see pdflatex's output.
>
> An easy fix is to do
>
> let g:Tex_CompileRule_pdf =
>    \ 'pdfclose --file $*.pdf & '.
>    \ 'pdflatex -interaction=nonstopmode $* & '.
>    \ 'pdfopen --file $*.pdf &'.
>    \ 'type $*.log'
>


This is brilliant and works perfectly.

> (Why are you using TexLet? You should simply use :let to provide options
> in either ~/.vim/ftplugin/tex.vim)

I had just copied texrc to ftplugin/tex/texrc. I remember having read 
that somewhere a long time back. That is why I have TexLet rather than 
let:. Is this a bad idea?

>
> This basically prints the log file as the last command so that gvim is
> able to see the output of pdflatex. (This is assuming pdflatex produces
> a .log file like latex does).
>

This works perfectly.

Thanks a lot

aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

Re: [Vim-latex-devel] Opening file with acrord in windows

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

On Thu, 20 May 2004, Aditya Mahajan wrote:

> On May 20, Srinath Avadhanula wrote
> > I never really like acroread. It seems to lock the file so that you
> > cannot update the pdf file while its being viewed by acrord. That is too
> > much of a pain...
> >
>
> I managed to find the solution of both the problems in a single shot.
> fptex distributes pdfopen.exe and pdfclose.exe as part of its
> bin-pdftools package. What one can do is ALWAYS open a file with
>
>    pdfopen --file filename.pdf
>
That seems like a useful tool. I'll take a look at it sometime.

In the meanwhile, it looks like this...

> closing transparent to me. So I tried something like this
>
> TexLet g:Tex_CompileRule_pdf = 'pdfclose --file $*.pdf & pdflatex -interaction=nonstopmode $* &pdfopen --file $*.pdf'
>
> but when the latex file has some errors, I do not see them in the
> error window.

...has an easy solution. What latex-suite does (via gvim's :make
mechanism) is to redirect the output of the Tex_CompileRule_pdf command
to a temporary file and then parse then according to the 'efm' setting.
Since you string a series of commands via cmd.exe's & mechanism, only
the output from the last command is piped to the temporary file. This
means that gvim is never able to see pdflatex's output.

An easy fix is to do

let g:Tex_CompileRule_pdf =
    \ 'pdfclose --file $*.pdf & '.
    \ 'pdflatex -interaction=nonstopmode $* & '.
    \ 'pdfopen --file $*.pdf &'.
    \ 'type $*.log'

(Why are you using TexLet? You should simply use :let to provide options
in either ~/.vim/ftplugin/tex.vim)

This basically prints the log file as the last command so that gvim is
able to see the output of pdflatex. (This is assuming pdflatex produces
a .log file like latex does).

HTH
Srinath

Re: [Vim-latex-devel] Opening file with acrord in windows

[Aditya M. <adi...@al...>]

On May 20, Srinath Avadhanula wrote
>
> I would think that in this case, till the bug(?) somehow gets worked out
> in latex-suite, it might be simpler to make a little bat file which
> appends the present directory to the filename and calls acrord32 on
> that. Then you could point Tex_ViewRule_pdf to that. It will be pretty
> trivial to do if you have cygwin. Then it could be a little python
> scriptlet.
>


> I never really like acroread. It seems to lock the file so that you
> cannot update the pdf file while its being viewed by acrord. That is too
> much of a pain...
>

I managed to find the solution of both the problems in a single shot.
fptex distributes pdfopen.exe and pdfclose.exe as part of its 
bin-pdftools package. What one can do is ALWAYS open a file with

   pdfopen --file filename.pdf

by changing g:Tex_ViewRule_pdf = 'pdfopen --file' and change the 
Tex_CompileRule_pdf to 'pdfclose --file $* & pdflatex 
-interaction=nonstopmode $*'

Now a file that was opened by pdfopen can be closed by pdfclose. So if 
you are always using gvim to launch acrobat while working on a 
latex project (as I often do), the pdf is opened by pdfopen and when 
you want to compile it again, it first closes the pdf file if it is 
open and then compiles it. May take a fraction of a second longer to 
execute, but all this happens in the background and you never getting 
the nagging error, unable to write to pdf file, enter another 
filename:

You can use pdfopen and pdfclose, even with Miktex, just need to 
download the binaries of bin-pdftools from the fptex site.

But what is little frustating in this approach is that I have to 
open the pdf file every time I compile. I want gvim to open the file 
again in the viewer, thereby keeping the whole process of opening and 
closing transparent to me. So I tried something like this

TexLet g:Tex_CompileRule_pdf = 'pdfclose --file $*.pdf & pdflatex -interaction=nonstopmode $* &pdfopen --file $*.pdf'

but when the latex file has some errors, I do not see them in the 
error window. I understand why this happens, but is there some method 
of avoiding this, something like

nmap <leader>ll call to my_tex_compile<CR>

where
function my_tex_compile
"does something like
call original_tex_compile
if (target=pdf)&&(no errors in compiling)
call view_pdf
end

Is something like this possible?

Thanks
aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

Re: [Vim-latex-devel] Opening file with acrord in windows

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

On Thu, 20 May 2004, Aditya Mahajan wrote:

> I get an error saying "There was an error opening the document. The
> file cannot be found". I have tested this on three systems, all
> windows XP and acrobat reader 6.0. Maybe this is a bug that crept into
> acrobat reader in the latest version :-(

Must be... I did try closing the document without closing adobe etc and
it still worked on my system...

I would think that in this case, till the bug(?) somehow gets worked out
in latex-suite, it might be simpler to make a little bat file which
appends the present directory to the filename and calls acrord32 on
that. Then you could point Tex_ViewRule_pdf to that. It will be pretty
trivial to do if you have cygwin. Then it could be a little python
scriptlet.

I never really like acroread. It seems to lock the file so that you
cannot update the pdf file while its being viewed by acrord. That is too
much of a pain...

Srinath

Re: [Vim-latex-devel] Opening file with acrord in windows

[Aditya M. <adi...@al...>]

>>> On May 20, Srinath Avadhanula wrote

> On Wed, 19 May 2004, Aditya Mahajan wrote:
>
>>   It turns out that the error occurs because acrobat reader does not
>> recognize the directory from which it was launched. This is easy to
>> see. CD to a directory having a pdf file, say test.pdf and on command
>> prompt type
>> acrord32 file.pdf
>
> This is pretty strange. On my system (windows XP + Adobe Acrobat Reader
> 5.0), if I have the reader open (but without the file) and if I issue
> a command like
>
>    AcroRd32 file.pdf
>
> from a command prompt after cd'ing to the directory containing the file,
> Acrobat does correctly launch the file...
>

I also found this to be strange. In my system (Windows XP + Acrobat 
Reader 6.0) when I cd to a directory containing a pdf file and issue a 
command

  acrord32 file.pdf

acrobat reader correctly shows the file. Now if I close the file 
(without closing acrobat reader) and again issue the same command on 
the command prompt

  acrord32 file.pdf

I get an error saying "There was an error opening the document. The 
file cannot be found". I have tested this on three systems, all 
windows XP and acrobat reader 6.0. Maybe this is a bug that crept into 
acrobat reader in the latest version :-(


>> Note that I have changed "%:p:t:r" to "%:p:r" so that mainfname points
>> to the complete path of the file.
>>
>> Now \lv calls
>>   :!start Acrord32 "complete_path_to_file/file.pdf"
>> and the file shows correctly. Also the filename is surrounded with
>> quotes, so everything should be fine.
>>
>
> Unfortunately, there are a LOT of issues when doing this. For one,
> enclosing the file name in quotes doesn't work on some systems when the
> the actual shell command is interpreted by bash or similar which quotes
> the command... Escaping on the other hand works in *nix but not on
> windows...
>
How about something like
if has('win32')
  something
else
  something else
endif

I know that this will unnecessarily complicate the code. So if you do 
not want to include it in the main branch, I will simply make a change 
in my local files.

Aditya