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

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

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

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

Re: [Vim-latex-devel] Prevent mainfile scan in parent directories

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

Hi,

there is currently no possibility to disable this feature globally. 
However, you can set

   :let b:Tex_MainFileExpression = expand('%:p')

in the buffers belonging to your tikzfig*.tex files to explicitly set 
the main file for compilation.

Hope this helps,
Gerd


On 03/22/2017 02:12 PM, Christoffer Østfeldt wrote:
> Dear vim-latex comminity
>
> I'm currently working on a somewhat large project in latex, which
> includes several files for individual chapters as well as several
> TikZ-figures. To achieve faster compile-tine when modifying the
> TikZ-figures I use the standalone-class and package, which allows the
> compilation of the figures individually.
>
> When modifying the main text I would like to use the "mainfile"-feature,
> so I don't have to manually switch to main.tex, compile, and go back to
> whatever I was editing. This however does not work if I have my
> TikZ-files in a subfolder, as I will then compile the entire document
> when I just want to compile the figure.
>
> Folder example:
>
> mainfolder/
> |--- main.tex
> |--- main.tex.mainfile
> |--- chapter1.tex
> |--- chapter2.tex
> |--- figs/
>       |--- chapter1figs/
>       |     |--- tikzfig1.tex
>       |     |--- tikzfig2.tex
>       |--- chapter2fig/
>             |--- tikzfig3.tex
>
> Can I disable the backwards search for the mainfile, so only files *in
> the same folder* compiles the mainfile, and I can compile tikzfig1-3
> separately?
>
> Hope you guys can help.
>
> Best regards
> Christoffer
>
>
> ------------------------------------------------------------------------------
> 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] Prevent mainfile scan in parent directories

[Christoffer Ø. <chr...@gm...>]

Dear vim-latex comminity

I'm currently working on a somewhat large project in latex, which includes
several files for individual chapters as well as several TikZ-figures. To
achieve faster compile-tine when modifying the TikZ-figures I use the
standalone-class and package, which allows the compilation of the figures
individually.

When modifying the main text I would like to use the "mainfile"-feature, so
I don't have to manually switch to main.tex, compile, and go back to
whatever I was editing. This however does not work if I have my TikZ-files
in a subfolder, as I will then compile the entire document when I just want
to compile the figure.

Folder example:

mainfolder/
|--- main.tex
|--- main.tex.mainfile
|--- chapter1.tex
|--- chapter2.tex
|--- figs/
     |--- chapter1figs/
     |     |--- tikzfig1.tex
     |     |--- tikzfig2.tex
     |--- chapter2fig/
           |--- tikzfig3.tex

Can I disable the backwards search for the mainfile, so only files *in the
same folder* compiles the mainfile, and I can compile tikzfig1-3 separately?

Hope you guys can help.

Best regards
Christoffer

Re: [Vim-latex-devel] Old tutorials + <alt> problems on Windows

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

> After setting the winaltkeys to 'no' it no longer triggers the menu
> but it prints characters like éě and such instead.
Yes, this is intended behavior of newer versions of the latex-suite. Vim
is not able to distinguish between, e.g., <alt-i> and é (see :help
map-alt-keys). Therefore, these alt-mappings are disabled by default,
see :help altkey-mappings. Note that the online help reflect the state
of version 1.9.0 of latex-suite and this settings has changes since then.

> Nor does it work on 'Bash on Ubuntu on Windows'.
I do not know what you mean.

>
> 3) Delete by backspace? Or is there another key to do that?
Yes, 'delete' or 'backspace' key should work.

Best regards,
Gerd

Re: [Vim-latex-devel] Old tutorials + <alt> problems on Windows

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

Hi,

> 1) When I type eqnarray, hit <F5> it does create the environment but
> with different placeholders than the ones in the tutorial and it doesn't
> have the \label there. Can you please update the tutorial so it matches
> the current state?
Yes, this should be preferable. The current version of latex-suite no 
longer supports the obsolete 'eqnarray'. If you try 'align<F5>', you 
should get a reasonable expansion.

> 2) I tried to create the \label by <Alt>+<L> but it collides with
> TeX-E_l_ements menu shortcut and apparently Windows catches that first
> so no label is created. Is there a way to circumvent this? Or can the
> shortcut of TeX-Elements be changed to something else?
This is covered in the manual, see section 3.10:

http://vim-latex.sourceforge.net/documentation/latex-suite/altkey-mappings.html

Something like

set winaltkeys=no

should help.

> *3) I also didn't find a way how to get rid of the named placeholders
> (e.g. <+position+>)  if I don't want to write anything there (if I hit
> <Ctrl>+<J> they stay there). How does one do that?
1. Possibility: You can delete the placeholder before jumping.
2. Possibility: You set g:Imap_StickyPlaceHolders to 0. This 
automatically deletes the placeholders if you jump away, see

http://vim-latex.sourceforge.net/documentation/latex-suite.html#Imap_StickyPlaceHolders


Best regards,
Gerd

[Vim-latex-devel] Old tutorials + <alt> problems on Windows

[Václav N. <vav...@gm...>]

Hello!

I've just installed vim-latex 1.9.0 to my gvim 8.0 on Windows and started
the tutorial (
http://vim-latex.sourceforge.net/documentation/latex-suite-quickstart.html)
and I've found that it doesn't match the behaviour of vim-latex.

1) When I type eqnarray, hit <F5> it does create the environment but with
different placeholders than the ones in the tutorial and it doesn't have
the \label there. Can you please update the tutorial so it matches the
current state?

2) I tried to create the \label by <Alt>+<L> but it collides with
TeX-E*l*ements
menu shortcut and apparently Windows catches that first so no label is
created. Is there a way to circumvent this? Or can the shortcut of
TeX-Elements be changed to something else?

*3) I also didn't find a way how to get rid of the named placeholders (e.g.
<+position+>)  if I don't want to write anything there (if I hit <Ctrl>+<J>
they stay there). How does one do that?

Sincere thanks

vavanade

Re: [Vim-latex-devel] Aux completion

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

Hi,

> - F9 works only after the first compilation (not too restrictive)
> - F9 completes based on either labels or current reference numbers. -
> The labels method works almost as before, except that the outline window
> does not show a preview of the relevant part of the .tex file.
Yes.


> For the "new" method, how does your algorithm detect which numbers to
> scan?
It looks in the aux-file and tries to differentiate between equations 
(which use \eqref) and other things (which use \cref, \autoref, or 
simply \ref). It works best if you are using hyperref and cleveref. E.g. 
by using the tex-file

=================================================
\documentclass[]{article}
\usepackage{hyperref}
\usepackage{amsthm}
\usepackage{cleveref}
\newtheorem{theorem}{Theorem}[section]
\newtheorem{lemma}[theorem]{Lemma}
\begin{document}
\section{Preliminaries}
\begin{theorem}
	\label{lem:trivial}
	\begin{equation}
		\label{sec:trivial}
		1 + 1 = 2
	\end{equation}
\end{theorem}
\begin{lemma}
	\label{lem:obvious}
	\begin{equation}
		\label{subsec:obvios}
		2 = 1 + 1
	\end{equation}
\end{lemma}
\end{document}
=================================================

you can use the following four completions:
theorem.1.1<F9> => \cref{lem:trivial}
lemma.1.2<F9>   => \cref{lem:obvious}
(1)<F9>         => \eqref{sec:trivial}
(2)<F9>         => \eqref{subsec:obvious}

Moreover, you can still complete via the labels, e.g.
"\ref{<F9>".

> Is it sensitive to a keyword like section, part, theorem, eq, fig,
> etc. when F9 is hit?
No, it just looks into the aux file. It does not matter that e.g. the 
label is prefixed with something like "eq:" (see above). This renders 
this method really robust.

> And depending on this keyword, it enters various
> commands like \autoref, \eqref... right?
Currently, it uses
	Tex_RefCompletionCommand
for the completion of something like "theorem.1.",
	\eqref
for the completion of something that looks like an equation number, e.g. 
"(1".
You can also use "\myrefcommand{<F9>" to get a completion with a custom 
reference command (which should contain 'ref').

> How about the \cite command? As far as I understand, its
> functionality would stay as before.
Yes, this has not been changed.


Anybody who would try to test the new behaviour, is invited to use
	https://github.com/gerw/vim-latex-suite
instead of the default latex-suite.


Best regards,
Gerd

Re: [Vim-latex-devel] Aux completion

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

Hello,

  things start to be clearer to me and it seems to me that the new version
could, indeed, supersede the old one in functionality. To summarize, in
the new version:

- F9 works only after the first compilation (not too restrictive)
- F9 completes based on either labels or current reference numbers. 
- The labels method works almost as before, except that the outline window
does not show a preview of the relevant part of the .tex file.

For the "new" method, how does your algorithm detect which numbers to
scan? Is it sensitive to a keyword like section, part, theorem, eq, fig,
etc. when F9 is hit? And depending on this keyword, it enters various
commands like \autoref, \eqref... right? But in plain LaTeX, just \ref{}
should suffice, maybe with options \ref{sec:}, \ref{fig:}, \ref{eq:} etc.,
I think. How about the \cite command? As far as I understand, its
functionality would stay as before.

Filip

On Fri, 27 Jan 2017, Gerd Wachsmuth wrote:

>Date: Fri, 27 Jan 2017 19:42:28
>From: Gerd Wachsmuth <ger...@ma...>
>To: Filip Kadlec <ka...@fz...>,
>    "vim...@li..."
>    <vim...@li...>
>Subject: Re: [Vim-latex-devel] Aux completion
>
> Thank you for your comments.
>
> I think I was not precise at one point: You still can use labels for 
> completion (as long as they are already in the aux file).
>
> To given an example:
> ========================================
> \documentclass{article}
> \usepackage{hyperref}
> \begin{document}
> \begin{equation}
> 	\label{eq:einstein}
> 	E = m \, c^2
> \end{equation}
> \begin{equation}
> 	a^2 + b^2 = c^2
> 	\label{eq:pythagoras}
> \end{equation}
> \end{document}
> ========================================
>
> The current version produces the following outline window:
> ========================================
>>  eq:einstein		</tmp/test.tex>
> :
>>  eq:pythagoras		</tmp/test.tex>
> :    a^2 + b^2 = c^2
> ========================================
> You can only use the labels for completion and you see some of the surrounding 
> text.
>
> The new, aux-based version produces:
> ========================================
>> eq:einstein
> :  (1)
>> eq:pythagoras
> :  (2)
> ========================================
> Here, you can use both, the label and the actual number, with the new aux 
> completion. However, you do not see some of the text.
>
>
> Moreover, the old mechanism fails to detect if you input some other files via 
> macros, e.g.,
>  \newcommand{\myinput}[1]{\input{#1}}
> and then
>  \myinput{test}.
> Since the labels of the file test.tex still appear in the aux file, the aux 
> based completion also find those labels.
>
>
> In my opinion, the only regress is that you have to compile (once) after 
> entering a new \label{} and before you will be able to complete a reference to 
> exactly this label.
>
>
> Best regards,
> Gerd
>
>
> On 2017-01-27 10:05, Filip Kadlec wrote:
>> Hi, Gerd,
>>
>>  I second Laszlo's point of view; for me, using labels with well chosen
>> names is clearly the best choice, and I think that the latex-suite should
>> keep this behavior by default. To me, the <F9>-completion works quite well
>> and it would maybe need some improvements (it does not work for me with
>> \includegraphics, and if the vim-window is split when invoking <F9> in
>> \cite, it oftentimes fails...) but not a complete change of logic.
>>
>>  Your idea to scan the .aux files could be useful for someone, though. I
>> don't know if it is feasible, but I would suggest an implementation via a
>> command, something like
>>
>>  let g:Tex_completion_scanfile = tex / aux
>> 
>> whereby everyone would have the choice.
>> 
>> This would does not imply less code nor less maintenance, though.
>>
>>     Best regards,
>>         Filip
>> 
>> On Thu, 26 Jan 2017, N Laszlo Frazer wrote:
>> 
>>> Date: Thu, 26 Jan 2017 21:33:44
>>> From: N Laszlo Frazer <per...@ce...>
>>> To: "vim...@li..."
>>>    <vim...@li...>
>>> Subject: Re: [Vim-latex-devel] Aux completion
>>> 
>>> Please do not remove the current functionality.  I think it would be very
>>> annoying to rely on the aux file being up-to-date.
>>> 
>>> Well-chosen keys are much easier to remember than numbers, and they do
>>> not
>>> change when you expand the document.
>>> 
>>> On Fri, 27 Jan 2017 00:52:25 +1100, Gerd Wachsmuth
>>> <ger...@ma...> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> in my version of latex-suite (https://github.com/gerw/vim-latex-suite),
>>>> I have changed the mechanism of \ref-completions. The current version of
>>>> latex-suite greps through the tex-file for \labels. My version greps
>>>> through the aux-file. This has the advantage, that one does not have to
>>>> memorize the keys within the \labels for completion, but can use the
>>>> actual labels in the compiled document.
>>>> 
>>>> Hence, you get the following expansions (given that the tex-file has the
>>>> corresponding labels):
>>>>
>>>>     theorem.1.3<F9>   =>   \autoref{thm:bar}
>>>>     section.2<F9>     =>   \autoref{sec:foo}
>>>>     (1.9<F9>          =>   \eqref{eq:baz}
>>>>     (1.9)<F9>         =>   \eqref{eq:baz}
>>>> 
>>>> (You can also reconfigure an option to use \cref (or anything else)
>>>> instead of \autoref)
>>>> 
>>>> This is quite convenient, because you can look in the pdf to get the
>>>> appropriate number of the thing you want to refer to and use this for
>>>> the completion. No need for packages like showkeys.
>>>> 
>>>> The only disadvantage is that you get the labels from the aux-file.
>>>> Hence, if the aux-file is not up-to-date or you use the numbers from a
>>>> print-out (and the aux-file is more recent), you might get unexpected
>>>> results.
>>>> 
>>>> My question is: Can I replace the current style of the completion with
>>>> this aux-based completion in the official repository? This would result
>>>> in less code (less maintenance) and is therefore desirable. However, I
>>>> can understand if someone would like to stay with the current behavior.
>>>> 
>>>> The stage is open for discussion, see also
>>>> https://github.com/vim-latex/vim-latex/issues/55
>>>> 
>>>> 
>>>> Best regards,
>>>> Gerd
>
>

Re: [Vim-latex-devel] Aux completion

[George <geo...@gm...>]

Hi all,



I switched to Gerd's version of vim-latex while I'm writing my thesis.
The reason is that I'm
using tcolorbox[1] to create coloured boxes for my theorems. Tcolorbox
has its own way of
labelling theorems, which does not play well with the label completion
of vim-latex suite.
 

Here is an example to demonstrate. First I define a theorem environment
using tcolorbox,
as follows:

 

    \newtcbtheorem[number within=section]%

    {theorem} % \begin..

    {Theorem} % Title

    {} % Style - default

    {theo} % label prefix; cite as ``theo:yourlabel''

 

Then, inside my document I can write:

 

   \begin{theorem}{The title}{mylabel}

   This is a theorem.

   \end{theorem}

 

and I'll get a theorem inside a coloured box. Then I can cite that
theorem by
writing "\ref{theo:mylabel}".

 

The problem is that if I type "\ref{" and press F9, vim-latex will
not recognise
the label "theo:mylable", so it won't automplete.

 

Gerd's approach fixes this. That said, I understand that this is a
rather special
case, but I just thought of throwing it in the discussion.



Cheers,

George





On Fri, Jan 27, 2017, at 20:42, Gerd Wachsmuth wrote:

> Thank you for your comments.

> 

> I think I was not precise at one point: You still can use labels for

> completion (as long as they are already in the aux file).

> 

> To given an example:

> ========================================

> \documentclass{article}

> \usepackage{hyperref}

> \begin{document}

> \begin{equation}

> \label{eq:einstein}

> E = m \, c^2

> \end{equation}

> \begin{equation}

> a^2 + b^2 = c^2

> \label{eq:pythagoras}

> \end{equation}

> \end{document}

> ========================================

> 

> The current version produces the following outline window:

> ========================================

> >  eq:einstein  </tmp/test.tex>

> :

> >  eq:pythagoras  </tmp/test.tex>

> :    a^2 + b^2 = c^2

> ========================================

> You can only use the labels for completion and you see some of the

> surrounding text.

> 

> The new, aux-based version produces:

> ========================================

> >eq:einstein

> :  (1)

> >eq:pythagoras

> :  (2)

> ========================================

> Here, you can use both, the label and the actual number, with the new
> aux completion. However, you do not see some of the text.

> 

> 

> Moreover, the old mechanism fails to detect if you input some other

> files via macros, e.g.,

>   \newcommand{\myinput}[1]{\input{#1}}

> and then

>   \myinput{test}.

> Since the labels of the file test.tex still appear in the aux
> file, the
> aux based completion also find those labels.

> 

> 

> In my opinion, the only regress is that you have to compile
> (once) after
> entering a new \label{} and before you will be able to complete a

> reference to exactly this label.

> 

> 

> Best regards,

> Gerd

> 

> 

> On 2017-01-27 10:05, Filip Kadlec wrote:

>> Hi, Gerd,

>> 

>> I second Laszlo's point of view; for me, using labels with
>> well chosen
>> names is clearly the best choice, and I think that the latex-
>> suite should
>> keep this behavior by default. To me, the <F9>-completion works
>> quite well
>> and it would maybe need some improvements (it does not work for
>> me with
>> \includegraphics, and if the vim-window is split when invoking
>> <F9> in
>> \cite, it oftentimes fails...) but not a complete change of logic.

>> 

>> Your idea to scan the .aux files could be useful for someone,
>> though. I
>> don't know if it is feasible, but I would suggest an
>> implementation via a
>> command, something like

>> 

>> let g:Tex_completion_scanfile = tex / aux

>> 

>> whereby everyone would have the choice.

>> 

>> This would does not imply less code nor less maintenance, though.

>> 

>>   Best regards,

>>       Filip

>> 

>> On Thu, 26 Jan 2017, N Laszlo Frazer wrote:

>> 

>>> Date: Thu, 26 Jan 2017 21:33:44

>>> From: N Laszlo Frazer <per...@ce...>

>>> To: "vim...@li..."

>>>   <vim...@li...>

>>> Subject: Re: [Vim-latex-devel] Aux completion

>>> 

>>> Please do not remove the current functionality.  I think it would
>>> be very
>>> annoying to rely on the aux file being up-to-date.

>>> 

>>> Well-chosen keys are much easier to remember than numbers, and
>>> they do
>>> not

>>> change when you expand the document.

>>> 

>>> On Fri, 27 Jan 2017 00:52:25 +1100, Gerd Wachsmuth

>>> <ger...@ma...> wrote:

>>> 

>>>> Hi,

>>>> 

>>>> in my version of latex-suite
>>>> (https://github.com/gerw/vim-latex-suite),
>>>> I have changed the mechanism of \ref-completions. The current
>>>> version of
>>>> latex-suite greps through the tex-file for \labels. My version
>>>> greps
>>>> through the aux-file. This has the advantage, that one does not
>>>> have to
>>>> memorize the keys within the \labels for completion, but can
>>>> use the
>>>> actual labels in the compiled document.

>>>> 

>>>> Hence, you get the following expansions (given that the tex-file
>>>> has the
>>>> corresponding labels):

>>>> 

>>>>   theorem.1.3<F9>   =>   \autoref{thm:bar}

>>>>   section.2<F9>     =>   \autoref{sec:foo}

>>>>   (1.9<F9>          =>   \eqref{eq:baz}

>>>>   (1.9)<F9>         =>   \eqref{eq:baz}

>>>> 

>>>> (You can also reconfigure an option to use \cref (or anything else)
>>>> instead of \autoref)

>>>> 

>>>> This is quite convenient, because you can look in the pdf to
>>>> get the
>>>> appropriate number of the thing you want to refer to and use
>>>> this for
>>>> the completion. No need for packages like showkeys.

>>>> 

>>>> The only disadvantage is that you get the labels from the aux-file.
>>>> Hence, if the aux-file is not up-to-date or you use the numbers
>>>> from a
>>>> print-out (and the aux-file is more recent), you might get
>>>> unexpected
>>>> results.

>>>> 

>>>> My question is: Can I replace the current style of the
>>>> completion with
>>>> this aux-based completion in the official repository? This would
>>>> result
>>>> in less code (less maintenance) and is therefore desirable.
>>>> However, I
>>>> can understand if someone would like to stay with the current
>>>> behavior.
>>>> 

>>>> The stage is open for discussion, see also

>>>> https://github.com/vim-latex/vim-latex/issues/55

>>>> 

>>>> 

>>>> Best regards,

>>>> Gerd

> 

> 

> ----------------------------------------------------------------------
> --------
> 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




Links:

  1. https://www.ctan.org/pkg/tcolorbox?lang=en

Re: [Vim-latex-devel] Aux completion

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

Thank you for your comments.

I think I was not precise at one point: You still can use labels for 
completion (as long as they are already in the aux file).

To given an example:
========================================
\documentclass{article}
\usepackage{hyperref}
\begin{document}
\begin{equation}
	\label{eq:einstein}
	E = m \, c^2
\end{equation}
\begin{equation}
	a^2 + b^2 = c^2
	\label{eq:pythagoras}
\end{equation}
\end{document}
========================================

The current version produces the following outline window:
========================================
 >  eq:einstein		</tmp/test.tex>
:
 >  eq:pythagoras		</tmp/test.tex>
:    a^2 + b^2 = c^2
========================================
You can only use the labels for completion and you see some of the 
surrounding text.

The new, aux-based version produces:
========================================
 >eq:einstein
:  (1)
 >eq:pythagoras
:  (2)
========================================
Here, you can use both, the label and the actual number, with the new 
aux completion. However, you do not see some of the text.


Moreover, the old mechanism fails to detect if you input some other 
files via macros, e.g.,
   \newcommand{\myinput}[1]{\input{#1}}
and then
   \myinput{test}.
Since the labels of the file test.tex still appear in the aux file, the 
aux based completion also find those labels.


In my opinion, the only regress is that you have to compile (once) after 
entering a new \label{} and before you will be able to complete a 
reference to exactly this label.


Best regards,
Gerd


On 2017-01-27 10:05, Filip Kadlec wrote:
> Hi, Gerd,
>
>  I second Laszlo's point of view; for me, using labels with well chosen
> names is clearly the best choice, and I think that the latex-suite should
> keep this behavior by default. To me, the <F9>-completion works quite well
> and it would maybe need some improvements (it does not work for me with
> \includegraphics, and if the vim-window is split when invoking <F9> in
> \cite, it oftentimes fails...) but not a complete change of logic.
>
>  Your idea to scan the .aux files could be useful for someone, though. I
> don't know if it is feasible, but I would suggest an implementation via a
> command, something like
>
>  let g:Tex_completion_scanfile = tex / aux
>
> whereby everyone would have the choice.
>
> This would does not imply less code nor less maintenance, though.
>
>     Best regards,
>         Filip
>
> On Thu, 26 Jan 2017, N Laszlo Frazer wrote:
>
>> Date: Thu, 26 Jan 2017 21:33:44
>> From: N Laszlo Frazer <per...@ce...>
>> To: "vim...@li..."
>>    <vim...@li...>
>> Subject: Re: [Vim-latex-devel] Aux completion
>>
>> Please do not remove the current functionality.  I think it would be very
>> annoying to rely on the aux file being up-to-date.
>>
>> Well-chosen keys are much easier to remember than numbers, and they do
>> not
>> change when you expand the document.
>>
>> On Fri, 27 Jan 2017 00:52:25 +1100, Gerd Wachsmuth
>> <ger...@ma...> wrote:
>>
>>> Hi,
>>>
>>> in my version of latex-suite (https://github.com/gerw/vim-latex-suite),
>>> I have changed the mechanism of \ref-completions. The current version of
>>> latex-suite greps through the tex-file for \labels. My version greps
>>> through the aux-file. This has the advantage, that one does not have to
>>> memorize the keys within the \labels for completion, but can use the
>>> actual labels in the compiled document.
>>>
>>> Hence, you get the following expansions (given that the tex-file has the
>>> corresponding labels):
>>>
>>>     theorem.1.3<F9>   =>   \autoref{thm:bar}
>>>     section.2<F9>     =>   \autoref{sec:foo}
>>>     (1.9<F9>          =>   \eqref{eq:baz}
>>>     (1.9)<F9>         =>   \eqref{eq:baz}
>>>
>>> (You can also reconfigure an option to use \cref (or anything else)
>>> instead of \autoref)
>>>
>>> This is quite convenient, because you can look in the pdf to get the
>>> appropriate number of the thing you want to refer to and use this for
>>> the completion. No need for packages like showkeys.
>>>
>>> The only disadvantage is that you get the labels from the aux-file.
>>> Hence, if the aux-file is not up-to-date or you use the numbers from a
>>> print-out (and the aux-file is more recent), you might get unexpected
>>> results.
>>>
>>> My question is: Can I replace the current style of the completion with
>>> this aux-based completion in the official repository? This would result
>>> in less code (less maintenance) and is therefore desirable. However, I
>>> can understand if someone would like to stay with the current behavior.
>>>
>>> The stage is open for discussion, see also
>>> https://github.com/vim-latex/vim-latex/issues/55
>>>
>>>
>>> Best regards,
>>> Gerd

Re: [Vim-latex-devel] Aux completion

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

Hi, Gerd,

  I second Laszlo's point of view; for me, using labels with well chosen
names is clearly the best choice, and I think that the latex-suite should
keep this behavior by default. To me, the <F9>-completion works quite well
and it would maybe need some improvements (it does not work for me with
\includegraphics, and if the vim-window is split when invoking <F9> in
\cite, it oftentimes fails...) but not a complete change of logic.

  Your idea to scan the .aux files could be useful for someone, though. I
don't know if it is feasible, but I would suggest an implementation via a
command, something like

  let g:Tex_completion_scanfile = tex / aux

whereby everyone would have the choice.

This would does not imply less code nor less maintenance, though.

 	Best regards,
 		Filip

On Thu, 26 Jan 2017, N Laszlo Frazer wrote:

>Date: Thu, 26 Jan 2017 21:33:44
>From: N Laszlo Frazer <per...@ce...>
>To: "vim...@li..."
>    <vim...@li...>
>Subject: Re: [Vim-latex-devel] Aux completion
>
> Please do not remove the current functionality.  I think it would be very
> annoying to rely on the aux file being up-to-date.
>
> Well-chosen keys are much easier to remember than numbers, and they do not
> change when you expand the document.
>
> On Fri, 27 Jan 2017 00:52:25 +1100, Gerd Wachsmuth
> <ger...@ma...> wrote:
>
>> Hi,
>>
>> in my version of latex-suite (https://github.com/gerw/vim-latex-suite),
>> I have changed the mechanism of \ref-completions. The current version of
>> latex-suite greps through the tex-file for \labels. My version greps
>> through the aux-file. This has the advantage, that one does not have to
>> memorize the keys within the \labels for completion, but can use the
>> actual labels in the compiled document.
>>
>> Hence, you get the following expansions (given that the tex-file has the
>> corresponding labels):
>>
>> 	theorem.1.3<F9>   =>   \autoref{thm:bar}
>> 	section.2<F9>     =>   \autoref{sec:foo}
>> 	(1.9<F9>          =>   \eqref{eq:baz}
>> 	(1.9)<F9>         =>   \eqref{eq:baz}
>>
>> (You can also reconfigure an option to use \cref (or anything else)
>> instead of \autoref)
>>
>> This is quite convenient, because you can look in the pdf to get the
>> appropriate number of the thing you want to refer to and use this for
>> the completion. No need for packages like showkeys.
>>
>> The only disadvantage is that you get the labels from the aux-file.
>> Hence, if the aux-file is not up-to-date or you use the numbers from a
>> print-out (and the aux-file is more recent), you might get unexpected
>> results.
>>
>> My question is: Can I replace the current style of the completion with
>> this aux-based completion in the official repository? This would result
>> in less code (less maintenance) and is therefore desirable. However, I
>> can understand if someone would like to stay with the current behavior.
>>
>> The stage is open for discussion, see also
>> https://github.com/vim-latex/vim-latex/issues/55
>>
>>
>> Best regards,
>> Gerd
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
> ------------------------------------------------------------------------------
> 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
>

Re: [Vim-latex-devel] Aux completion

[N L. F. <per...@ce...>]

Please do not remove the current functionality.  I think it would be very  
annoying to rely on the aux file being up-to-date.

Well-chosen keys are much easier to remember than numbers, and they do not  
change when you expand the document.

On Fri, 27 Jan 2017 00:52:25 +1100, Gerd Wachsmuth  
<ger...@ma...> wrote:

> Hi,
>
> in my version of latex-suite (https://github.com/gerw/vim-latex-suite),
> I have changed the mechanism of \ref-completions. The current version of
> latex-suite greps through the tex-file for \labels. My version greps
> through the aux-file. This has the advantage, that one does not have to
> memorize the keys within the \labels for completion, but can use the
> actual labels in the compiled document.
>
> Hence, you get the following expansions (given that the tex-file has the
> corresponding labels):
>
> 	theorem.1.3<F9>   =>   \autoref{thm:bar}
> 	section.2<F9>     =>   \autoref{sec:foo}
> 	(1.9<F9>          =>   \eqref{eq:baz}
> 	(1.9)<F9>         =>   \eqref{eq:baz}
>
> (You can also reconfigure an option to use \cref (or anything else)
> instead of \autoref)
>
> This is quite convenient, because you can look in the pdf to get the
> appropriate number of the thing you want to refer to and use this for
> the completion. No need for packages like showkeys.
>
> The only disadvantage is that you get the labels from the aux-file.
> Hence, if the aux-file is not up-to-date or you use the numbers from a
> print-out (and the aux-file is more recent), you might get unexpected
> results.
>
> My question is: Can I replace the current style of the completion with
> this aux-based completion in the official repository? This would result
> in less code (less maintenance) and is therefore desirable. However, I
> can understand if someone would like to stay with the current behavior.
>
> The stage is open for discussion, see also
> https://github.com/vim-latex/vim-latex/issues/55
>
>
> Best regards,
> Gerd
>
>
> ------------------------------------------------------------------------------
> 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] Aux completion

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

Hi,

in my version of latex-suite (https://github.com/gerw/vim-latex-suite), 
I have changed the mechanism of \ref-completions. The current version of 
latex-suite greps through the tex-file for \labels. My version greps 
through the aux-file. This has the advantage, that one does not have to 
memorize the keys within the \labels for completion, but can use the 
actual labels in the compiled document.

Hence, you get the following expansions (given that the tex-file has the 
corresponding labels):

	theorem.1.3<F9>   =>   \autoref{thm:bar}
	section.2<F9>     =>   \autoref{sec:foo}
	(1.9<F9>          =>   \eqref{eq:baz}
	(1.9)<F9>         =>   \eqref{eq:baz}

(You can also reconfigure an option to use \cref (or anything else) 
instead of \autoref)

This is quite convenient, because you can look in the pdf to get the 
appropriate number of the thing you want to refer to and use this for 
the completion. No need for packages like showkeys.

The only disadvantage is that you get the labels from the aux-file. 
Hence, if the aux-file is not up-to-date or you use the numbers from a 
print-out (and the aux-file is more recent), you might get unexpected 
results.

My question is: Can I replace the current style of the completion with 
this aux-based completion in the official repository? This would result 
in less code (less maintenance) and is therefore desirable. However, I 
can understand if someone would like to stay with the current behavior.

The stage is open for discussion, see also 
https://github.com/vim-latex/vim-latex/issues/55


Best regards,
Gerd

Re: [Vim-latex-devel] spell

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

Hi,

latex-suite does not deal with the spell checking. Which part of the 
tex-file is spell-checked depends on the syntax file (syntax/tex.vim), 
which is not provided by the latex-suite.

Best regards,
Gerd

On 2016-10-20 19:32, Le Cocq wrote:
> Hello.
>
> Although I have activated spell in french, the highlighting of
> misspelled words have a strange behavior. Sometimes just sentences in
> comments or in brackets are verified, sometimes wrong words in the text
> are detected. I do not understand when it works or not, it can be in the
> same session of text editing, after a compilation, or when I add or
> delete a file.
>
> In help spell I noticed remarks on performance, but I do not understand
> really how it could help me.
>
> Vim does on-the-fly spell checking.  To make this work fast the word list is
> loaded in memory.  Thus this uses a lot of memory (1 Mbyte or more).  There
> might also be a noticeable delay when the word list is loaded, which happens
> when 'spell' is set and when 'spelllang' is set while 'spell' was
> already set.
> To minimize the delay each word list is only loaded once, it is not deleted
> when 'spelllang' is made empty or 'spell' is reset.  When 'encoding' is set
> all the word lists are reloaded, thus you may notice a delay then too.
>
> In ~/.vim/ftplugin/tex.vim I have the following lines about spell checking :
>
> :set spell spelllang=fr,en        "français et anglais
> :syntax spell toplevel                "activé
> :let g:tex_verbspell=1                "prenant en compte les commandes LaTeX
>
> The file I am writing contains 650 lines on a computer with 8 Go of
> physical memory.
>
> Could someone help me ? Thank you.
>
>

[Vim-latex-devel] spell

[Le C. <car...@ov...>]

Hello.

Although I have activated spell in french, the highlighting of 
misspelled words have a strange behavior. Sometimes just sentences in 
comments or in brackets are verified, sometimes wrong words in the text 
are detected. I do not understand when it works or not, it can be in the 
same session of text editing, after a compilation, or when I add or 
delete a file.

In help spell I noticed remarks on performance, but I do not understand 
really how it could help me.

Vim does on-the-fly spell checking.  To make this work fast the word list is
loaded in memory.  Thus this uses a lot of memory (1 Mbyte or more).  There
might also be a noticeable delay when the word list is loaded, which happens
when 'spell' is set and when 'spelllang' is set while 'spell' was 
already set.
To minimize the delay each word list is only loaded once, it is not deleted
when 'spelllang' is made empty or 'spell' is reset.  When 'encoding' is set
all the word lists are reloaded, thus you may notice a delay then too.

In ~/.vim/ftplugin/tex.vim I have the following lines about spell checking :

:set spell spelllang=fr,en        "français et anglais
:syntax spell toplevel                "activé
:let g:tex_verbspell=1                "prenant en compte les commandes LaTeX

The file I am writing contains 650 lines on a computer with 8 Go of 
physical memory.

Could someone help me ? Thank you.


-- 
pierrO

Re: [Vim-latex-devel] Bug? SmartDots in Vim 8

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

Hi,

I think this is an issue with the compatibility mode of vim. What does

:set compatible?
:set cpoptions?

say? You may want to add

set nocompatible

at the beginning of your vimrc file.

Best regards,
Gerd


On 2016-10-20 11:44, Christoffer Østfeldt wrote:
> Hi there
>
> I am experiencing what i perceive to be an error with vim-latex and vim
> 8. Vim 8 is completely fresh, compiled from latest version on github on
> ubuntu 14.04.
>
> ~$ vim --version
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct 18 2016 09:52:55)
> Included patches: 1-42
> Compiled by christoffer@chrisNotebook
> Huge version with GTK2 GUI.  Features included (+) or not (-):
> +acl             +file_in_path    +mouse_sgr       +tag_old_static
> +arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
> +autocmd         +float           +mouse_urxvt     -tcl
> +balloon_eval    +folding         +mouse_xterm     +termguicolors
> +browse          -footer          +multi_byte      +terminfo
> ++builtin_terms  +fork()          +multi_lang      +termresponse
> +byte_offset     +gettext         -mzscheme        +textobjects
> +channel         -hangul_input    +netbeans_intg   +timers
> +cindent         +iconv           +num64           +title
> +clientserver    +insert_expand   +packages        +toolbar
> +clipboard       +job             +path_extra      +user_commands
> +cmdline_compl   +jumplist        +perl            +vertsplit
> +cmdline_hist    +keymap          +persistent_undo +virtualedit
> +cmdline_info    +lambda          +postscript      +visual
> +comments        +langmap         +printer         +visualextra
> +conceal         +libcall         +profile         +viminfo
> +cryptv          +linebreak       -python          +vreplace
> +cscope          +lispindent      +python3         +wildignore
> +cursorbind      +listcmds        +quickfix        +wildmenu
> +cursorshape     +localmap        +reltime         +windows
> +dialog_con_gui  +lua             +rightleft       +writebackup
> +diff            +menu            +ruby            +X11
> +digraphs        +mksession       +scrollbind      -xfontset
> +dnd             +modify_fname    +signs           +xim
> -ebcdic          +mouse           +smartindent     +xpm
> +emacs_tags      +mouseshape      +startuptime     +xsmp_interact
> +eval            +mouse_dec       +statusline      +xterm_clipboard
> +ex_extra        +mouse_gpm       -sun_workshop    -xterm_save
> +extra_search    -mouse_jsbterm   +syntax
> +farsi           +mouse_netterm   +tag_binary
>    system vimrc file: "$VIM/vimrc"
>      user vimrc file: "$HOME/.vimrc"
>  2nd user vimrc file: "~/.vim/vimrc"
>       user exrc file: "$HOME/.exrc"
>   system gvimrc file: "$VIM/gvimrc"
>     user gvimrc file: "$HOME/.gvimrc"
> 2nd user gvimrc file: "~/.vim/gvimrc"
>        defaults file: "$VIMRUNTIME/defaults.vim"
>     system menu file: "$VIMRUNTIME/menu.vim"
>   fall-back for $VIM: "/usr/share/vim"
>  f-b for $VIMRUNTIME: "/usr/share/vim/vim80"
> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0
> -I/usr/include/gio-unix-2.0/ -I/usr/include/freetype2
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/harfbuzz
>     -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> Linking: gcc   -L. -Wl,-Bsymbolic-functions -Wl,-z,relro
> -L/build/buildd/ruby1.9.1-1.9.3.484/debian/lib -rdynamic
> -Wl,-export-dynamic -Wl,-E   -L/usr/local/lib -Wl,--as-needed -o vim
> -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
> -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig
> -lgobject-2.0 -lglib-2.0 -lfreetype   -lSM -lICE -lXpm -lXt -lX11
> -lXdmcp -lSM -lICE  -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm
> -ldl  -L/usr/lib -llua5.2 -Wl,-E  -fstack-protector -L/usr/local/lib
>  -L/usr/lib/perl/5.18/CORE -lperl -ldl -lm -lpthread -lcrypt
>  -L/home/christoffer/anaconda3/lib/python3.5/config-3.5m -lpython3.5m
> -lpthread -ldl -lutil -lrt -lm  -lruby-1.9.1 -lpthread -lrt -ldl -lcrypt
> -lm  -L/usr/lib
>
> Opening gvim, inserting the article templating and pressing:
> "i-H-e-j-.-Esc" i obtain the following:
>
> %        File: article.tex
> %     Created: Thu Oct 20 11:00 AM 2016 C
> % Last Change: Thu Oct 20 11:00 AM 2016 C
> %
> \documentclass[a4paper]{article}
> \begin{document}
> Hej<C-R>=<SID>SmartDots()<CR>
> \end{document}
>
> My .vimrc is exactly like the one suggested here:
> http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html
>
> I have tried searching for suggestions on fixing this issue, but without
> any luck.
>
> Sincerely
> Christoffer
>
>
> ------------------------------------------------------------------------------
> 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] Bug? SmartDots in Vim 8

[Christoffer Ø. <chr...@gm...>]

Hi there

I am experiencing what i perceive to be an error with vim-latex and vim 8.
Vim 8 is completely fresh, compiled from latest version on github on ubuntu
14.04.

~$ vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct 18 2016 09:52:55)
Included patches: 1-42
Compiled by christoffer@chrisNotebook
Huge version with GTK2 GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_old_static
+arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           +mouse_urxvt     -tcl
+balloon_eval    +folding         +mouse_xterm     +termguicolors
+browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     +gettext         -mzscheme        +textobjects
+channel         -hangul_input    +netbeans_intg   +timers
+cindent         +iconv           +num64           +title
+clientserver    +insert_expand   +packages        +toolbar
+clipboard       +job             +path_extra      +user_commands
+cmdline_compl   +jumplist        +perl            +vertsplit
+cmdline_hist    +keymap          +persistent_undo +virtualedit
+cmdline_info    +lambda          +postscript      +visual
+comments        +langmap         +printer         +visualextra
+conceal         +libcall         +profile         +viminfo
+cryptv          +linebreak       -python          +vreplace
+cscope          +lispindent      +python3         +wildignore
+cursorbind      +listcmds        +quickfix        +wildmenu
+cursorshape     +localmap        +reltime         +windows
+dialog_con_gui  +lua             +rightleft       +writebackup
+diff            +menu            +ruby            +X11
+digraphs        +mksession       +scrollbind      -xfontset
+dnd             +modify_fname    +signs           +xim
-ebcdic          +mouse           +smartindent     +xpm
+emacs_tags      +mouseshape      +startuptime     +xsmp_interact
+eval            +mouse_dec       +statusline      +xterm_clipboard
+ex_extra        +mouse_gpm       -sun_workshop    -xterm_save
+extra_search    -mouse_jsbterm   +syntax
+farsi           +mouse_netterm   +tag_binary
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/share/vim"
 f-b for $VIMRUNTIME: "/usr/share/vim/vim80"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/
-I/usr/include/freetype2 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/libpng12 -I/usr/include/harfbuzz     -g -O2
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L. -Wl,-Bsymbolic-functions -Wl,-z,relro
-L/build/buildd/ruby1.9.1-1.9.3.484/debian/lib -rdynamic
-Wl,-export-dynamic -Wl,-E   -L/usr/local/lib -Wl,--as-needed -o vim
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
-lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig
-lgobject-2.0 -lglib-2.0 -lfreetype   -lSM -lICE -lXpm -lXt -lX11 -lXdmcp
-lSM -lICE  -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl
 -L/usr/lib -llua5.2 -Wl,-E  -fstack-protector -L/usr/local/lib
 -L/usr/lib/perl/5.18/CORE -lperl -ldl -lm -lpthread -lcrypt
 -L/home/christoffer/anaconda3/lib/python3.5/config-3.5m -lpython3.5m
-lpthread -ldl -lutil -lrt -lm  -lruby-1.9.1 -lpthread -lrt -ldl -lcrypt
-lm  -L/usr/lib

Opening gvim, inserting the article templating and pressing:
"i-H-e-j-.-Esc" i obtain the following:

%        File: article.tex
%     Created: Thu Oct 20 11:00 AM 2016 C
% Last Change: Thu Oct 20 11:00 AM 2016 C
%
\documentclass[a4paper]{article}
\begin{document}
Hej<C-R>=<SID>SmartDots()<CR>
\end{document}

My .vimrc is exactly like the one suggested here:
http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html

I have tried searching for suggestions on fixing this issue, but without
any luck.

Sincerely
Christoffer

Re: [Vim-latex-devel] How to prevent latex-suite from loading

[David N. <ye...@ph...>]

On Wed, Oct 05, 2016 at 10:55:33AM +0200, Gerd Wachsmuth wrote:
> this was not possible up to now. I have pushed a fix to this problem to the
> upstream git repository (https://github.com/vim-latex/vim-latex). However,
> this will not help you, since there will be some lag until this is included
> in package managers.
> 
> So you could also try to convince/force your admin to install the most
> recent version of latex-suite (or, of course, to remove it).

OK, thanks for the fix (for the future) and information.  Currently I
simply did ‘filetype plugin off’ and only enable it when I actually need
some ftplugin (which is not that often as this setting no longer breaks
reading compressed vim help files) but I am looking forward to the more
fine-grained control with suppress_latex_suite.

Regards,

Yeti

Re: [Vim-latex-devel] How to prevent latex-suite from loading

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

Hi,

this was not possible up to now. I have pushed a fix to this problem to 
the upstream git repository (https://github.com/vim-latex/vim-latex). 
However, this will not help you, since there will be some lag until this 
is included in package managers.

So you could also try to convince/force your admin to install the most 
recent version of latex-suite (or, of course, to remove it).

Best regards,
Gerd


On 10/04/2016 04:07 PM, David Nečas wrote:
>
> Hello guys,
>
> recently latex-suite was installed into the system on a machine I use.
> I have a custom TeX highlighting and other setup (focused on generic TeX
> and low-level macro development so, no, latex-suite is not for me) and I
> started getting **lots** of errors when opening any TeX file due to some
> clashes.
>
> First I thought, well, there would be some variable like
> b:latex_suite_already_loaded that I set to prevent it from loading.  But
> I did not find any.
>
> So I googled and searched and found this unanswered post from 2011 in
> this very mailing list
>
>      https://sourceforge.net/p/vim-latex/mailman/message/27393051/
>
> Is it really possible to disable latex-suite by convincing the admin of
> the system to physically remove it?
>
> Thanks,
>
> Yeti
>
>
> ------------------------------------------------------------------------------
> 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] How to prevent latex-suite from loading

[David N. <ye...@ph...>]

Hello guys,

recently latex-suite was installed into the system on a machine I use.
I have a custom TeX highlighting and other setup (focused on generic TeX
and low-level macro development so, no, latex-suite is not for me) and I
started getting **lots** of errors when opening any TeX file due to some
clashes.

First I thought, well, there would be some variable like
b:latex_suite_already_loaded that I set to prevent it from loading.  But
I did not find any.

So I googled and searched and found this unanswered post from 2011 in
this very mailing list

    https://sourceforge.net/p/vim-latex/mailman/message/27393051/

Is it really possible to disable latex-suite by convincing the admin of
the system to physically remove it?

Thanks,

Yeti

Re: [Vim-latex-devel] addition to manuals

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

Hi,

what about

http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html

?

I agree that the download instructions at

http://vim-latex.sourceforge.net/index.php?subject=download

could be enhanced by mentioning:
- the direct cloning of the github repository
- usage of Vundle/pathogen

Best regards,
Gerd


On 09/23/2016 06:46 AM, Laszlo Frazer wrote:
> Hi,
>
> Could instructions on the use of vim-addons be added to the manual?  Here's an example.
>
> http://deblogian.blogspot.com.au/2011/11/how-to-install-vim-latexsuite-in-debian.html
>
> It would be a big help to those of us who only do it every five years or so.
>
> Laszlo
>
>
> --
>
> Laszlo Frazer
>
> Research Associate, UNSW Australia
> Room 411, Building F10
> Email is a good way to reach me.
> +61 401 648 058
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] addition to manuals

[Laszlo F. <per...@ce...>]

Hi,

Could instructions on the use of vim-addons be added to the manual?  Here's an example.

http://deblogian.blogspot.com.au/2011/11/how-to-install-vim-latexsuite-in-debian.html

It would be a big help to those of us who only do it every five years or so.

Laszlo


--

Laszlo Frazer

Research Associate, UNSW Australia
Room 411, Building F10
Email is a good way to reach me.
+61 401 648 058

Re: [Vim-latex-devel] spell problem

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

Hi PierrO,

  I had a similar problem with .tex files some time ago. The behavior has 
much improved when I added to my .vimrc these lines:

set spell linebreak
syntax spell toplevel

Since then, spelling stops working only exceptionally in some longer files
with several hundred lines, and this may have something to do with
folding.  Often, re-loading the file or reformatting restores the
spelling.

Hope this will help you.

Filip


On Wed, 17 Aug 2016, Le Cocq wrote:

>Date: Wed, 17 Aug 2016 19:10:16
>From: Le Cocq <car...@ov...>
>To: vim...@li...
>Subject: [Vim-latex-devel] spell problem
>
> Hi,
>
> I activated in vain : spell spelllang=fr
>
> But when I am working with several files, spelling is activated in some
> of them, or only in comments or inside a command in the first loaded
> file. I do not remember if a keyword is defined and do not know where is
> the configuration file.
>
> Could you help a beginner since 2 years ;)
>
>

[Vim-latex-devel] vimlatex and synctex

[Guido M. <gui...@un...>]

Hello,
I have just installed TexLive-2016 and vimlatex. All right, except that 
I was trying to find a good system to synchronize LaTeX source and PDF 
viewer. For some reasons, the system that I found here:

http://debdeep777.blogspot.it/2015/01/vim-texlive-vim-latex-suite-zathura-pdf.html

does not work now. I still use the old configurations files, so I cannot 
understand what's wrong.

Anyway, zathura does a good job with old files accompanied by a 
*filename.synctex.gz* file, but nothing happens with the new projects.

I tried to configure both

let g:Tex_ViewRule_pdf = 'zathura'

and

let g:Tex_ViewRule_pdf = 'zathura -x "gvim --servername synctex -n 
--remote-silent +\%{line} \%{input}"'

evince does not work either.

Thank you for your kind help. Incidentally, I was wondering if the 
installation instructions could be updated -- at least for (x)ubuntu 
they do not work and the installation must be performed differently.

guido (italy)
-- 
Guido Milanese
Professor of Classics, Docteur HC Paris ICP
http://docenti.unicatt.it/ita/guido_fabrizio_milanese/
http://usi.to/tz4

[Vim-latex-devel] spell problem

[Le C. <car...@ov...>]

Hi,

I activated in vain : spell spelllang=fr

But when I am working with several files, spelling is activated in some 
of them, or only in comments or inside a command in the first loaded 
file. I do not remember if a keyword is defined and do not know where is 
the configuration file.

Could you help a beginner since 2 years ;)

-- 
pierrO