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

[Vim-latex-devel] Windows help

[Daniel S. <dsu...@gm...>]

Firstly, I apologize for any breach of etiquette. This is my first developer
mailing list.

 

I am trying to go through the quickstart guide and have gotten stuck with
the auto completion step (page 7). I copy pasted the document into VIM to
ensure there were no errors and added the line in the reference step as
instructed. When I hit F9 with the cursor between the brackets, a new buffer
opens as expected but the text reads:

 

' 'C:' is not recognized as an internal or external command,

operable program or batch file.

 

I verified that Vim is compiled with both Python and Python3. I also put the
grep.exe into my PATH from the recommended repository mentioned in the FAQ.
I verified that Windows recognizes 'grep' as a valid command from the
terminal. I'm not sure if it is relevant, but I have also added "set
shellslash" to my vimrc.

 

For reference here is the text of my file:

 

%        File: sample.tex

%     Created: Sun Jun 22 04:00 PM 2003 P

% Last Change: Mon Dec 15 07:00 PM 2003 

%

\documentclass[a4paper]{article}

\usepackage[sumlimits,]{amsmath}

\begin{document}

\begin{equation}

    \label{eqn:euler}

    e^{j\pi} + 1 = 0

\end{equation}

This is the famous euler equation. I

will type another equation, just as

true:

\begin{equation}

               \label{eqn:simple}

    1 + 1 = 2

\end{equation}

This is my contribution to mathematics.

This is a reference to (\ref{}

\end{document}

 

Thank you

 

Daniel Suttle

Re: [Vim-latex-devel] compiling multiple times - how to debug

[Filip K. <ka...@fz...>]

Dear Marko,

  thanks for this enquiry. In my system, the file compiler.vim is located 
elsewhere, namely in the directory 
/usr/share/vim/site/ftplugin/latex-suite/. But this is not important, I 
guess. The file header is as follows:

"=============================================================================
" 	     File: compiler.vim
"      Author: Srinath Avadhanula
"     Created: Tue Apr 23 05:00 PM 2002 PST
"
"  Description: functions for compiling/viewing/searching latex documents
"=============================================================================

and it has a total of 875 lines. I am not quite sure we are comparing the 
same versions, since I found the lines you mention slightly elsewhere. 
Instead of the code located around lines 608 and 617, I think you mean 
these lines:

580             " If the .bbl file changed after running bibtex, we need to
581             " latex again.
582             if biblinesAfter != biblinesBefore 
583                 echomsg 'Need to rerun because bibliography file changed...'
584                 call Tex_Debug('Tex_CompileMultipleTimes: Need to rerun because bibliography file changed...', 'comp')
585                 let needToRerun = 1

589         " check if latex asks us to rerun
590         let auxlinesAfter = Tex_GetAuxFile(auxFileName)
591         if auxlinesAfter != auxlinesBefore
592             echomsg "Need to rerun because the AUX file changed..."
593             call Tex_Debug("Tex_CompileMultipleTimes: Need to rerun to get cross-references right...", 'comp')
594             let needToRerun = 1
595         endif

One question is whether these two criteria are well chosen and sufficient; 
as you wrote, it seems that swapping two citations is a sufficient reason 
for triggering BibTeX but may not necessarily change the number of lines 
in the .aux file.

Another question is whether these tests in the procedure work as they were 
intended. In this respect, I have doubts. I checked that when I compile my 
.tex file, and this compilation _does_ produce an .aux file with a number 
of lines different from before the compilation, I get anyway the message 
in gvim:

Ran latex 1 time(s)

and BibTeX is not run (no new .bbl file is produced).

As for the other test concerning the number of lines in the .bbl files, I 
could not verify because BibTeX is not triggered in this way.

Debugging the .vim script does not seem easy to me, so I don't know how to 
proceed now.

  All the best,

 	Filip


On Wed, 24 Feb 2021, Mirko Hessel-von Molo wrote:

> 
> Dear Filip,
> 
> from lines 608 and 617 of /usr/share/vim/addons/ftplugin/latex-suite/compiler.vim I gather that
> a second (or further) run of pdflatex is issued when either the _number of lines_ of the bib file or of the aux file
> has changed during the first run.
> 
> So when you just rearrange the cite commands in your file, this presumably won't change the number of lines of either of those files.
> In that way, the multiple compile function is not adapted to bibliography styles which number references by the order of first appearance.
> 
> You could check what happens when you add a new citation to your tex file.
> 
> Best regards, Mirko
> 
> 
> 
> Am Mittwoch, den 24.02.2021, 11:36 +0100 schrieb Filip Kadlec:
> 
> Hi, Mirko,
>
>   thank you for your reply. Having explored the two hints you suggested,
> 
> first I think you are right that the synctex option should only be
> 
> preceded by a single dash; that is in agreement with the man page.. I do
> 
> not know exactly why the double dash was there; someone has advised me
> 
> this line a long time ago, but I cannot exclude I later accidentally added
> 
> a second dash without noticing. So I have fixed this in my .vimrc file.
> 
> As for the debugging procedure, I have done as you advised, and the result
> 
> is the following:
> 
> comp : +Tex_RunLaTeX, b:fragmentFile = 0
> 
> comp : Tex_RunLaTeX: compiling to target [pdf]
> 
> comp : Tex_RunLaTeX: getting dependency chain = [pdf]
> 
> comp : +Tex_SetTeXCompilerTarget: setting target to [pdf] for Compiler
> 
> comp : Tex_RunLaTeX: setting target to pdf
> 
> comp : Tex_RunLaTeX: compiling file multiple times via Tex_CompileMultipleTimes
> 
> comp : Tex_CompileMultipleTimes: latex run number : 1
> 
> comp : Tex_CompileLatex: getting mainfname = [NbN-ver1.tex] from Tex_GetMainFileName
> 
> comp : Tex_CompileLatex: execing [make! NbN-ver1.tex]
> 
> comp : Tex_CompileMultipleTimes: errors = []
> 
> comp : Tex_CompileMultipleTimes: Ran latex 1 time(s)
> 
> comp : Tex_RunLaTeX: errlist = [
>
>   1:  ]
> 
> comp : Tex_SetupErrorWindow: mfnlog = NbN-ver1.log
> 
> comp : -Tex_RunLaTeX
> 
> I was not able to find any suspicious message there. The .bbl file is
> 
> still not updated when I recompile the main file after a change in the
> 
> order of references. It seems the Tex_CompileMultipleTimes procedure does
> 
> not notice there was a change in the .aux file.
>
>   Otherwise, there is a workaround I found in some discussion list, which
> 
> consists in running
> 
> :!latexmk -pdf %
> 
> on the command line. This will update also the bibliography as one would 
> 
> wish, but, unfortunately, the produced pdf file then does not support the 
> 
> inverse search feature. At least it kind of proves BibTeX is functional. 
> 
> By the way, also my forward search has problems, which is quite an old 
> 
> issue but off-topic here.
>
>   Thank you for your effort,
>
>   Filip
> 
> On Tue, 23 Feb 2021, Mirko Hessel-von Molo wrote:
> 
> Dear Filip,
> 
> since noone else who is more competent than me seems to be here to answer, let us try it together.
> 
> I'm just an "ordinary vim-latexsuite user" with no particular experience in writing or debugging vim addons,
> 
> but let's see how far we get.
> 
> You could try adding
> 
> let g:Tex_Debug=1
> 
> to your vimrc file. This enables debugging function within latex-suite.
> 
> Then when a compilation run is done (and multiple compilation has not worked)
> 
> issue the command
> 
> :call Tex_PrintDebug()
> 
> within vim. What results does this give?
> 
> Besides, I'm a bit puzzled by the value given in your vimrc to the g:Tex_CompileRule_pdf variable.
> 
> Are you quite sure that it should read "--synctex=1" and not "-synctex=1" ? (Two dashes versus one?)
> 
> Best regards, Mirko
> 
> Am Freitag, den 19.02.2021, 16:56 +0100 schrieb Filip Kadlec:
> 
> Hello all,
> 
> since years, I have been using successfully the LaTeX suite under OpenSUSE 
> 
> Linux. Having configured the compilation to pdf format, it has always 
> 
> worked straightforwardly. Since recently, however, I have problems with 
> 
> the multiple compilation feature, described in part 6.3 of :h 
> 
> latex-suite.txt.  In situations, where the required routine pdflatex - 
> 
> bibtex - pdflatex - pdflatex would be triggered automatically by a single 
> 
> compilation command, now only a single pdflatex compilation appears to 
> 
> occur. This is obviously annoying.
> 
> In my ~/.vimrc, I have the following settings:
> 
> let g:tex_flavor='latex'
> 
> let g:Tex_DefaultTargetFormat='pdf' 
> 
> let g:Tex_MultipleCompileFormats='pdf' 
> 
> let g:Tex_ViewRule_pdf = 'okular --unique' 
> 
> let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode -file-line-error $* -inverse-search "gvim --servername GVIM --remo
> 
> te +\%l \%f"'
> 
> I reused documents which I compiled earlier; currently, swapping some 
> 
> citations in the .tex file leads to a wrong order of their numbering in 
> 
> the output pdf file if just a single compilation command is triggered.
> 
> I suspect the reason that the multiple compilation has stopped working is 
> 
> some update in texlive; or perhaps an update of vim-latex? Anyway, I 
> 
> wonder how I can debug this problem. Any help would be appreciated.
> 
> By the way, since this forum has been quite inactive, I thought of posting 
> 
> this elsewhere, but I am not sure what the best place would be.
>
>  	Best regards, Filip
> 
> _______________________________________________
> 
> Vim-latex-devel mailing list
> 
> Vim...@li...
> 
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
>

Re: [Vim-latex-devel] compiling multiple times - how to debug

[Mirko Hessel-v. M. <mir...@pa...>]

Dear Filip, 
from lines 608 and 617 of /usr/share/vim/addons/ftplugin/latex-
suite/compiler.vim I gather that a second (or further) run of pdflatex
is issued when either the _number of lines_ of the bib file or of the
aux file has changed during the first run.
So when you just rearrange the cite commands in your file, this
presumably won't change the number of lines of either of those files.In
that way, the multiple compile function is not adapted to bibliography
styles which number references by the order of first appearance.
You could check what happens when you add a new citation to your tex
file.
Best regards, Mirko


Am Mittwoch, den 24.02.2021, 11:36 +0100 schrieb Filip Kadlec:
> Hi, Mirko,
>   thank you for your reply. Having explored the two hints you
> suggested,first I think you are right that the synctex option should
> only bepreceded by a single dash; that is in agreement with the man
> page. I donot know exactly why the double dash was there; someone has
> advised methis line a long time ago, but I cannot exclude I later
> accidentally addeda second dash without noticing. So I have fixed
> this in my .vimrc file.
> As for the debugging procedure, I have done as you advised, and the
> resultis the following:
> comp : +Tex_RunLaTeX, b:fragmentFile = 0comp : Tex_RunLaTeX:
> compiling to target [pdf]comp : Tex_RunLaTeX: getting dependency
> chain = [pdf]comp : +Tex_SetTeXCompilerTarget: setting target to
> [pdf] for Compilercomp : Tex_RunLaTeX: setting target to pdfcomp :
> Tex_RunLaTeX: compiling file multiple times via
> Tex_CompileMultipleTimescomp : Tex_CompileMultipleTimes: latex run
> number : 1comp : Tex_CompileLatex: getting mainfname = [NbN-ver1.tex] 
> from Tex_GetMainFileNamecomp : Tex_CompileLatex: execing [make! NbN-
> ver1.tex]comp : Tex_CompileMultipleTimes: errors = []comp :
> Tex_CompileMultipleTimes: Ran latex 1 time(s)comp : Tex_RunLaTeX:
> errlist = [  1:  ]comp : Tex_SetupErrorWindow: mfnlog = NbN-
> ver1.logcomp : -Tex_RunLaTeX
> I was not able to find any suspicious message there. The .bbl file
> isstill not updated when I recompile the main file after a change in
> theorder of references. It seems the Tex_CompileMultipleTimes
> procedure doesnot notice there was a change in the .aux file.
>   Otherwise, there is a workaround I found in some discussion list,
> whichconsists in running:!latexmk -pdf %
> on the command line. This will update also the bibliography as one
> would wish, but, unfortunately, the produced pdf file then does not
> support the inverse search feature. At least it kind of proves BibTeX
> is functional. By the way, also my forward search has problems, which
> is quite an old issue but off-topic here.
>   Thank you for your effort,
>   Filip
> On Tue, 23 Feb 2021, Mirko Hessel-von Molo wrote:
> 
> Dear Filip,
> since noone else who is more competent than me seems to be here to
> answer, let us try it together.I'm just an "ordinary vim-latexsuite
> user" with no particular experience in writing or debugging vim
> addons,but let's see how far we get.
> You could try adding
> let g:Tex_Debug=1
> to your vimrc file. This enables debugging function within latex-
> suite.Then when a compilation run is done (and multiple compilation
> has not worked)issue the command
> :call Tex_PrintDebug()
> within vim. What results does this give?
> Besides, I'm a bit puzzled by the value given in your vimrc to the
> g:Tex_CompileRule_pdf variable.Are you quite sure that it should read
> "--synctex=1" and not "-synctex=1" ? (Two dashes versus one?)
> Best regards, Mirko
> Am Freitag, den 19.02.2021, 16:56 +0100 schrieb Filip Kadlec:
> Hello all,
> since years, I have been using successfully the LaTeX suite under
> OpenSUSE 
> Linux. Having configured the compilation to pdf format, it has
> always 
> worked straightforwardly. Since recently, however, I have problems
> with 
> the multiple compilation feature, described in part 6.3 of :h 
> latex-suite.txt.  In situations, where the required routine pdflatex
> - 
> bibtex - pdflatex - pdflatex would be triggered automatically by a
> single 
> compilation command, now only a single pdflatex compilation appears
> to 
> occur. This is obviously annoying.
> In my ~/.vimrc, I have the following settings:
> let g:tex_flavor='latex'
> let g:Tex_DefaultTargetFormat='pdf' 
> let g:Tex_MultipleCompileFormats='pdf' 
> let g:Tex_ViewRule_pdf = 'okular --unique' 
> let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1
> -interaction=nonstopmode -file-line-error $* -inverse-search "gvim --
> servername GVIM --remote +\%l \%f"'
> I reused documents which I compiled earlier; currently, swapping
> some 
> citations in the .tex file leads to a wrong order of their numbering
> in 
> the output pdf file if just a single compilation command is
> triggered.
> I suspect the reason that the multiple compilation has stopped
> working is 
> some update in texlive; or perhaps an update of vim-latex? Anyway, I 
> wonder how I can debug this problem. Any help would be appreciated.
> By the way, since this forum has been quite inactive, I thought of
> posting 
> this elsewhere, but I am not sure what the best place would be.
>  	Best regards, Filip
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> 
> 

Re: [Vim-latex-devel] compiling multiple times - how to debug

[Filip K. <ka...@fz...>]

Hi, Mirko,

  thank you for your reply. Having explored the two hints you suggested,
first I think you are right that the synctex option should only be
preceded by a single dash; that is in agreement with the man page. I do
not know exactly why the double dash was there; someone has advised me
this line a long time ago, but I cannot exclude I later accidentally added
a second dash without noticing. So I have fixed this in my .vimrc file.

As for the debugging procedure, I have done as you advised, and the result
is the following:

comp : +Tex_RunLaTeX, b:fragmentFile = 0
comp : Tex_RunLaTeX: compiling to target [pdf]
comp : Tex_RunLaTeX: getting dependency chain = [pdf]
comp : +Tex_SetTeXCompilerTarget: setting target to [pdf] for Compiler
comp : Tex_RunLaTeX: setting target to pdf
comp : Tex_RunLaTeX: compiling file multiple times via Tex_CompileMultipleTimes
comp : Tex_CompileMultipleTimes: latex run number : 1
comp : Tex_CompileLatex: getting mainfname = [NbN-ver1.tex] from Tex_GetMainFileName
comp : Tex_CompileLatex: execing [make! NbN-ver1.tex]
comp : Tex_CompileMultipleTimes: errors = []
comp : Tex_CompileMultipleTimes: Ran latex 1 time(s)
comp : Tex_RunLaTeX: errlist = [
  1:  ]
comp : Tex_SetupErrorWindow: mfnlog = NbN-ver1.log
comp : -Tex_RunLaTeX

I was not able to find any suspicious message there. The .bbl file is
still not updated when I recompile the main file after a change in the
order of references. It seems the Tex_CompileMultipleTimes procedure does
not notice there was a change in the .aux file.

  Otherwise, there is a workaround I found in some discussion list, which
consists in running
:!latexmk -pdf %

on the command line. This will update also the bibliography as one would 
wish, but, unfortunately, the produced pdf file then does not support the 
inverse search feature. At least it kind of proves BibTeX is functional. 
By the way, also my forward search has problems, which is quite an old 
issue but off-topic here.

  Thank you for your effort,

  Filip

On Tue, 23 Feb 2021, Mirko Hessel-von Molo wrote:

> 
> Dear Filip,
> 
> since noone else who is more competent than me seems to be here to answer, let us try it together.
> I'm just an "ordinary vim-latexsuite user" with no particular experience in writing or debugging vim addons,
> but let's see how far we get.
> 
> You could try adding
> 
> let g:Tex_Debug=1
> 
> to your vimrc file. This enables debugging function within latex-suite.
> Then when a compilation run is done (and multiple compilation has not worked)
> issue the command
> 
> :call Tex_PrintDebug()
> 
> within vim. What results does this give?
> 
> Besides, I'm a bit puzzled by the value given in your vimrc to the g:Tex_CompileRule_pdf variable.
> Are you quite sure that it should read "--synctex=1" and not "-synctex=1" ? (Two dashes versus one?)
> 
> Best regards, Mirko
> 
> Am Freitag, den 19.02.2021, 16:56 +0100 schrieb Filip Kadlec:
> 
> Hello all,
> 
> since years, I have been using successfully the LaTeX suite under OpenSUSE 
> 
> Linux. Having configured the compilation to pdf format, it has always 
> 
> worked straightforwardly. Since recently, however, I have problems with 
> 
> the multiple compilation feature, described in part 6.3 of :h 
> 
> latex-suite.txt.  In situations, where the required routine pdflatex - 
> 
> bibtex - pdflatex - pdflatex would be triggered automatically by a single 
> 
> compilation command, now only a single pdflatex compilation appears to 
> 
> occur. This is obviously annoying.
> 
> In my ~/.vimrc, I have the following settings:
> 
> let g:tex_flavor='latex'
> 
> let g:Tex_DefaultTargetFormat='pdf' 
> 
> let g:Tex_MultipleCompileFormats='pdf' 
> 
> let g:Tex_ViewRule_pdf = 'okular --unique' 
> 
> let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode -file-line-error $* -inverse-search "gvim --servername GVIM --remo
> te +\%l \%f"'
> 
> I reused documents which I compiled earlier; currently, swapping some 
> 
> citations in the .tex file leads to a wrong order of their numbering in 
> 
> the output pdf file if just a single compilation command is triggered.
> 
> I suspect the reason that the multiple compilation has stopped working is 
> 
> some update in texlive; or perhaps an update of vim-latex? Anyway, I 
> 
> wonder how I can debug this problem. Any help would be appreciated.
> 
> By the way, since this forum has been quite inactive, I thought of posting 
> 
> this elsewhere, but I am not sure what the best place would be.
>
>  	Best regards, Filip
> 
> _______________________________________________
> 
> Vim-latex-devel mailing list
> 
> Vim...@li...
> 
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
>

Re: [Vim-latex-devel] compiling multiple times - how to debug

[Mirko Hessel-v. M. <mir...@pa...>]

Dear Filip, 

since noone else who is more competent than me seems to be here to
answer, let us try it together. 
I'm just an "ordinary vim-latexsuite user" with no particular
experience in writing or debugging vim addons, 
but let's see how far we get. 

You could try adding 

let g:Tex_Debug=1

to your vimrc file. This enables debugging function within latex-suite.
Then when a compilation run is done (and multiple compilation has not
worked)
issue the command 

:call Tex_PrintDebug() 

within vim. What results does this give?

Besides, I'm a bit puzzled by the value given in your vimrc to the
g:Tex_CompileRule_pdf variable. 
Are you quite sure that it should read "--synctex=1" and not "-
synctex=1" ? (Two dashes versus one?)

Best regards, Mirko

Am Freitag, den 19.02.2021, 16:56 +0100 schrieb Filip Kadlec:
> Hello all,
> 
> since years, I have been using successfully the LaTeX suite under OpenSUSE 
> Linux. Having configured the compilation to pdf format, it has always 
> worked straightforwardly. Since recently, however, I have problems with 
> the multiple compilation feature, described in part 6.3 of :h 
> latex-suite.txt.  In situations, where the required routine pdflatex - 
> bibtex - pdflatex - pdflatex would be triggered automatically by a single 
> compilation command, now only a single pdflatex compilation appears to 
> occur. This is obviously annoying.
> 
> In my ~/.vimrc, I have the following settings:
> 
> let g:tex_flavor='latex'
> let g:Tex_DefaultTargetFormat='pdf' 
> let g:Tex_MultipleCompileFormats='pdf' 
> let g:Tex_ViewRule_pdf = 'okular --unique' 
> let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode -file-line-error $* -inverse-search "gvim --servername GVIM --remote +\%l \%f"'
> 
> I reused documents which I compiled earlier; currently, swapping some 
> citations in the .tex file leads to a wrong order of their numbering in 
> the output pdf file if just a single compilation command is triggered.
> 
> I suspect the reason that the multiple compilation has stopped working is 
> some update in texlive; or perhaps an update of vim-latex? Anyway, I 
> wonder how I can debug this problem. Any help would be appreciated.
> 
> By the way, since this forum has been quite inactive, I thought of posting 
> this elsewhere, but I am not sure what the best place would be.
> 
>  	Best regards, Filip
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 

[Vim-latex-devel] compiling multiple times - how to debug

[Filip K. <ka...@fz...>]

Hello all,

since years, I have been using successfully the LaTeX suite under OpenSUSE 
Linux. Having configured the compilation to pdf format, it has always 
worked straightforwardly. Since recently, however, I have problems with 
the multiple compilation feature, described in part 6.3 of :h 
latex-suite.txt.  In situations, where the required routine pdflatex - 
bibtex - pdflatex - pdflatex would be triggered automatically by a single 
compilation command, now only a single pdflatex compilation appears to 
occur. This is obviously annoying.

In my ~/.vimrc, I have the following settings:

let g:tex_flavor='latex'
let g:Tex_DefaultTargetFormat='pdf' 
let g:Tex_MultipleCompileFormats='pdf' 
let g:Tex_ViewRule_pdf = 'okular --unique' 
let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode -file-line-error $* -inverse-search "gvim --servername GVIM --remote +\%l \%f"'

I reused documents which I compiled earlier; currently, swapping some 
citations in the .tex file leads to a wrong order of their numbering in 
the output pdf file if just a single compilation command is triggered.

I suspect the reason that the multiple compilation has stopped working is 
some update in texlive; or perhaps an update of vim-latex? Anyway, I 
wonder how I can debug this problem. Any help would be appreciated.

By the way, since this forum has been quite inactive, I thought of posting 
this elsewhere, but I am not sure what the best place would be.

 	Best regards, Filip

Re: [Vim-latex-devel] Live PDF Preview

[Gary J. <gar...@sp...>]

On 2020-07-04, ravi r wrote:
> My Vim Latex-Suite .vimrc settings:
>      let g:Tex_DefaultTargetFormat="pdf"
>      let g:Tex_CompileRule_pdf='pdflatex --output-directory=/tmp -aux-directory
> =/tmp -interaction=nonstopmode $*'
>      let g:Tex_ViewRule_pdf='cd /tmp; AcroRd32'
> 
> I would like to find out if there is any support from Vim Latex Suite for pdf
> readers
> like evince, okular that would allow live pdf preview as the tex document is
> being modified.

I use this:

    let g:Tex_ViewRule_pdf = 'evince'

Updating the PDF document is just a matter of executing

    \ll

Regards,
Gary

[Vim-latex-devel] Live PDF Preview

[ravi r <rav...@gm...>]

My Vim Latex-Suite .vimrc settings:
     let g:Tex_DefaultTargetFormat="pdf"
     let g:Tex_CompileRule_pdf='pdflatex --output-directory=/tmp
-aux-directory=/tmp -interaction=nonstopmode $*'
     let g:Tex_ViewRule_pdf='cd /tmp; AcroRd32'

I would like to find out if there is any support from Vim Latex Suite for
pdf readers
like evince, okular that would allow live pdf preview as the tex document
is being modified.

[Vim-latex-devel] editing xml files with a lot of latex codes using vim-latex

[Wai Y. P. <wyp...@gm...>]

Hi vim-latex-developers,

     The xml files that I write will have a lot of latex codes (since I
want to use PreTeXt)
I really like vim-latex but I also want the functionality of a plugin likes
xml.vim (e.g. typing <m> will automatically close it to <m></m>). Can I
have both, if so how? I tried setting the filetype to tex.xml but the
xml.vim plugin doesn't load and setting ft to xml.tex then latex-vim
doesn't load.

Thank you for the help in advance,
Wai Yan Pong

[Vim-latex-devel] Smart Quotes in subordinate project file

[Mirko Hessel-v. M. <mir...@pa...>]

Dear Vim-Latexsuite-Developers, 

let me first say thank you for that great piece of software I've been
using for so many years now. 
I'm using vim-latexsuite 1.9.0 with Vim 8.0.

For the first time, I'm now working on a larger multi-file project in
my native language (German), and so this is the first time I come
across the following problem:

The document (a large lecture script) is split into several .tex files
each holding one chapter. There is a master file (Skript.tex) within
which the chapter files are \included. 
This is also marked as main file via a file Skript.tex.latexmain in the
same folder. So compiling works flawlessly also when I'm editing only
one of the chapter files.

However, the smart quotes mechanism does not work when I edit one of
the chapter files. 
As far as I can see, the filetype plugin checks whether the .tex file
contains the line \usepackage[utf8]{inputenc} to set the smart quotes
to the correct Unicode symbols.
Now this works, when I'm in the master file (where I'm rather seldom),
but it does not work in the chapter files. 

What can I do about this? Is it possible e. g. to have the
corresponding TexLet commands issued from a modeline?

Thanks a lot for any help, 

with best regards, 

Mirko

[Vim-latex-devel] Bug: folding preambles with multi-line document class

[Felix K. <kue...@gm...>]

Hello vim-latex developers,

there is a bug in the folding functionality of the current version of 
vim-latex. When the \documentclass command spreads across multiple 
lines, the preamble is not folded by vim-latex. Consider the following 
example (also attached):

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% fold_bug.tex
\documentclass[
         %draft,
         12pt,
     ]{article}

% This should be folded, but actually isn't :-(
\usepackage[T1]{fontenc}        % font encoding

\begin{document}
     \section{Example section}
     This is the document body.  It will be properly folded.
\end{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Here, the \section is folded correctly, but the preamble is not. When 
putting the \documentclass entirely on one line, i.e., write:

\documentclass[12pt,]{article}

folding of the preamble works correctly. But then, obviously, one cannot 
state options line-wise, include comments, or comment out option. It 
would be great if this bug could be fixed. Thanks for your efforts.


~Felix

Re: [Vim-latex-devel] [Solved] Inserting a Template also inserts Jump marks

[Scott D F. <sc...@fr...>]

That's it. Solved. Thank you very much.

I had neglected to look at the samples.

Scott


On 9/19/2019 1:35 PM, Gerd Wachsmuth wrote:
> The first line in a template file is supposed to look like
> <+    +>    !comp!    !exe!
> (with tabs), compare with the files in ftplugin/latex-suite/templates/
>
> Please check your template file. I think you have an empty first line 
> in it!
>
> Best regards,
> Gerd
>
>
> On 07.09.19 21:29, Scott D Friedemann wrote:
>> Windows 10 latest
>> Vim 8.1, using gvim
>> vim-latex latest (didn't see the version number)
>> the template file has Windows-style line endings
>>
>> Here is a sample template file
>> ========
>> \documentclass[12pt]{article}
>> \pagestyle{empty}
>>
>> \begin{document}
>>
>>
>> \end{document}
>> ========
>>
>> Not much in it, but if I insert it with TeX-Suite, Templates, it 
>> looks like this
>>
>> ========
>> <++>\<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>c<++>l<++>a<++>s<++>s<++>[<++>1<++>2<++>p<++>t<++>]<++>{<++>a<++>r<++>t<++>i<++>c<++>l<++>e<++>}<++> 
>>
>> <++>\<++>p<++>a<++>g<++>e<++>s<++>t<++>y<++>l<++>e<++>{<++>e<++>m<++>p<++>t<++>y<++>}<++> 
>>
>> <++>
>> <++>\<++>b<++>e<++>g<++>i<++>n<++>{<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>}<++> 
>>
>> <++>
>> <++>
>> <++>\<++>e<++>n<++>d<++>{<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>}<++> 
>>
>> <++>
>> <++>
>> ========
>>
>>
>> On 9/7/2019 12:39 PM, Gerd Wachsmuth wrote:
>>> This sounds like a bug. Can you provide some more information that 
>>> allows me to reproduce this bug?
>>>
>>>
>>>
>>> On 07.09.19 17:14, Scott D Friedemann wrote:
>>>> Whenever I insert a template I get jump marks after every character 
>>>> in the template, making it a bit unwieldy, actually unusable.
>>>>
>>>> Is there some way to prevent the insertion of these jump marks?
>>

Re: [Vim-latex-devel] Inserting a Template also inserts Jump marks

[Gerd W. <ger...@ma...>]

The first line in a template file is supposed to look like
<+	+>	!comp!	!exe!
(with tabs), compare with the files in ftplugin/latex-suite/templates/

Please check your template file. I think you have an empty first line in it!

Best regards,
Gerd


On 07.09.19 21:29, Scott D Friedemann wrote:
> Windows 10 latest
> Vim 8.1, using gvim
> vim-latex latest (didn't see the version number)
> the template file has Windows-style line endings
> 
> Here is a sample template file
> ========
> \documentclass[12pt]{article}
> \pagestyle{empty}
> 
> \begin{document}
> 
> 
> \end{document}
> ========
> 
> Not much in it, but if I insert it with TeX-Suite, Templates, it looks 
> like this
> 
> ========
> <++>\<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>c<++>l<++>a<++>s<++>s<++>[<++>1<++>2<++>p<++>t<++>]<++>{<++>a<++>r<++>t<++>i<++>c<++>l<++>e<++>}<++>
> <++>\<++>p<++>a<++>g<++>e<++>s<++>t<++>y<++>l<++>e<++>{<++>e<++>m<++>p<++>t<++>y<++>}<++>
> <++>
> <++>\<++>b<++>e<++>g<++>i<++>n<++>{<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>}<++>
> <++>
> <++>
> <++>\<++>e<++>n<++>d<++>{<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>}<++>
> <++>
> <++>
> ========
> 
> 
> On 9/7/2019 12:39 PM, Gerd Wachsmuth wrote:
>> This sounds like a bug. Can you provide some more information that 
>> allows me to reproduce this bug?
>>
>>
>>
>> On 07.09.19 17:14, Scott D Friedemann wrote:
>>> Whenever I insert a template I get jump marks after every character 
>>> in the template, making it a bit unwieldy, actually unusable.
>>>
>>> Is there some way to prevent the insertion of these jump marks?
> 

Re: [Vim-latex-devel] Inserting a Template also inserts Jump marks

[Scott D F. <sc...@fr...>]

Windows 10 latest
Vim 8.1, using gvim
vim-latex latest (didn't see the version number)
the template file has Windows-style line endings

Here is a sample template file
========
\documentclass[12pt]{article}
\pagestyle{empty}

\begin{document}


\end{document}
========

Not much in it, but if I insert it with TeX-Suite, Templates, it looks 
like this

========
<++>\<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>c<++>l<++>a<++>s<++>s<++>[<++>1<++>2<++>p<++>t<++>]<++>{<++>a<++>r<++>t<++>i<++>c<++>l<++>e<++>}<++>
<++>\<++>p<++>a<++>g<++>e<++>s<++>t<++>y<++>l<++>e<++>{<++>e<++>m<++>p<++>t<++>y<++>}<++>
<++>
<++>\<++>b<++>e<++>g<++>i<++>n<++>{<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>}<++>
<++>
<++>
<++>\<++>e<++>n<++>d<++>{<++>d<++>o<++>c<++>u<++>m<++>e<++>n<++>t<++>}<++>
<++>
<++>
========


On 9/7/2019 12:39 PM, Gerd Wachsmuth wrote:
> This sounds like a bug. Can you provide some more information that 
> allows me to reproduce this bug?
>
>
>
> On 07.09.19 17:14, Scott D Friedemann wrote:
>> Whenever I insert a template I get jump marks after every character 
>> in the template, making it a bit unwieldy, actually unusable.
>>
>> Is there some way to prevent the insertion of these jump marks?

[Vim-latex-devel] Inserting a Template also inserts Jump marks

[Scott D F. <sc...@fr...>]

Whenever I insert a template I get jump marks after every character in 
the template, making it a bit unwieldy, actually unusable.

Is there some way to prevent the insertion of these jump marks?

Re: [Vim-latex-devel] tikz commutative diagrams

[Gerd W. <ger...@ma...>]

Hi,

I would guess that your vim tries to compile the document with latex 
instead of pdflatex. Try to add

	let g:Tex_DefaultTargetFormat = 'pdf'

to your ~/.vim/ftplugin/tex.vim

Best regards,
Gerd


On 30.04.19 17:26, Daniel Ricardo Barrero wrote:
> Thank you for your interest, professor Wachsmuth, and I apologize for so 
> late a response.
> What happens is the following:
> In gvim, if I load the package \usepackage{tikz-cd} and then write the 
> code for a simple tikz commutative diagram (such as a commutative square 
> with four letters and four arrows), compile it, and then view the output 
> with xdvi, arrows and letters assume places that do not match. Moreover,
> the diagram elements seem to scatter through the page and superpose 
> themselves to the preceding text.
> In vim, the package \usepackage{tikz-cd} simply does not seem to load, 
> i.e. the document does not compile. And this seems to be the only 
> problem, because when I replace the text "\usepackage{tikz-cd}" with 
> "\usepackage[all]{xy}" the document compiles with no problem.
> Begging your pardon, I will attach a couple of screenshots relevant to 
> my inconvenient.
> 
> Thank you for your attention,
> Daniel R. Barrero R.
> 
> El vie., 26 abr. 2019 a las 1:19, Gerd Wachsmuth 
> (<ger...@ma... 
> <mailto:ger...@ma...>>) escribió:
> 
>     Hi,
> 
>     what do you mean by 'tikz commutative diagrams do not work'? Does the
>     code not compile? Is the syntax highlighting wrong? Please provide some
>     more details!
> 
>     Best regards,
>     Gerd
> 
> 
>     On 17/04/2019 17:19, Daniel Ricardo Barrero wrote:
>      > Hello dear latex-suite development team. I've been using the
>     program for
>      > two days on my Ubuntu 18.04 laptop. Everything has been working just
>      > fine except for tikz commutative diagrams, which I use
>     frequently. It is
>      > not a syntax problem since the same code works perfectly in
>     texmaker. Is
>      > there a way I can fix this say by writing something down on my
>     tex.vim
>      > file? I use xdvi for visualizing and forward-backward searching.
>      >
>      > Thank you and best regards,
>      > Daniel R. Barrero R.
>      >
>      >
>      > _______________________________________________
>      > Vim-latex-devel mailing list
>      > Vim...@li...
>     <mailto:Vim...@li...>
>      > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>      >
> 

Re: [Vim-latex-devel] tikz commutative diagrams

[Gerd W. <ger...@ma...>]

Hi,

what do you mean by 'tikz commutative diagrams do not work'? Does the 
code not compile? Is the syntax highlighting wrong? Please provide some 
more details!

Best regards,
Gerd


On 17/04/2019 17:19, Daniel Ricardo Barrero wrote:
> Hello dear latex-suite development team. I've been using the program for 
> two days on my Ubuntu 18.04 laptop. Everything has been working just 
> fine except for tikz commutative diagrams, which I use frequently. It is 
> not a syntax problem since the same code works perfectly in texmaker. Is 
> there a way I can fix this say by writing something down on my tex.vim 
> file? I use xdvi for visualizing and forward-backward searching.
> 
> Thank you and best regards,
> Daniel R. Barrero R.
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

[Vim-latex-devel] tikz commutative diagrams

[Daniel R. B. <bar...@gm...>]

Hello dear latex-suite development team. I've been using the program for
two days on my Ubuntu 18.04 laptop. Everything has been working just fine
except for tikz commutative diagrams, which I use frequently. It is not a
syntax problem since the same code works perfectly in texmaker. Is there a
way I can fix this say by writing something down on my tex.vim file? I use
xdvi for visualizing and forward-backward searching.

Thank you and best regards,
Daniel R. Barrero R.

[Vim-latex-devel] (no subject)

[Zach B. <zb...@gm...>]

Hi all,

Sorry if the format is wrong--first time submitting a patch anywhere. I
would like to submit the following  simple patch. See below for the details.

Best,

Zach

>From 7ed2740e40741dc58bf1dccc3dcdd54da0d25b5a Mon Sep 17 00:00:00 2001
From: "Zachary M. Boyd" <zb...@gm...>
Date: Thu, 11 Oct 2018 14:57:28 -0400
Subject: [PATCH] Fixed support for user-defined g:Tex_CompileRule_bib

Previously, the value of this variable was ignored.
Now, the trailing $* is stripped off, and then the variable is exec'ed
to run Bibtex.
---
 ftplugin/latex-suite/compiler.vim | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/ftplugin/latex-suite/compiler.vim
b/ftplugin/latex-suite/compiler.vim
index be9e267..d1dcc31 100644
--- a/ftplugin/latex-suite/compiler.vim
+++ b/ftplugin/latex-suite/compiler.vim
@@ -624,9 +624,14 @@ function! Tex_CompileMultipleTimes()
             let biblinesBefore = Tex_CatFile(bibFileName)

             echomsg "Running '".Tex_GetVarValue('Tex_BibtexFlavor')."' ..."
-            let temp_mp = &mp | let &mp =
Tex_GetVarValue('Tex_BibtexFlavor')
-            exec 'silent! make '.mainFileName_root
-            let &mp = temp_mp
+
+            " strip off the $* at the end of Tex_CompileRule_bib
+            if split(g:Tex_CompileRule_bib)[-1] !=# '$*'
+                let tmp_compileRule =
join(split(g:Tex_CompileRule_bib)[:-2])
+            else
+                let tmp_compileRule = g:Tex_CompileRule_bib
+            endif
+            exec 'silent !' . tmp_compileRule . ' ' . mainFileName_root

             let biblinesAfter = Tex_CatFile(bibFileName)

Re: [Vim-latex-devel] Environment mapping scheme

[Gerd W. <ger...@ma...>]

Dear Kevin,

what you describe is currently not possible, i.e., you cannot remove the 
"<CR>" after "\begin{someenv}" directly by some configuration variable.

However, you can define

let g:Tex_Env_someenv = 
"\\begin{someenv}[<+optional+>]{<+mandatory+>}\<CR><++>\<CR>\\end{someenv}"

in your `.vim/ftplugin/tex.vim` to obtain the desired expansion (see 
also 
http://vim-latex.sourceforge.net/documentation/latex-suite.html#Tex_Env_name).

Best regards,
Gerd


On 2018-04-01 04:29, Kevin wrote:
> Hi,
> In the current version, the environment mapping is like below:
> 
> \begin{someenv}
>    <++>
> \end{someenv}
> 
> but in many cases, the environments have arguments, so I have to press `<ESC>kA` to add those arguments, like
> 
> \begin{someenv}[<optional>]{<mandatory >}
>    <++>
> \end{someenv}
> 
> it's very annoying. This problem will be solved by changing the mapping to
> 
> \begin{someenv}<++>
> \end{someenv}
> 
> At this time, if the environment doesn't have arguments, I can simply press `<CR>`, if it does, I can directly type them.
> 
> I have read the help document but cannot find a way to change it. So is there a method to change the default mapping? If not, hope you make it possible, thanks!
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

[Vim-latex-devel] Environment mapping scheme

[Kevin <wan...@gm...>]

Hi,
In the current version, the environment mapping is like below:

\begin{someenv}
  <++>
\end{someenv}

but in many cases, the environments have arguments, so I have to press `<ESC>kA` to add those arguments, like

\begin{someenv}[<optional>]{<mandatory >}
  <++>
\end{someenv}

it's very annoying. This problem will be solved by changing the mapping to

\begin{someenv}<++>
\end{someenv}

At this time, if the environment doesn't have arguments, I can simply press `<CR>`, if it does, I can directly type them.

I have read the help document but cannot find a way to change it. So is there a method to change the default mapping? If not, hope you make it possible, thanks!

Re: [Vim-latex-devel] Template names missing: OS X

[Gerd W. <ger...@ma...>]

Hi,

to me, this looks like a bug in vim itself.

Best regards,
Gerd


On 2017-12-24 15:29, Daryl Lee wrote:
> Thanks for the response!
> 
> By the way, this is Vim-Latex 1.9.0.
> 
> Here is more data.  I tried the following variants (beginning with the i 
> that numbers the item):
> 
> i."<Tab>".fname."  "    Produces "1"
> 
> i.":<Tab>".fname." "   Produces "1:"
> 
> i.":".fname." "   Produces "1:article"
>    (No space after the colon)
> 
> i.": ".fname." "   Produces "1:"
>    (Space after the colon)
> 
> Also, there is nothing after the word Compile (or any of its siblings) 
> in the TeX-Suite menu.  So, feeling brave, I opened texmenuconf.vim and 
> on line 56 deleted the <Tab> after the word "Compile" and got the -ll. 
> When I added a space after "Compile", the -ll disappeared.
> 
> So, recognizing that both <Tab> and space are whitespace, I'll be 
> looking at how whitespace is handled.
> 
> On 12/24/17 1:11 AM, Gerd Wachsmuth wrote:
>> Hi Daryl,
>>
>> this is weird. In fact, `:help creating-menus` states:
>> >>>>>>>>>
>> Special characters in a menu name:
>>
>> <Tab>    Separates the menu name from right-aligned text. This can be
>>     used to show the equivalent typed command.  The text "<Tab>"
>>     can be used here for convenience.  If you are using a real
>>     tab, don't forget to put a backslash before it!
>> >>>>>>>>>
>>
>> Hence, a "<Tab>" is perfectly fine here. Do you have right-aligned 
>> text in the other menus, e.g. right of "Compile", you should find "ll"??
>>
>>
>> Best regards
>> Gerd
>>
>>
>> On 2017-12-24 03:44, Daryl Lee wrote:
>>> Okay, in case this question comes up again, here is *A* solution 
>>> (there may be better, but I'm a near-total VimScript newbie:
>>>
>>> I deleted the <TAB> in line 24 of templates.vim:
>>>
>>> " SetTemplateMenu: sets up the menu for templates {{{
>>> function! <SID>SetTemplateMenu()
>>>      let flist = <SID>FindInTemplateDir('')
>>>      let i = 1
>>>      while 1
>>>          let fname = Tex_Strntok(flist, ',', i)
>>>          if fname == ''
>>>              break
>>>          endif
>>> "        exe "amenu 
>>> ".g:Tex_TemplatesMenuLocation."&".i.":<Tab>".fname." ".
>>>          exe "amenu ".g:Tex_TemplatesMenuLocation."&".i.":".fname." ".
>>>              \":call <SID>ReadTemplate('".fname."')<CR>"
>>>          let i = i + 1
>>>      endwhile
>>> endfunction
>>>
>>> And then closed all Vim windows and opened .tex file.
>>>
>>> According to one of the earlier posters on this problem, the issue 
>>> arises in other menus as well.  I'll remember this in case I need it 
>>> later.
>>>
>>>
>>> On 12/23/17 7:10 PM, Daryl Lee wrote:
>>>> I'm installing Vim-LaTeX on all my workstations (OS X, Windows 10, 
>>>> and four Ubuntu).  First, kudos to the people who brought this to 
>>>> the state that it's in; very impressive.  The first thing I noticed 
>>>> in OS X (from MacVim) is that when I click TeX-Suite->Templates, I 
>>>> get a list of numbers 1: through 4:, but without the name of the 
>>>> template. The templates work (at least 'article' and 'IEEEtran', 
>>>> which I picked by looking at the contents of the 'templates' file.
>>>>
>>>> How do I get the actual file names to show up?
>>>>
>>>> This question was asked in 2010 and 2011 by different people and 
>>>> apparently never answered.  I thought I might try again.
>>>>
>>>
>>
> 

[Vim-latex-devel] Fwd: Re: Template names missing: OS X

[Daryl L. <da...@da...>]

I failed to copy this reply to the list.  Here it is, in case anyone 
else is following this thread.



-------- Forwarded Message --------
Subject: 	Re: [Vim-latex-devel] Template names missing: OS X
Date: 	Sun, 24 Dec 2017 07:29:22 -0700
From: 	Daryl Lee <da...@da...>
To: 	Gerd Wachsmuth <ger...@ma...>



Thanks for the response!

By the way, this is Vim-Latex 1.9.0.

Here is more data.  I tried the following variants (beginning with the i
that numbers the item):

i."<Tab>".fname."  "    Produces "1"

i.":<Tab>".fname." "   Produces "1:"

i.":".fname." "   Produces "1:article"
   (No space after the colon)

i.": ".fname." "   Produces "1:"
   (Space after the colon)

Also, there is nothing after the word Compile (or any of its siblings)
in the TeX-Suite menu.  So, feeling brave, I opened texmenuconf.vim and
on line 56 deleted the <Tab> after the word "Compile" and got the -ll.
When I added a space after "Compile", the -ll disappeared.

So, recognizing that both <Tab> and space are whitespace, I'll be
looking at how whitespace is handled.

On 12/24/17 1:11 AM, Gerd Wachsmuth wrote:
> Hi Daryl,
>
> this is weird. In fact, `:help creating-menus` states:
> >>>>>>>>>
> Special characters in a menu name:
>
> <Tab>    Separates the menu name from right-aligned text. This can be
>     used to show the equivalent typed command.  The text "<Tab>"
>     can be used here for convenience.  If you are using a real
>     tab, don't forget to put a backslash before it!
> >>>>>>>>>
>
> Hence, a "<Tab>" is perfectly fine here. Do you have right-aligned 
> text in the other menus, e.g. right of "Compile", you should find "ll"??
>
>
> Best regards
> Gerd
>
>
> On 2017-12-24 03:44, Daryl Lee wrote:
>> Okay, in case this question comes up again, here is *A* solution 
>> (there may be better, but I'm a near-total VimScript newbie:
>>
>> I deleted the <TAB> in line 24 of templates.vim:
>>
>> " SetTemplateMenu: sets up the menu for templates {{{
>> function! <SID>SetTemplateMenu()
>>      let flist = <SID>FindInTemplateDir('')
>>      let i = 1
>>      while 1
>>          let fname = Tex_Strntok(flist, ',', i)
>>          if fname == ''
>>              break
>>          endif
>> "        exe "amenu 
>> ".g:Tex_TemplatesMenuLocation."&".i.":<Tab>".fname." ".
>>          exe "amenu ".g:Tex_TemplatesMenuLocation."&".i.":".fname." ".
>>              \":call <SID>ReadTemplate('".fname."')<CR>"
>>          let i = i + 1
>>      endwhile
>> endfunction
>>
>> And then closed all Vim windows and opened .tex file.
>>
>> According to one of the earlier posters on this problem, the issue 
>> arises in other menus as well.  I'll remember this in case I need it 
>> later.
>>
>>
>> On 12/23/17 7:10 PM, Daryl Lee wrote:
>>> I'm installing Vim-LaTeX on all my workstations (OS X, Windows 10, 
>>> and four Ubuntu).  First, kudos to the people who brought this to 
>>> the state that it's in; very impressive.  The first thing I noticed 
>>> in OS X (from MacVim) is that when I click TeX-Suite->Templates, I 
>>> get a list of numbers 1: through 4:, but without the name of the 
>>> template. The templates work (at least 'article' and 'IEEEtran', 
>>> which I picked by looking at the contents of the 'templates' file.
>>>
>>> How do I get the actual file names to show up?
>>>
>>> This question was asked in 2010 and 2011 by different people and 
>>> apparently never answered.  I thought I might try again.
>>>
>>
>

-- 
Daryl Lee
All our discontents about what we want appeared to
me to spring from the want of thankfulness for what we
have. -- Daniel Defoe

-- 
Daryl Lee
All our discontents about what we want appeared to
me to spring from the want of thankfulness for what we
have. -- Daniel Defoe

Re: [Vim-latex-devel] Template names missing: OS X

[Gerd W. <ger...@ma...>]

Hi Daryl,

this is weird. In fact, `:help creating-menus` states:
 >>>>>>>>>
Special characters in a menu name:

<Tab>	Separates the menu name from right-aligned text.  This can be
	used to show the equivalent typed command.  The text "<Tab>"
	can be used here for convenience.  If you are using a real
	tab, don't forget to put a backslash before it!
 >>>>>>>>>

Hence, a "<Tab>" is perfectly fine here. Do you have right-aligned text 
in the other menus, e.g. right of "Compile", you should find "ll"??


Best regards
Gerd


On 2017-12-24 03:44, Daryl Lee wrote:
> Okay, in case this question comes up again, here is *A* solution (there 
> may be better, but I'm a near-total VimScript newbie:
> 
> I deleted the <TAB> in line 24 of templates.vim:
> 
> " SetTemplateMenu: sets up the menu for templates {{{
> function! <SID>SetTemplateMenu()
>      let flist = <SID>FindInTemplateDir('')
>      let i = 1
>      while 1
>          let fname = Tex_Strntok(flist, ',', i)
>          if fname == ''
>              break
>          endif
> "        exe "amenu ".g:Tex_TemplatesMenuLocation."&".i.":<Tab>".fname." ".
>          exe "amenu ".g:Tex_TemplatesMenuLocation."&".i.":".fname." ".
>              \":call <SID>ReadTemplate('".fname."')<CR>"
>          let i = i + 1
>      endwhile
> endfunction
> 
> And then closed all Vim windows and opened .tex file.
> 
> According to one of the earlier posters on this problem, the issue 
> arises in other menus as well.  I'll remember this in case I need it later.
> 
> 
> On 12/23/17 7:10 PM, Daryl Lee wrote:
>> I'm installing Vim-LaTeX on all my workstations (OS X, Windows 10, and 
>> four Ubuntu).  First, kudos to the people who brought this to the 
>> state that it's in; very impressive.  The first thing I noticed in OS 
>> X (from MacVim) is that when I click TeX-Suite->Templates, I get a 
>> list of numbers 1: through 4:, but without the name of the template. 
>> The templates work (at least 'article' and 'IEEEtran', which I picked 
>> by looking at the contents of the 'templates' file.
>>
>> How do I get the actual file names to show up?
>>
>> This question was asked in 2010 and 2011 by different people and 
>> apparently never answered.  I thought I might try again.
>>
> 

Re: [Vim-latex-devel] Template names missing: OS X

[Daryl L. <da...@da...>]

Okay, in case this question comes up again, here is *A* solution (there 
may be better, but I'm a near-total VimScript newbie:

I deleted the <TAB> in line 24 of templates.vim:

" SetTemplateMenu: sets up the menu for templates {{{
function! <SID>SetTemplateMenu()
     let flist = <SID>FindInTemplateDir('')
     let i = 1
     while 1
         let fname = Tex_Strntok(flist, ',', i)
         if fname == ''
             break
         endif
"        exe "amenu ".g:Tex_TemplatesMenuLocation."&".i.":<Tab>".fname." ".
         exe "amenu ".g:Tex_TemplatesMenuLocation."&".i.":".fname." ".
             \":call <SID>ReadTemplate('".fname."')<CR>"
         let i = i + 1
     endwhile
endfunction

And then closed all Vim windows and opened .tex file.

According to one of the earlier posters on this problem, the issue 
arises in other menus as well.  I'll remember this in case I need it later.


On 12/23/17 7:10 PM, Daryl Lee wrote:
> I'm installing Vim-LaTeX on all my workstations (OS X, Windows 10, and 
> four Ubuntu).  First, kudos to the people who brought this to the 
> state that it's in; very impressive.  The first thing I noticed in OS 
> X (from MacVim) is that when I click TeX-Suite->Templates, I get a 
> list of numbers 1: through 4:, but without the name of the template.  
> The templates work (at least 'article' and 'IEEEtran', which I picked 
> by looking at the contents of the 'templates' file.
>
> How do I get the actual file names to show up?
>
> This question was asked in 2010 and 2011 by different people and 
> apparently never answered.  I thought I might try again.
>

-- 
Daryl Lee
All our discontents about what we want appeared to
me to spring from the want of thankfulness for what we
have. -- Daniel Defoe