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

Re: [Vim-latex-devel] foldcolumn disappeared

[Ruthard B. <rut...@we...>]

>== Auszüge aus der Nachricht von  Filip Kadlec vom 2014-12-19 09:56:
> Hello everyone,
> 
>   after a distribution upgrade, my vim-latex still works as before, but I 
> have noticed that in the .tex files, the foldcolumn does not appear 
> although the folds exist. Previously, I did not modify my personal 
> settings for folds since everything worked normally. I have tried to look 
> into the vim-latex suite FAQ and manual but I found no simple solution. 
> Can anybody help me please about the best way to proceed. Of course, I 
> could set foldcolumn=4 but this would affect all open files, not only 
> .tex, which I do not wish.
> 
>      Best regards,
>          Filip
> 

Hello Filip,

I don't know a latex-suite-ish solution to this, but local
custumizations to vim should be put in `.vim/after/` – these files are
loaded _after_ the main configuration files are loaded, thus overriding
them.

The `ftplugin` directories are for FileTypePLUGINs (hence the name), the
name of the files in this directory should start with the file type's
name.

Thus, putting a file named `tex.vim` in the directory
`.vim/after/ftplugin/` containing the line
`set foldcolumn=4` would set foldcolumn to 4 only for tex files and
would not be overridden by updates.

Best regards,

Ruthard

-- 

Dr. Ruthard Baudach
Speckertsweg 36a
97209 Veitshöchheim
----

Emails bitte verschlüsseln und signieren.
Meine PGP-Id: 0xAC5AC6C2

[Vim-latex-devel] foldcolumn disappeared

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

Hello everyone,

  after a distribution upgrade, my vim-latex still works as before, but I 
have noticed that in the .tex files, the foldcolumn does not appear 
although the folds exist. Previously, I did not modify my personal 
settings for folds since everything worked normally. I have tried to look 
into the vim-latex suite FAQ and manual but I found no simple solution. 
Can anybody help me please about the best way to proceed. Of course, I 
could set foldcolumn=4 but this would affect all open files, not only 
.tex, which I do not wish.

 	Best regards,
 		Filip

Re: [Vim-latex-devel] [PATCH] Trigger citation completion on \Cite as well as \cite.

[Till M. <ope...@ti...>]

On Tue, Feb 04, 2014 at 03:10:12PM +0100, Arne Skjærholt wrote:
> I use BibLaTeX for my references, which has a \Cite* family of
> citation commands. The attached patch makes <F9> completion work with
> these commands too.

Thank you, applied in c9a8d973cc72beb42457e213fbc8ad498559990d.

Regards
Till

Re: [Vim-latex-devel] abbreviations with <shift><enter>

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

Hi,

this seems to be a strange interaction with the IMAP-features of the
latex-suite.

I tried

:iab a (m)
:iab m [a]

Now,
a<space>  =>  (m)
a<s-space> => ([a])

Here, first a is expanded to (m) and the inner m is expanded to [a].

If one uses

let Imap_FreezeImap=1

<space> triggers no expansions, but <s-space> works correctly.


I have no clue how to fix this.

Best regards,
Gerd

On 09/30/2014 11:38 AM, Luca Innocenti wrote:
> Hi I noticed the following behaviour which I didn't find documented
> on the guide. It only happens with gvim (not with vim), on .tex
> files, hence I guess is due to vim-latex.
>
> Defining an insert-mode abbreviation with (for example)
>
> :iab m <m>
>
> I get the expected behaviour writing in insert mode
>
> m<space>
>
> However, if I use <shift>+<space> instead of just <space>:
>
> m<shift><space>
>
> I get the "container" characters to be doubled:
>
> m<shift><space>    produces    <<m>>
>
> This seems to work with any "container" characters, like e.g.
>
> :iab m \m\ :iab m \(m\) :iab m £%m£%
>
> It doesn not happen with letters: in
>
> :iab m ama
>
> the "a" is not doubled.
>
> Is this a feature? If yes, where is it documented?
>
> Thanks
>
>
>
> ------------------------------------------------------------------------------
>
>
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download
> White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
> EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
>
>
>
> _______________________________________________ Vim-latex-devel
> mailing list Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] abbreviations with <shift><enter>

[Luca I. <luk...@gm...>]

Hi
I noticed the following behaviour which I didn't find documented on the
guide.
It only happens with gvim (not with vim), on .tex files, hence I guess is
due to vim-latex.

Defining an insert-mode abbreviation with (for example)

:iab m <m>

I get the expected behaviour writing in insert mode

m<space>

However, if I use <shift>+<space> instead of just <space>:

m<shift><space>

I get the "container" characters to be doubled:

m<shift><space>    produces    <<m>>

This seems to work with any "container" characters, like e.g.

:iab m \m\
:iab m \(m\)
:iab m £%m£%

It doesn not happen with letters: in

:iab m ama

the "a" is not doubled.

Is this a feature? If yes, where is it documented?

Thanks

Re: [Vim-latex-devel] change the figure environment

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

Hi,

s:figure_graphicx is invoked, if the graphicx package is detected. If 
the automatic detection does not work for you (and you always use the 
graphicx package), you could put


"" Add graphicx to the detected packages (such that EFI uses 
\includegraphics)
if !exists("g:Tex_package_detected")
	let g:Tex_package_detected = 'graphicx'
elseif g:Tex_package_detected !~ '\<graphicx\>'
	let g:Tex_package_detected = g:Tex_package_detected.',graphicx'
endif


into your .vim/after/tex.vim.

Best regards,
Gerd


On 09/24/2014 06:15 PM, Rudra Banerjee wrote:
> Hi,
> In latex-suite, there is two shortcut for figure:
>   let s:figure =     "\\begin{figure}[<+htpb+>]\<cr>\\centering\<cr>\
> \psfig{figure=<+eps file+>}\<cr>\\caption{<+caption text+>}\<cr>\
> \label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
> s:end_with_cr . "<++>"
> let s:figure_graphicx =    "\\begin{figure}[<+htpb+>]\<cr>\\centering
> \<cr>\\includegraphics{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\
> \label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
> s:end_with_cr . "<++>"
> But, the shortcut EFI is only given for s:figure.
> can I possibly define EFI to trigger s:figure_graphicx (may be in
> my .vimrc?)
> Thanks
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] change the figure environment

[Rudra B. <bnr...@li...>]

Hi,
In latex-suite, there is two shortcut for figure:
 let s:figure =     "\\begin{figure}[<+htpb+>]\<cr>\\centering\<cr>\
\psfig{figure=<+eps file+>}\<cr>\\caption{<+caption text+>}\<cr>\
\label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
s:end_with_cr . "<++>"
let s:figure_graphicx =    "\\begin{figure}[<+htpb+>]\<cr>\\centering
\<cr>\\includegraphics{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\
\label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
s:end_with_cr . "<++>"
But, the shortcut EFI is only given for s:figure.
can I possibly define EFI to trigger s:figure_graphicx (may be in
my .vimrc?)
Thanks

[Vim-latex-devel] Trouble with shortcuts.

[Visakha R. <vis...@gm...>]

Hello.

I recently installed the vim latex-suite in my Windows computer. The vim
installation is portable vim, version 7.4. I use Windows 7 OS. Installation
files were downloaded from this link (
http://sourceforge.net/projects/vim-latex/files/latest/download?source=files)
and was carried out by copying the files into the vim folder structure in
Data\settings\vimfiles folder.

The help says that typing shortcuts puts intended text into a tex file. Say
`p inserts \pi. This works for me. However, the shortcut keystrokes are not
replaced as soon as I type them rather they are appended with the command
intended for shortcut. Thus typing `p results in `p\pi rather than the
typed `p getting replaced with \pi. The problem is for any file with a .tex
extension. Simply opening a .tex file by typing :e somefile.tex and typing
`p in insert mode results in the problem just described.

Would you please consider looking into this problem ? Perhaps its a problem
only with me and some minor adjustments would make it work.

Please note that I am by no means a vim expert but a general user with
basic understanding of its commands and settings.

Thanks a lot in advance and please inform if any other information is
necessary, I would provide them as soon as I could.

Thank you,
Visakha Raja.

Re: [Vim-latex-devel] New investigations of spell checking and syntax/tex.vim: FOLDING the problem?

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

I have no problem with the spell checking, even if I use the
standard tex.syntax (which is versioned with 57):

gerw:~/head -n 6 /usr/share/vim/current/syntax/tex.vim
" Vim syntax file
" Language:     TeX
" Maintainer:   Dr. Charles E. Campbell, Jr. 
<NdrchipO@ScampbellPfamily.AbizM>
" Last Change:  Aug 12, 2010
" Version:      57
" URL: 
http://mysite.verizon.net/astronaut/vim/index.html#vimlinks_syntax

I also use the folding features of the suite.

What kind of problems do you have with the spell checking?

Best regards,
Gerd


On 08/22/2014 01:05 AM, Ted Pavlic wrote:
> 	I think it's been a long-standing problem that Vim's built-in spell
> checking breaks when Vim's standard syntax/tex.vim is used with the
> vim-latex suite.
>
> * If you stop using vim-latex, then syntax/tex.vim still properly
> highlights, but spell checking starts working again.
>
> * If you are using vim-latex and you set your filetype to something
> other than "tex", spell checking starts working again (but syntax
> highlighting stops working).
>
> I noticed today that if I try to turn on syntax/tex.vim's syntax-based
> folding in my .vimrc:
>
> let g:tex_fold_enabled=1
>
> then spell checking in vim-latex starts to work again (but folding is
> totally broken).
>
> 	Turning off Vim-LaTeX folding (setting g:Tex_Folding=0) doesn't fix the
> problem. The only thing that fixes the problem is setting
> g:tex_fold_enabled=1, but I'd rather use Vim-LaTeX's folding.
>
> 	Has anyone managed to solve the spell-checking problem for good in the
> latest versions of Vim? It seems to be a moving target...
>
> 	--Ted
>

[Vim-latex-devel] s:origdir overridden when using tex_RunLaTeX

[Kai H. <ka...@ho...>]

Hi!

I am using vim-latex on a project with a main file including several sections from files in a folder sections/.
If I call <leader>ll while editing sections/foo.tex, vim-latex will return from compilation correctly but also set cwd to sections/. This is unexpected behavior for me. I would not expect compilation to suddenly change the working directory.

I dug into the source code and came to the following conclusion:
s:origdir is used throughout the source code to save the cwd at the beginning of a function and later restore it. Unfortunately, s:origdir is a script-local variable. Therefore, reusing the method of "save cwd to s:origdir and restore" will not work if calls of functions using this method are nested. 

This is exactly the source of my unexpected change of cwd after compilation.
tex_RunLaTeX saves the correct cwd to s:origdir. It then changes the working directory. This is followed by calling tex_CompileLaTex() at some point, which will save the wrong cwd again to s:origdir and thus overrides the old, but correct cwd. By extension, the final restore of cwd at the end of tex_RunLaTeX will then restore the the incorrect directory, which in my case is the subdirectory sections/.

As a simple solution, I propose to substitute s:origdir with l:origdir or simply origdir as I see no compelling reason to make origdir a script-local variable. A simple "%s/s:origdir/l:origdir/g" on ftplugin/latex-suite/compiler.vim solved the original issue for me. It also appears to be used in main.vim, texproject.vim, and texviewer.vim. The same fix will probably apply there as well.

Is there any way I can contribute a pull-request or something alike?

Best,

Kai. (kaihowl)

Re: [Vim-latex-devel] change the IMAP

[Francesco M. <fra...@gm...>]

Hi Rudra,

I hope that the following helps you. In my .vim/ftplugin/tex.vim I've
redefined the default figure environment [1] added a new figure environment
[1] and mapped the new environment to EFS [3].

[1] let g:Tex_Env_figure =
 "\\begin{figure}\<cr>\\centering\<cr>\\includegraphics[width=80mm,
keepaspectratio]{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\\label{fig:
   <+label+>}\<cr>\\end{figure}<++>"

[2] let g:Tex_Env_figures =
 "\\begin{figure*}\<cr>\\centering\<cr>\\includegraphics[width=160mm,
keepaspectratio]{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\\label{fig
   :<+label+>}\<cr>\\end{figure*}<++>"

[3] call IMAP ('EFS', g:Tex_Env_figures, 'tex')

Cheers,

Fra


2014-09-04 14:32 GMT+02:00 Rudra Banerjee <bnr...@li...>:

> Hi,
> In vim-latex, there is two IMAP for figure:
> let s:figure =     "\\begin{figure}[<+htpb+>]\<cr>\\centering\<cr>\
> \psfig{figure=<+eps file+>}\<cr>\\caption{<+caption text+>}\<cr>\
> \label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
> s:end_with_cr . "<++>"
> let s:figure_graphicx =    "\\begin{figure}[<+htpb+>]\<cr>\\centering
> \<cr>\\includegraphics{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\
> \label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
> s:end_with_cr . "<++>"
>
> And, EFI always picks the s:figure, and I am unable to access
> s:figure_graphics.
> I have also tried to put the figure_graphics to my vimrc and rename it
> to figure, which is givine error:
> $ vi i.tex
> Error detected while processing ~/.vimrc:
> line  110:
> E121: Undefined variable: s:labelprefix_figure
> E15: Invalid expression: "\\begin{figure}[<+htpb+>]\<cr>\\centering
> \<cr>\\includegraphics{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\
> \label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
> s:end_with_cr . "<++>"
>
> I am just an enduser without much knowledge of twiking it.
> Is there any way I can use EFI for figure_graphicx?
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] change the IMAP

[Rudra B. <bnr...@li...>]

Hi, 
In vim-latex, there is two IMAP for figure:
let s:figure =     "\\begin{figure}[<+htpb+>]\<cr>\\centering\<cr>\
\psfig{figure=<+eps file+>}\<cr>\\caption{<+caption text+>}\<cr>\
\label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
s:end_with_cr . "<++>"
let s:figure_graphicx =    "\\begin{figure}[<+htpb+>]\<cr>\\centering
\<cr>\\includegraphics{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\
\label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
s:end_with_cr . "<++>"

And, EFI always picks the s:figure, and I am unable to access
s:figure_graphics. 
I have also tried to put the figure_graphics to my vimrc and rename it
to figure, which is givine error:
$ vi i.tex
Error detected while processing ~/.vimrc:
line  110:
E121: Undefined variable: s:labelprefix_figure
E15: Invalid expression: "\\begin{figure}[<+htpb+>]\<cr>\\centering
\<cr>\\includegraphics{<+file+>}\<cr>\\caption{<+caption text+>}\<cr>\
\label{" . s:labelprefix_figure . "<+label+>}\<cr>\\end{figure}" .
s:end_with_cr . "<++>"

I am just an enduser without much knowledge of twiking it.
Is there any way I can use EFI for figure_graphicx?

[Vim-latex-devel] New investigations of spell checking and syntax/tex.vim: FOLDING the problem?

[Ted P. <te...@te...>]

	I think it's been a long-standing problem that Vim's built-in spell
checking breaks when Vim's standard syntax/tex.vim is used with the
vim-latex suite.

* If you stop using vim-latex, then syntax/tex.vim still properly
highlights, but spell checking starts working again.

* If you are using vim-latex and you set your filetype to something
other than "tex", spell checking starts working again (but syntax
highlighting stops working).

I noticed today that if I try to turn on syntax/tex.vim's syntax-based
folding in my .vimrc:

let g:tex_fold_enabled=1

then spell checking in vim-latex starts to work again (but folding is
totally broken).

	Turning off Vim-LaTeX folding (setting g:Tex_Folding=0) doesn't fix the
problem. The only thing that fixes the problem is setting
g:tex_fold_enabled=1, but I'd rather use Vim-LaTeX's folding.

	Has anyone managed to solve the spell-checking problem for good in the
latest versions of Vim? It seems to be a moving target...

	--Ted

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Help: painfully slow loading up (and using 100% CPU for mins)

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

Hi,

this may come from the folding of your file. Try to disable folding

http://stackoverflow.com/questions/3322453/how-can-i-disable-code-folding-in-vim-with-vim-latex

and try again. If this helps, the folding is the bad guy.

Another possibility is to disable the menus. Add

" no Tex-Menus
let g:Tex_Menus = 0
" Do not scan for packages. This is slow and we don't need it.
let g:Tex_PackagesMenu = 0

to .vim/ftplugins/tex.vim


Best Regards,
Gerd



On 08/01/2014 02:19 AM, Nom Plume wrote:
>   Hi,
>
> I have been using Vim-LateX for years, and it has been EXTREMELY helpful.
>
> However, I recently noticed that it is taking a VERY LONG time (minutes!!)
> to load up files that are long (well, still negligible time when using
> emacs or vim -u NONE filename.tex).Note the huge jump in time after
> sourcing main.vim below. After loading, it works fine.
>
> Below is the output when I run:
>
> $gvim --startuptime startup.log filename.tex
>
> I have tried the latest version (and other tips I have seen on web:
>
> autocmd FileType tex :NoMatchParen
> au FileType tex setlocal nocursorline
>
>
> I am using Vim 7.4 on Linux (Ubuntu).
>
> Since this is such a PHENOMENAL tool, I would appreciate if this is
> resolved.
>
> *************
>
> times in msec
>   clock   self+sourced   self:  sourced script
>   clock   elapsed:              other lines
>
> 000.005  000.005: --- VIM STARTING ---
> 000.090  000.085: Allocated generic buffers
> 000.136  000.046: locale set
> 000.153  000.017: GUI prepared
> 000.155  000.002: clipboard setup
> 000.162  000.007: window checked
> 000.568  000.406: inits 1
> 000.616  000.048: parsing arguments
> 000.621  000.005: expanding arguments
> 000.644  000.023: shell init
> 000.848  000.204: Termcap init
> 000.885  000.037: inits 2
> 000.986  000.101: init highlight
> 001.315  000.220  000.220: sourcing /usr/share/vim/vim74/debian.vim
> 001.670  000.182  000.182: sourcing /usr/share/vim/vim74/syntax/syncolor.vim
> 001.785  000.353  000.171: sourcing /usr/share/vim/vim74/syntax/synload.vim
> 019.766  000.041  000.041: sourcing /usr/share/vim/vim74/autoload/paste.vim
> 029.466  010.662  010.621: sourcing /usr/share/vim/vim74/menu.vim
> 029.498  027.660  016.998: sourcing /usr/share/vim/vim74/filetype.vim
> 029.543  028.173  000.160: sourcing /usr/share/vim/vim74/syntax/syntax.vim
> 029.571  028.541  000.148: sourcing $VIM/vimrc
> 029.668  000.010  000.010: sourcing /usr/share/vim/vim74/filetype.vim
> 029.760  000.038  000.038: sourcing /usr/share/vim/vim74/ftplugin.vim
> 029.833  000.009  000.009: sourcing /usr/share/vim/vim74/filetype.vim
> 029.919  000.033  000.033: sourcing /usr/share/vim/vim74/indent.vim
> 029.979  000.368  000.278: sourcing $HOME/.vimrc
> 029.988  000.093: sourcing vimrc file(s)
> 030.279  000.108  000.108: sourcing /home/guest/.vim/plugin/SpellChecker.vim
> 030.485  000.174  000.174: sourcing /home/guest/.vim/plugin/SyntaxFolds.vim
> 030.686  000.169  000.169: sourcing /home/guest/.vim/plugin/filebrowser.vim
> 031.331  000.616  000.616: sourcing /home/guest/.vim/plugin/imaps.vim
> 031.481  000.112  000.112: sourcing /home/guest/.vim/plugin/libList.vim
> 032.227  000.712  000.712: sourcing /home/guest/.vim/plugin/prtdialog.vim
> 032.372  000.101  000.101: sourcing /home/guest/.vim/plugin/remoteOpen.vim
> 032.664  000.074  000.074: sourcing
> /usr/share/vim/vim74/plugin/getscriptPlugin.vim
> 032.918  000.226  000.226: sourcing /usr/share/vim/vim74/plugin/gzip.vim
> 033.126  000.177  000.177: sourcing
> /usr/share/vim/vim74/plugin/matchparen.vim
> 033.619  000.462  000.462: sourcing
> /usr/share/vim/vim74/plugin/netrwPlugin.vim
> 033.701  000.039  000.039: sourcing /usr/share/vim/vim74/plugin/rrhelper.vim
> 033.767  000.032  000.032: sourcing
> /usr/share/vim/vim74/plugin/spellfile.vim
> 033.968  000.166  000.166: sourcing
> /usr/share/vim/vim74/plugin/tarPlugin.vim
> 034.105  000.093  000.093: sourcing /usr/share/vim/vim74/plugin/tohtml.vim
> 034.296  000.158  000.158: sourcing
> /usr/share/vim/vim74/plugin/vimballPlugin.vim
> 034.527  000.189  000.189: sourcing
> /usr/share/vim/vim74/plugin/zipPlugin.vim
> 034.567  000.971: loading plugins
> 034.574  000.007: inits 3
> 055.378  000.960  000.960: sourcing $VIMRUNTIME/menu.vim
> 055.479  000.049  000.049: sourcing $VIM/gvimrc
> 383.730  348.147: starting GUI
> 386.554  002.824: reading viminfo
> 389.155  002.601: GUI delay
> 389.818  000.663: register server name
> 389.824  000.006: setting raw mode
> 389.828  000.004: start termcap
> 389.995  000.167: clearing screen
> 428.651  020.103  020.103: sourcing /usr/share/vim/vim74/syntax/tex.vim
> 428.830  000.009  000.009: sourcing /home/guest/.vim/ftplugin/tex.vim
> 431.490  002.377  002.377: sourcing
> /home/guest/.vim/ftplugin/latex-suite/texrc
> 463.293  002.243  002.243: sourcing
> /home/guest/.vim/ftplugin/latex-suite/texproject.vim
> 465.092  001.737  001.737: sourcing
> /home/guest/.vim/ftplugin/latex-suite/texmenuconf.vim
> 466.298  000.457  000.457: sourcing
> /home/guest/.vim/ftplugin/latex-suite/wizardfuncs.vim
> 486.512  021.350  020.893: sourcing
> /home/guest/.vim/ftplugin/latex-suite/envmacros.vim
> 503.492  016.906  016.906: sourcing
> /home/guest/.vim/ftplugin/latex-suite/elementmacros.vim
> 547.870  044.291  044.291: sourcing
> /home/guest/.vim/ftplugin/latex-suite/mathmacros.vim
> 558.936  010.926  010.926: sourcing
> /home/guest/.vim/ftplugin/latex-suite/multicompile.vim
> 559.445  000.414  000.414: sourcing
> /home/guest/.vim/ftplugin/latex-suite/compiler.vim
> 559.750  000.200  000.200: sourcing
> /home/guest/.vim/ftplugin/latex-suite/folding.vim
> 564.329  004.518  004.518: sourcing
> /home/guest/.vim/ftplugin/latex-suite/templates.vim
> 565.441  001.042  001.042: sourcing
> /home/guest/.vim/ftplugin/latex-suite/custommacros.vim
> 566.137  000.605  000.605: sourcing
> /home/guest/.vim/ftplugin/latex-suite/bibtex.vim
> 581.961  015.724  015.724: sourcing
> /home/guest/.vim/ftplugin/latex-suite/packages.vim
> 581.000  153.002  030.669: sourcing
> /home/guest/.vim/ftplugin/latex-suite/main.vim
> 271433.582  001.437  001.437: sourcing /home/guest/.vim/compiler/tex.vim
> 272024.611  000.081  000.081: sourcing
> /home/guest/.vim/ftplugin/latex-suite/packages/amsmath
> 272043.759  000.070  000.070: sourcing
> /home/guest/.vim/ftplugin/latex-suite/packages/cite
> 272047.613  000.046  000.046: sourcing
> /home/guest/.vim/ftplugin/latex-suite/packages/graphicx
> 272059.663  000.060  000.060: sourcing
> /home/guest/.vim/ftplugin/latex-suite/packages/url
> 272064.032  271636.092  271481.396: sourcing
> /home/guest/.vim/ftplugin/tex_latexSuite.vim
> 272064.351  000.213  000.213: sourcing
> /home/guest/.vim/ftplugin/tex/brackets.vim
> 272064.412  000.016  000.016: sourcing
> /home/guest/.vim/ftplugin/tex/smartspace.vim
> 272064.893  000.442  000.442: sourcing
> /home/guest/.vim/ftplugin/tex/texviewer.vim
> 272065.157  000.073  000.073: sourcing
> /usr/share/vim/vim74/ftplugin/initex.vim
> 272065.206  000.168  000.095: sourcing
> /usr/share/vim/vim74/ftplugin/plaintex.vim
> 272065.258  000.273  000.105: sourcing /usr/share/vim/vim74/ftplugin/tex.vim
> 272065.610  000.092  000.092: sourcing /home/guest/.vim/indent/tex.vim
> 272065.717  000.052  000.052: sourcing /usr/share/vim/vim74/indent/tex.vim
> 272065.911  019.624: opening buffers
> 272065.939  000.028: BufEnter autocommands
> 272065.941  000.002: editing files in windows
> 272067.381  001.440: VimEnter autocommands
> 272067.383  000.002: before starting main loop
> 272080.590  013.207: first screen update
> 272080.594  000.004: --- VIM STARTED ---
>
>
> ***********
>
> FYI, my simple .vimrc:
>
> ******************
> " REQUIRED. This makes vim invoke latex-suite when you open a tex file.
> filetype plugin on
>
> " IMPORTANT: win32 users will need to have 'shellslash' set so that latex
> " can be called correctly.
> set shellslash
>
> " IMPORTANT: grep will sometimes skip displaying the file name if you
> " search in a singe file. This will confuse latex-suite. Set your grep
> " program to alway generate a file-name.
> set grepprg=grep\ -nH\ $*
>
> " OPTIONAL: This enables automatic indentation as you type.
> filetype indent on
>
> " this is mostly a matter of taste. but LaTeX looks good with just a bit
> " of indentation.
> set sw=2
> " TIP: if you write your \label's as \label{fig:something}, then if you
> " type in \ref{fig: and press <C-n> you will automatically cycle through
> " all the figure labels. Very useful!
> set iskeyword+=:
>
>
> **************
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
>
>
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] Help: painfully slow loading up (and using 100% CPU for mins)

[Nom P. <nom...@gm...>]

 Hi,

I have been using Vim-LateX for years, and it has been EXTREMELY helpful.

However, I recently noticed that it is taking a VERY LONG time (minutes!!)
to load up files that are long (well, still negligible time when using
emacs or vim -u NONE filename.tex).Note the huge jump in time after
sourcing main.vim below. After loading, it works fine.

Below is the output when I run:

$gvim --startuptime startup.log filename.tex

I have tried the latest version (and other tips I have seen on web:

autocmd FileType tex :NoMatchParen
au FileType tex setlocal nocursorline


I am using Vim 7.4 on Linux (Ubuntu).

Since this is such a PHENOMENAL tool, I would appreciate if this is
resolved.

*************

times in msec
 clock   self+sourced   self:  sourced script
 clock   elapsed:              other lines

000.005  000.005: --- VIM STARTING ---
000.090  000.085: Allocated generic buffers
000.136  000.046: locale set
000.153  000.017: GUI prepared
000.155  000.002: clipboard setup
000.162  000.007: window checked
000.568  000.406: inits 1
000.616  000.048: parsing arguments
000.621  000.005: expanding arguments
000.644  000.023: shell init
000.848  000.204: Termcap init
000.885  000.037: inits 2
000.986  000.101: init highlight
001.315  000.220  000.220: sourcing /usr/share/vim/vim74/debian.vim
001.670  000.182  000.182: sourcing /usr/share/vim/vim74/syntax/syncolor.vim
001.785  000.353  000.171: sourcing /usr/share/vim/vim74/syntax/synload.vim
019.766  000.041  000.041: sourcing /usr/share/vim/vim74/autoload/paste.vim
029.466  010.662  010.621: sourcing /usr/share/vim/vim74/menu.vim
029.498  027.660  016.998: sourcing /usr/share/vim/vim74/filetype.vim
029.543  028.173  000.160: sourcing /usr/share/vim/vim74/syntax/syntax.vim
029.571  028.541  000.148: sourcing $VIM/vimrc
029.668  000.010  000.010: sourcing /usr/share/vim/vim74/filetype.vim
029.760  000.038  000.038: sourcing /usr/share/vim/vim74/ftplugin.vim
029.833  000.009  000.009: sourcing /usr/share/vim/vim74/filetype.vim
029.919  000.033  000.033: sourcing /usr/share/vim/vim74/indent.vim
029.979  000.368  000.278: sourcing $HOME/.vimrc
029.988  000.093: sourcing vimrc file(s)
030.279  000.108  000.108: sourcing /home/guest/.vim/plugin/SpellChecker.vim
030.485  000.174  000.174: sourcing /home/guest/.vim/plugin/SyntaxFolds.vim
030.686  000.169  000.169: sourcing /home/guest/.vim/plugin/filebrowser.vim
031.331  000.616  000.616: sourcing /home/guest/.vim/plugin/imaps.vim
031.481  000.112  000.112: sourcing /home/guest/.vim/plugin/libList.vim
032.227  000.712  000.712: sourcing /home/guest/.vim/plugin/prtdialog.vim
032.372  000.101  000.101: sourcing /home/guest/.vim/plugin/remoteOpen.vim
032.664  000.074  000.074: sourcing
/usr/share/vim/vim74/plugin/getscriptPlugin.vim
032.918  000.226  000.226: sourcing /usr/share/vim/vim74/plugin/gzip.vim
033.126  000.177  000.177: sourcing
/usr/share/vim/vim74/plugin/matchparen.vim
033.619  000.462  000.462: sourcing
/usr/share/vim/vim74/plugin/netrwPlugin.vim
033.701  000.039  000.039: sourcing /usr/share/vim/vim74/plugin/rrhelper.vim
033.767  000.032  000.032: sourcing
/usr/share/vim/vim74/plugin/spellfile.vim
033.968  000.166  000.166: sourcing
/usr/share/vim/vim74/plugin/tarPlugin.vim
034.105  000.093  000.093: sourcing /usr/share/vim/vim74/plugin/tohtml.vim
034.296  000.158  000.158: sourcing
/usr/share/vim/vim74/plugin/vimballPlugin.vim
034.527  000.189  000.189: sourcing
/usr/share/vim/vim74/plugin/zipPlugin.vim
034.567  000.971: loading plugins
034.574  000.007: inits 3
055.378  000.960  000.960: sourcing $VIMRUNTIME/menu.vim
055.479  000.049  000.049: sourcing $VIM/gvimrc
383.730  348.147: starting GUI
386.554  002.824: reading viminfo
389.155  002.601: GUI delay
389.818  000.663: register server name
389.824  000.006: setting raw mode
389.828  000.004: start termcap
389.995  000.167: clearing screen
428.651  020.103  020.103: sourcing /usr/share/vim/vim74/syntax/tex.vim
428.830  000.009  000.009: sourcing /home/guest/.vim/ftplugin/tex.vim
431.490  002.377  002.377: sourcing
/home/guest/.vim/ftplugin/latex-suite/texrc
463.293  002.243  002.243: sourcing
/home/guest/.vim/ftplugin/latex-suite/texproject.vim
465.092  001.737  001.737: sourcing
/home/guest/.vim/ftplugin/latex-suite/texmenuconf.vim
466.298  000.457  000.457: sourcing
/home/guest/.vim/ftplugin/latex-suite/wizardfuncs.vim
486.512  021.350  020.893: sourcing
/home/guest/.vim/ftplugin/latex-suite/envmacros.vim
503.492  016.906  016.906: sourcing
/home/guest/.vim/ftplugin/latex-suite/elementmacros.vim
547.870  044.291  044.291: sourcing
/home/guest/.vim/ftplugin/latex-suite/mathmacros.vim
558.936  010.926  010.926: sourcing
/home/guest/.vim/ftplugin/latex-suite/multicompile.vim
559.445  000.414  000.414: sourcing
/home/guest/.vim/ftplugin/latex-suite/compiler.vim
559.750  000.200  000.200: sourcing
/home/guest/.vim/ftplugin/latex-suite/folding.vim
564.329  004.518  004.518: sourcing
/home/guest/.vim/ftplugin/latex-suite/templates.vim
565.441  001.042  001.042: sourcing
/home/guest/.vim/ftplugin/latex-suite/custommacros.vim
566.137  000.605  000.605: sourcing
/home/guest/.vim/ftplugin/latex-suite/bibtex.vim
581.961  015.724  015.724: sourcing
/home/guest/.vim/ftplugin/latex-suite/packages.vim
581.000  153.002  030.669: sourcing
/home/guest/.vim/ftplugin/latex-suite/main.vim
271433.582  001.437  001.437: sourcing /home/guest/.vim/compiler/tex.vim
272024.611  000.081  000.081: sourcing
/home/guest/.vim/ftplugin/latex-suite/packages/amsmath
272043.759  000.070  000.070: sourcing
/home/guest/.vim/ftplugin/latex-suite/packages/cite
272047.613  000.046  000.046: sourcing
/home/guest/.vim/ftplugin/latex-suite/packages/graphicx
272059.663  000.060  000.060: sourcing
/home/guest/.vim/ftplugin/latex-suite/packages/url
272064.032  271636.092  271481.396: sourcing
/home/guest/.vim/ftplugin/tex_latexSuite.vim
272064.351  000.213  000.213: sourcing
/home/guest/.vim/ftplugin/tex/brackets.vim
272064.412  000.016  000.016: sourcing
/home/guest/.vim/ftplugin/tex/smartspace.vim
272064.893  000.442  000.442: sourcing
/home/guest/.vim/ftplugin/tex/texviewer.vim
272065.157  000.073  000.073: sourcing
/usr/share/vim/vim74/ftplugin/initex.vim
272065.206  000.168  000.095: sourcing
/usr/share/vim/vim74/ftplugin/plaintex.vim
272065.258  000.273  000.105: sourcing /usr/share/vim/vim74/ftplugin/tex.vim
272065.610  000.092  000.092: sourcing /home/guest/.vim/indent/tex.vim
272065.717  000.052  000.052: sourcing /usr/share/vim/vim74/indent/tex.vim
272065.911  019.624: opening buffers
272065.939  000.028: BufEnter autocommands
272065.941  000.002: editing files in windows
272067.381  001.440: VimEnter autocommands
272067.383  000.002: before starting main loop
272080.590  013.207: first screen update
272080.594  000.004: --- VIM STARTED ---


***********

FYI, my simple .vimrc:

******************
" REQUIRED. This makes vim invoke latex-suite when you open a tex file.
filetype plugin on

" IMPORTANT: win32 users will need to have 'shellslash' set so that latex
" can be called correctly.
set shellslash

" IMPORTANT: grep will sometimes skip displaying the file name if you
" search in a singe file. This will confuse latex-suite. Set your grep
" program to alway generate a file-name.
set grepprg=grep\ -nH\ $*

" OPTIONAL: This enables automatic indentation as you type.
filetype indent on

" this is mostly a matter of taste. but LaTeX looks good with just a bit
" of indentation.
set sw=2
" TIP: if you write your \label's as \label{fig:something}, then if you
" type in \ref{fig: and press <C-n> you will automatically cycle through
" all the figure labels. Very useful!
set iskeyword+=:


**************

Re: [Vim-latex-devel] Using vim-latex suite for docs written in markdown, rest, sphinx, etc.

[Mike R. <ri...@um...>]

On Fri, Jul 25, 2014 at 5:37 AM, ozhan fenerci <o_f...@ya...> wrote:
> Dear Friends,
>
> I am using vim-latex suite for my writing in Latex. I would like to use it for not only tex docs but also other formats such as Sphinx. My questions:
>
> 1) How to load vim-latex suite for files written in Sphinx (say that, my file has extension like " myfile.rst")
>
> 2) I would like to use IMAP() and placeholder  functionality of vim-latex (and its place holder functionality)  for some shortcuts for such as " :math:`x^2` " in Sphinx, which is equivalent $x^2$ in Latex. For example, whenever I write 'MM' in file, I want it  to refer a shortcut to ":math:` placeholder`"
>
>
> In general, it would be great to extend vim-latex functionality to docs written in other formats.
>
>
> Best Regards,
> Ozhan


Hi Ozhan,

It sounds like you don't necessarily want to load all of it.  I made a
simple plugin with IMAPs for C/C++ and HTML code.  The gist of it is listed
below.  These are ripped from my ~/.vim/ftplugin/c.vim.

Hope this helps.  I may upload my plugins to github or something, but I'll
have to be careful about license stuff first.

Cheers,
Mike

    " get access to IMAP()
    runtime plugin/imaps.vim

    " SafeLet comes from latex-suite (vim-latex)
    " SafeLet: checks for value before giving default value {{{
    " Description: The function takes in a single argument and splits it into 2
    "              parts, the first being the first <CWORD> found. this is taken
    "              as a variable name and the next part is assigned to it
    "              depending on whether the variable already exists or not.
    "              handles the case where the next part is quoted or not.
    "              All these calls work:
    "                   CLet g:varname = 1
    "                   CLet g:varname = '1'
    "                   CLet g:varname = 'foo bar'
    "                   CLet g:varname = "foo\nbar"
    "                   CLet g:varname = foo bar
    function! <SID>SafeLet(arg)
        let name = matchstr(a:arg, '^\s*\zs\(\S\+\)\ze\s*=')
        let value = matchstr(a:arg, '=\s*\zs.*\ze')
        let value = substitute(value, '\s*$', '', '')
        if !exists(name)
            if value =~ "^'\\|^\""
                    exec "let ".name." = ".value
            else
                    exe "let ".name." = value"
            endif
        endif
    endfunction
    com! -nargs=+ CLet :call <SID>SafeLet(<q-args>)

    CLet g:C_leader = '`'
    " We need funny placeholders so code indentation works right.
    CLet b:Imap_PlaceHolderStart = ";<"
    CLet b:Imap_PlaceHolderEnd = ">;"

    " real plugin has more of these
    CLet g:C_idiom_if = "if (<++>) {\<cr><++>\<cr>}<++>"

    " make the IMAPs
    function! s:IMAPs (ft)
        call IMAP ('if(', g:C_idiom_if, a:ft)
        call IMAP ('if()', g:C_idiom_if, a:ft)
        " etc.
    endfunction

    " make the IMAPs for both C and C++ filetypes
    if !exists ('s:sourced_imaps')
        let s:sourced_imaps=1
        call s:IMAPs ('c')
        call s:IMAPs ('cpp')
    endif

[Vim-latex-devel] Using vim-latex suite for docs written in markdown, rest, sphinx, etc.

[ozhan f. <o_f...@ya...>]

Dear Friends,

I am using vim-latex suite for my writing in Latex. I would like to use it for not only tex docs but also other formats such as Sphinx. My questions:

1) How to load vim-latex suite for files written in Sphinx (say that, my file has extension like " myfile.rst") 

2) I would like to use IMAP() and placeholder  functionality of vim-latex (and its place holder functionality)  for some shortcuts for such as " :math:`x^2` " in Sphinx, which is equivalent $x^2$ in Latex. For example, whenever I write 'MM' in file, I want it  to refer a shortcut to ":math:` placeholder`" 


In general, it would be great to extend vim-latex functionality to docs written in other formats. 


Best Regards,
Ozhan 

[Vim-latex-devel] Dollar symbol breaks colorscheme

[William G. <wi...@ga...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi guys.

Don't know if this report has already been posted or if this is
related to vim-latex or to my colorscheme[1]. Otherwise, sorry for that.

I'm experiencing an issue each time I'm trying to print a dollar
symbol: the colorscheme becomes broken just after.

Since I'm an IT student, dollars are quite common in the LaTeX
documents I write. This is rather annoying.

I tried a workaround with the "literate" statement, by using <dollar>
each time I want to use the dollar symbol

{<dollar>}{\$}1

but it doesn't work.

Could you please fix this problem?


Regards,


[1] AFAIK, it should be related to the syntax highlighting you wrote.
But I'm unsure. -->
http://learnvimscriptthehardway.stevelosh.com/chapters/45.html


- -- 
William Gathoye
<wi...@ga...>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJTxu+xAAoJEA595SwE1xaDaYYQANXjoqa3W8mW/teVjDlj2RpW
9Uv4jk+U2R6C52LrGZIjEmgs1bXyab8hjWqtnp8THmNXOH9cNvw6hTnqhUtGFbVf
5qbIjrhJvqNGhRaFJFKFTCre0n6v0ena8y18mxmw4IYZWjgZVvaD6wS62l1I9Tjd
ZsF2VEjb0w0fd737CbDJ1hGu7rkmyQdet5U3JfcIFyMSjZDlrLwViKZBxAkhF/8C
GzQoDN28y1WlYmc9GSUIwulgTbBQDbVe1kDXhdgvMsXNOuM4wBmW7gzGPk6kyeuo
HDcKFQjeRoJ3IrYc3T3N5vL1Znm7aAiLdf/YEm6ydETIbM8W++1FG73nquuz2cn1
nhH0QB3EgLzNw9k4f7BYH2IlF2RJ8LiJCaK2/eDobdDes00xmIBhpoip4RTWwF4x
sck7jMUe7kTRbjM/arPHiYn0k+AajY8RlrR/CfJqDc65y9ZsEVWHo0Wa7aDLkceg
1K5PuLQhTAtRApbwdOYwIdBNEVXLkTcXJ55dKPopwQ/wFTlW167mp0QSustdDymY
QDOmtZvYhSTYUX51lxLpIBcXLCvhovdUDPJtUC60WhOFyeeaugboz6UUlfSTFRoe
zyS/TAjb3TMi6eAUpFOrxs8o4cTblhnPcNL0JQHage0jFKMHF/lxT29COGn3hrjf
oh+/goL8hyMFRlIkFTm8
=WfIz
-----END PGP SIGNATURE-----

[Vim-latex-devel] filename completion source

[Rudra B. <bnr...@li...>]

Hi,
I am a long user of Latex-Suite.
One feature that I want to use in other ft is  filename completion
(http://vim-latex.sourceforge.net/documentation/latex-suite/ls-filename-completion.html)
which is far better the C_x_C_f. But, after a simple look inside the
code, I am not sure which plugin actually do that(may be
plugin/filebrowser.vim?)?
Can anyone kindly help me export this feature to other ft? (I am
specially interested in fortran)
Regards,
Rudra

[Vim-latex-devel] Trouble with changing environments

[Adam E. N. T. <ad...@ad...>]

Dear Vim-Latex mailing list,

I am having trouble with the change environment feature.  It either adds 
an extra backslash or removes the backslash in front of begin and end.

It happens for example when I try to change between equation* and align* 
in the attached example. That is when I press Shift-F5 in the align* 
environment and write equation* it removes the backslashes in front of 
begin and end.  And vice versa in the other environment.

I am using Arch Linux and the official vim-latexsuite package, which has 
version number 20130126-1.

Sincerely,
Adam Ehlers Nyholm Thomsen

Re: [Vim-latex-devel] Trouble with changing environments

[Adam E. N. T. <ad...@ad...>]

I am very sorry that I forgot to attach the test case.

Re: [Vim-latex-devel] possible bug in block expansion?

[Mike R. <ri...@um...>]

Hi Walter,

This is possible: see

    :help remapping-latex-suite-keys

I would personally recommend a choice other than <C-n>, however; <C-n> and
<C-p> can be very useful at times -- in particular, in LaTeX, for filling in
\ref's and \cite's.

Cheers,
Mike


On Fri, May 30, 2014 at 11:00 AM, Walter Rabus <wal...@we...> wrote:
> Am 27.05.2014 04:44, schrieb Mike Richman:
>> I'd say this is a feature, not a bug.  The idea is that you use <C-j>
>> (control-J) to cycle through <++> markers.  You write in the equation, press
>> <C-j> and fill in the label, and press <C-j> again to get outside the
>> equation environment where you can then press <enter> and continue writing
>> the prose of the document.
>
> Ok, seeing it that way, it makes sense. I think I'd like to keep the the
> behavior for now and test if it can be incorporated into my workflow.
>
> I would, however, like to change the keybinding to Ctrl+n instead of
> Ctrl+j, is that possible to easily overwrite as well?
>
> Thanks,
> Walter
>

[Vim-latex-devel] Problem with "iskeyword"

[Renliang Gu <gur...@gm...>]

Hi,

Just noticed that the setting
set iskeyword+=:
as recommended in the installation page
<http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html>
and the help document is not working. As mentioned by Gary in link
<https://www.mail-archive.com/vim...@li.../msg01077.html>,
iskeyword is reset by $VIMRUNTIME/syntax/tex.vim

My vim is 7.3 under linux.

As said in $VIMRUNTIME/syntax/tex.vim,
" (La)TeX keywords: uses the characters 0-9,a-z,A-Z,192-255 only... {{{1
" but _ is the only one that causes problems.
" One may override this iskeyword setting by providing
" g:tex_isk
if exists("g:tex_isk")
 exe "setlocal isk=".g:tex_isk
else
 setlocal isk=48-57,a-z,A-Z,192-255
endif

Why not change the instruction and the document to add this so called
variable g:tex_isk, like
let g:tex_isk = '48-57,a-z,A-Z,192-255,:'
to reduce confusion?

顾任亮(Renliang Gu)

Re: [Vim-latex-devel] possible bug in block expansion?

[Walter R. <wal...@we...>]

Am 27.05.2014 04:44, schrieb Mike Richman:
> I'd say this is a feature, not a bug.  The idea is that you use <C-j>
> (control-J) to cycle through <++> markers.  You write in the equation, press
> <C-j> and fill in the label, and press <C-j> again to get outside the
> equation environment where you can then press <enter> and continue writing
> the prose of the document.

Ok, seeing it that way, it makes sense. I think I'd like to keep the the
behavior for now and test if it can be incorporated into my workflow.

I would, however, like to change the keybinding to Ctrl+n instead of
Ctrl+j, is that possible to easily overwrite as well?

Thanks,
Walter

Re: [Vim-latex-devel] possible bug in block expansion?

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

I am not a developer, but it seems this is a feature.  If you press  
Shift+J, you can skip to the next <++> and type the rest of your document.

On Mon, 26 May 2014 20:03:45 -0500, Walter Rabus <wal...@we...>  
wrote:

> Hi,
>
> I noticed a weird behavior when expanding a line with the vim-latexsuite
> and F5. Take the following code-snipped, pressing F5 in the line with
> the upper "equation" the line gets expanded to the lower construct:
>
> \documentclass[12pt,a4paper,oneside]{article}
> \usepackage{amssymb,amsmath}
> \begin{document}
>
> equation
>
> \begin{equation}
> 	foo
> 	\label{<++>}
> \end{equation}<++>
>
> \end{document}
>
> The problem I see with this is the <++> after "end{equation}" leads to
> "¡++¿" in the final document when compiled. As I think this is not
> intended to be there, I'd like to ask whether this is a bug or intended
> behavior for some reason and whether someone can reproduce it.
>
> I tested it with the git-version of vim-latexsuite as well.
>
> If it can be confirmed to be a reproducable bug, I would like to propose
> to remove the trailing "<++>" as I see no purpose it serves.
>
>
> Walter
>
> ------------------------------------------------------------------------------
> The best possible search technologies are now affordable for all  
> companies.
> Download your FREE open source Enterprise Search Engine today!
> Our experts will assist you in its installation for $59/mo, no  
> commitment.
> Test it for FREE on our Cloud platform anytime!
> http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel