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

[Vim-latex-devel] Cursor position after \ll changed

[Thomas K. <thk...@gm...>]

Hi,

when I compile a latex file in my project (i.e. I have a different
latex root file than the latex file I am currently in) the cursor
position is always changed. It jumps to one specific line no matter
what line I was in before I started compiling.
The line has nothing to do with any of the warnings I receive after
the compilation. Anyone ever experienced this behavior?

Thanks in advance,
Thomas

[Vim-latex-devel] Double definition?

[Alberto A. <ygr...@gm...>]

Hi guys,
I came across something tonight. If I wrote `w I didn't get \omega, but  
\wedge. I found in main.vim these two lines:

{{{
call IMAP(g:Tex_Leader.'w', '\omega', 'tex')
call IMAP(g:Tex_Leader.'w', '\wedge', 'tex')  " AUCTEX style
}}}

I commented the second and `w is giving \omega now. Is it a double  
definition or I am missing something?

Al.

[Vim-latex-devel] Issue about indentation

[Alberto A. <ygr...@gm...>]

Hey there,
I have yet another question, but as it's about a different part of the  
latexsuite I thought it would be better to 'file' a different question. I  
have added a couple of templates, and they include a few lines in the  
preamble to customise backreferences. Everything works fine, save for  
indentation, that gets screwed after these lines when I use the templates:

{{{
\renewcommand*{\backrefalt}[4]{%
    \ifcase #1 %
          { {\scriptsize Not cited in the text.}}%
      \or
          { {\scriptsize Back to page} #2}%
      \else
          { {\scriptsize Back to page} #2}%
    \fi
}
}}}

Vim indents the \ifcase command, which is reasonable, and adds an  
additional indentation for the \or, which is also reasonable. But then it  
adds also additional indentations for \else and \fi, and they don't  
disappear after closing the braces, so all the indentation is wrong. Is  
this something related to how I write those lines, or is it about  
indentation in the suite?

Thanks,

Al.

[Vim-latex-devel] Template names in the menus

[Alberto A. <ygr...@gm...>]

Hey guys,
I'm new to the vim latex suite, and rather young to vim itself, so excuse  
me if I ask something very straightforward. I am using vim 7.3.19 under  
Mac OS X Leopard. I have enabled the visual menus for the terminal version  
of vim, and I can navigate through them without problem. However, the  
names of the templates are not displayed; you can only see numbers,  
corresponding to the templates in alphabetical order. I read in  
templates.vim that there's a function to obtain the template names, but it  
seems it's not working. Is this a bug, or I just have to call some  
function or activate something?

Thanks!

Al.

[Vim-latex-devel] vimlatex and eclim

[Mario S. <ma...@ma...>]

I found a problem with vimlatex when eclim is installed.

The problem is similar to this:
http://permalink.gmane.org/gmane.comp.editors.vim.latex.devel/187

It is not possible to compile latex file on multiple file projects like 
explain in documentation here:
http://vim-latex.sourceforge.net/documentation/latex-suite/latex-
project.html

Erase .vim/eclim resolve this problem...but eclim is removed.
Test on elim 1.6.0 and eclipse 3.6.0

Are there any other solution? I will update eclim...maybe there is not 
trouble in new version...

I post this issue on eclim mailing list.

P.S.
Is there any updates on vim-latex patches?
http://sourceforge.net/tracker/?group_id=52322&atid=466458

Thank you
-- 
Mario Santagiuliana
www.marionline.it

Re: [Vim-latex-devel] Redirect latex output to background (or split window)

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

Hmm... actually, I think you may be stuck waiting for LaTeX to run
either way.  But if you use "gvim", the output is only shown if errors
are detected, so you can at least get ready to return to editing as
soon as compilation completes.

Next time I'll test before I e-mail, sorry!

-Mike Richman


On Mon, Oct 25, 2010 at 8:29 AM, Mike Richman <ri...@um...> wrote:
> Hi Robin,
>
> Are you using "vim" or "gvim"?  If I recall correctly, compiler output
> gets dumped all over your terminal when you're using "vim" in a
> terminal.  If you use "gvim", the self-contained windowed version,
> then the compiler is run in the background and its output is only
> shown if errors are detected.
>
> Hope this helps!
>
> -Mike Richman
>
>
> On Tue, Oct 19, 2010 at 8:06 PM, Robin Deits <rob...@gm...> wrote:
>> Hello all,
>> I have recently been playing around with vim-latex, and I'm really starting
>> to love it. So first, I should just thank all of you for your amazing work.
>> I have, however, run into an issue, which is that it is consistently
>> annoying that the latex output fills my entire vim window when I am
>> compiling, which preventing me from editing the .tex file until it is done.
>> It would be nice to have the output of the compiler directed to a temporary
>> split window (or even silenced entirely) so that I can keep working while my
>> file is compiling. Is there a way to do this?
>> Best,
>> Robin Deits
>>
>>
>

Re: [Vim-latex-devel] Redirect latex output to background (or split window)

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

Hi Robin,

Are you using "vim" or "gvim"?  If I recall correctly, compiler output
gets dumped all over your terminal when you're using "vim" in a
terminal.  If you use "gvim", the self-contained windowed version,
then the compiler is run in the background and its output is only
shown if errors are detected.

Hope this helps!

-Mike Richman


On Tue, Oct 19, 2010 at 8:06 PM, Robin Deits <rob...@gm...> wrote:
> Hello all,
> I have recently been playing around with vim-latex, and I'm really starting
> to love it. So first, I should just thank all of you for your amazing work.
> I have, however, run into an issue, which is that it is consistently
> annoying that the latex output fills my entire vim window when I am
> compiling, which preventing me from editing the .tex file until it is done.
> It would be nice to have the output of the compiler directed to a temporary
> split window (or even silenced entirely) so that I can keep working while my
> file is compiling. Is there a way to do this?
> Best,
> Robin Deits
>
>

[Vim-latex-devel] Redirect latex output to background (or split window)

[Robin D. <rob...@gm...>]

Hello all,

I have recently been playing around with vim-latex, and I'm really starting
to love it. So first, I should just thank all of you for your amazing work.

I have, however, run into an issue, which is that it is consistently
annoying that the latex output fills my entire vim window when I am
compiling, which preventing me from editing the .tex file until it is done.
It would be nice to have the output of the compiler directed to a temporary
split window (or even silenced entirely) so that I can keep working while my
file is compiling. Is there a way to do this?

Best,
Robin Deits

[Vim-latex-devel] Bug (probably) in texviewer.tex

[Martin S. <mar...@gm...>]

Dear all,

I started using the Vim LaTeX Suite only very recently and I'm very
happy with it. Today I had a little trouble getting the \ref{}
completion to work and it turned out the problem was that my working
directory name contains spaces. I digged in the code and I believe
that the problem is in texviewer.tex on line 757 (I'm using version
1.8.23-20100129-r1104). The original line is

\. 'r"' . fnameescape(fnamemodify(mainfname, ':p')) . '", '

and when I removed the fnameescape() call from it, thus becoming

\. 'r"' . fnamemodify(mainfname, ':p') . '", '

\ref{} completion started working again. I'm not sure whether this is
a correct fix but it seems to work for me. And if it is correct, you
might want to include it in some future version of the package.


Warm regards,

Martin Slota

[Vim-latex-devel] forced compilation and unsuccessful build

[Olga L. <ol...@he...>]

Dear all,

I have just switched to vim-latex and it is great. I have a question, I
know that there are few errors in my tex file, but I want to
(temporarily) ignore them. Each unsuccessful build results in the quick
fix buffer, and I have no clue how to compile file ignoring all errors?

Previously, using command line "r" would do this.

Many thanks,
Olga 

Re: [Vim-latex-devel] Bug with mapleader = " "

[ZyX <zy...@np...>]

Ответ на сообщение «Re: [Vim-latex-devel] Bug with mapleader = " "», 
присланное в 01:00:23 08 октября 2010, Пятница.
Отправитель: Mika Fischer:

> Also maybe an option not to set those mappings and let users set their
> own mappings would be useful.
It is the most useful option: I have to place
    function IMAP(...)
    endfunction
to my ftplugin/tex.vim in order not to have those very annoying insert mode 
mappings. Attached patch adds an option `g:latex_suite_omit_imap' that forbids 
using all IMAPs.

Текст сообщения:
> On Thu, Oct 7, 2010 at 22:17, ZyX <zy...@np...> wrote:
> > What problems do you have? If I do ``let g:mapleader="<Space>"'' before
> > loading tex file, everything works as expected. Maybe you tried to set
> > g:mapleader to literal space?
> 
> Yes, I did. I was under the impression that "<space>" would not work.
> I found some links to that effect:
> http://stackoverflow.com/questions/446269/can-i-use-space-as-mapleader-in-v
> im http://www.reddit.com/r/vim/comments/dh4u5/let_mapleader_space/
> 
> I have never tried it though. Maybe it's also an issue with missing
> quotes...
> 
> In any case the way vim-latex set the mappings was broken. I just
> changed it so that the behavior stays the same except for my problem.
> 
> > I think that ``g:mapleader'' should be replaced but not with
> > ``<Leader>'' but with ``g:latex_suite_mapleader'' or something like that.
> 
> I did not want to change this. But I agree it would make a lot of
> sense. Maybe this variable could then default to <Leader> to keep the
> current behavior?
> Also maybe an option not to set those mappings and let users set their
> own mappings would be useful.
> 
> Best,
>  Mika
> 
> ---------------------------------------------------------------------------
> --- Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Bug with mapleader = " "

[Mika F. <mik...@zo...>]

On Thu, Oct 7, 2010 at 22:17, ZyX <zy...@np...> wrote:
> What problems do you have? If I do ``let g:mapleader="<Space>"'' before loading
> tex file, everything works as expected. Maybe you tried to set g:mapleader to
> literal space?

Yes, I did. I was under the impression that "<space>" would not work.
I found some links to that effect:
http://stackoverflow.com/questions/446269/can-i-use-space-as-mapleader-in-vim
http://www.reddit.com/r/vim/comments/dh4u5/let_mapleader_space/

I have never tried it though. Maybe it's also an issue with missing quotes...

In any case the way vim-latex set the mappings was broken. I just
changed it so that the behavior stays the same except for my problem.

> I think that ``g:mapleader'' should be replaced but not with
> ``<Leader>'' but with ``g:latex_suite_mapleader'' or something like that.

I did not want to change this. But I agree it would make a lot of
sense. Maybe this variable could then default to <Leader> to keep the
current behavior?
Also maybe an option not to set those mappings and let users set their
own mappings would be useful.

Best,
 Mika

Re: [Vim-latex-devel] Bug with mapleader = " "

[ZyX <zy...@np...>]

Ответ на сообщение «[Vim-latex-devel] Bug with mapleader = " "», 
присланное в 23:26:23 07 октября 2010, Четверг.
Отправитель: Mika Fischer:

What problems do you have? If I do ``let g:mapleader="<Space>"'' before loading 
tex file, everything works as expected. Maybe you tried to set g:mapleader to 
literal space? I think that ``g:mapleader'' should be replaced but not with 
``<Leader>'' but with ``g:latex_suite_mapleader'' or something like that.

Текст сообщения:
> Hi,
> 
> there's a bug with vim-latex, when setting g:mapleader to <space>. The
> compile and view commands etc. get bound to "ll", "lv", and so on
> instead of "<space>ll", "<space>lv", and so on. Needless to say this
> messes things up quite a bit. The attached patch fixes this problem.
> 
> Please consider applying it.
> 
> Best regards,
>  Mika

Re: [Vim-latex-devel] Bug with mapleader = " "

[Mika F. <mik...@zo...>]

On Thu, Oct 7, 2010 at 22:21, Till Maas <ope...@ti...> wrote:
> I applied it in changeset 1109.

Great, thanks!

> There are more occurences of mapleader,
> e.g. in wizardfuncs.vim and texmenuconf.vim, don't they need to be
> patched?

No, because if I saw correctly, they're not used for mappings but for
displaying the mappings in the gvim menu and the wizard.

I guess it's not really helpful in this case, since the <space> will
probably not be visible anyway. Maybe space could be replaced by
<space> in this case? Or maybe just leave it as <leader> which
everybody who sets mapleader should know. In case it's not space, I
would leave it as it is now, as this way it's most useful to new
users...

Best,
 Mika

Re: [Vim-latex-devel] Keybindings reference

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

On Thu, Oct 07, 2010 at 09:34:02PM +0200, Mika Fischer wrote:

> I was unable to find a reference of the default keybindings and IMAPs
> that vim-latex provides.

Here are some:
http://vim-latex.sourceforge.net/documentation/latex-suite.html#latex-suite-commands-maps

> I case it really isn't there, maybe you could add a link to the
> following reference card to the documentation page:
> http://users.physik.fu-berlin.de/~mgoerz/blog/2008/05/vim-latexsuite-refcard/

I added a link.

Regards
Till

Re: [Vim-latex-devel] Bug with mapleader = " "

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

On Thu, Oct 07, 2010 at 09:26:23PM +0200, Mika Fischer wrote:
> Hi,
> 
> there's a bug with vim-latex, when setting g:mapleader to <space>. The
> compile and view commands etc. get bound to "ll", "lv", and so on
> instead of "<space>ll", "<space>lv", and so on. Needless to say this
> messes things up quite a bit. The attached patch fixes this problem.
> 
> Please consider applying it.

I applied it in changeset 1109. There are more occurences of mapleader,
e.g. in wizardfuncs.vim and texmenuconf.vim, don't they need to be
patched?

Regards
Till

[Vim-latex-devel] Keybindings reference

[Mika F. <mik...@zo...>]

Hi,

I was unable to find a reference of the default keybindings and IMAPs
that vim-latex provides.

I case it really isn't there, maybe you could add a link to the
following reference card to the documentation page:
http://users.physik.fu-berlin.de/~mgoerz/blog/2008/05/vim-latexsuite-refcard/

Best,
 Mika

[Vim-latex-devel] Bug with mapleader = " "

[Mika F. <mik...@zo...>]

Hi,

there's a bug with vim-latex, when setting g:mapleader to <space>. The
compile and view commands etc. get bound to "ll", "lv", and so on
instead of "<space>ll", "<space>lv", and so on. Needless to say this
messes things up quite a bit. The attached patch fixes this problem.

Please consider applying it.

Best regards,
 Mika

[Vim-latex-devel] modifying latex-suite syntax highlighting for Sweave (Rnw) files

[abr <all...@gm...>]

Hi folks,

Is there some easy way to tweak the syntax highlighting of latex-suite so it
will ignore Sweave/R code chunks embedded in LaTeX having the form:


<<echo=T>>==
# R code, often with "$"s which play havoc with syntax highlighting
x <- rnorm(10)
@


I know there are a handful of other people struggling with this problem, see
http://stackoverflow.com/questions/1504318/associate-rnw-with-vim-latex-suite

The solution proposed here [
http://feferraz.net/en/P/Sweave_Syntax_Highlighting_in_vim] works but it
doesn't seem compatible with latex-suite. It creates the following
after/syntax/noweb.vim file

runtime! syntax/tex.vim
unlet b:current_syntax

syntax include @nowebR syntax/r.vim
syntax region nowebChunk start="^<<.*>>=" end="^@" contains=@nowebR
syntax region Sexpr  start="\\Sexpr{"  end="}" keepend
hi Sexpr gui=bold guifg=chocolate2

let b:current_syntax="noweb"


Any thoughts? Suggestions?

cheers,

Allen Riddell

[Vim-latex-devel] Help with PDFview in windows

[Mak, T. <tim...@im...>]

Hi list,

I'm a new user of both Vim and latex-suite, and I'm having trouble configuring Latex-suite to PDF view my .pdf documents.

1. Because I'm used to Windows, I often add spaces to filenames. I managed to get pdflatex to compile my documents by altering:
g:Tex_CompileRule_pdf
 to include double quotes "$*"  before and after $*. However, how do I get Bibtex to do the same as well?

2. I've already set:
g:Tex_DefaultTargetFormat = 'pdf'

However, when I run \lv from Vim, it still tries to run Acrobat with my filename appended with a .dvi at the end. How can I change that to pdf?

Thanks very much for your help.

Yours,

Tim

[Vim-latex-devel] vim-latexsuite overwriting formatoptions?

[Ng Oon-Ee <ng...@gm...>]

Hi all,

My .vimrc sets some formatoptions (tcqo) for some other plugins that I
use, but on installing vim-latexsuite those options are ALWAYS
overwritten when I open my *.cpp and *.h files. My vim-foo isn't
strong enough to understand exactly why its happening, but I think its
about line 71-85 of /usr/share/vim/vimfiles/ftplugin/latex-suite, all
around the line that goes:-

set fo=

In my (basic) understanding the formatoptions are supposed to be
restored after that, but they don't seem to be. The same problem
happens with other files, but not when I first open vim (blank without
a file).

In my opinion vim-latexsuite should really change formatoptions when
the file is a bibtex or *.tex file. Can that be done with a simple
change? What other options do I have?

Thanks in advance,
Ng Oon-Ee

Re: [Vim-latex-devel] PATCH: Fold all %%fake, not just %%fakesection

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

Great. I checked in the patch from Gerd Wachsmuth (as is).

It's revision 1107.

--Ted

On 08/18/2010 02:52 PM, Till Maas wrote:
> Hi,
>
> On Wed, Aug 11, 2010 at 10:51:58AM -0400, Ted Pavlic wrote:
>
>> Either way, I'd be excited to see this merged into the devel branch
>> ASAP. I currently have my old version (which deferred to the nested
>
> you should now have commit access to the SVN repo on sourceforge, so you can
> commit the patch. Maybe you could also commit other patches, if there is a
> consensus for them here on the mailing list. Otherwise I hope to spend some time
> again on vim-latex within a month.
>
> Regards
> Till
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
>
>
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

[Vim-latex-devel] [ vim-latex-Patches-3057689 ] IMAP with mulitbyte lhs

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

Patches item #3057689, was opened at 2010-09-01 21:23
Message generated for change (Comment added) made by lux-vim-latex
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3057689&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: LuX (lux-vim-latex)
Assigned to: Nobody/Anonymous (nobody)
Summary: IMAP with mulitbyte lhs

Initial Comment:
The IMAP function, which comes with the latex-suite in the plugin imaps.vim, deals wrongly with multibyte left hand side (so-called lhs). The attached patch fixes this. 

Version number:
imaps.vim 997 2006-03-20 09:45:45Z srinathava $
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Dec  1 2008)

Example: 
You want to chain IMAP mapping, as follows: 
        call IMAP("\\subset", "⊂", "")
        call IMAP("⊂eq", "⊆", "")
Type "1234\subset", you see "1234⊂" (good). But if you add "eq", you see "12⊆" (bad) instead of "1234⊆".

Description:
The attached patch adds to imaps.vim two functions called s:MultiByteStrlen and s:MultiByteStrpart, analogous to Vim's functions strlen and strpart but which deal with strings character per character instead of byte per byte. Every call to strlen and strpart is then replaced by a call to these variants, and as far as I can see it solved the problem. 

----------------------------------------------------------------------

>Comment By: LuX (lux-vim-latex)
Date: 2010-09-06 19:53

Message:
Sorry, it appeared to me that the previously attached patch was not correct
(I did not apply 'diff' to the right files). But most of all the strategy
of changing every call to strlen and strpart by my s:MultiByte* variants is
not good: in some case, it is really strpart or strlen which must be used.


Example: 
The following command appears 3 times in imaps.vim: 
        strpart(getline(".", 0, col(".")-1)
What is expected is the content of the current line before the cursor.
Since col(".") returns the number of bytes, not of characters, until the
first byte (not the last one) of the character under the cursor, col(".")-1
is just the number of bytes in the current line before the cursor. Thus
strpart will return what expected, and MultiByteStrpart will not (not
always).

So this time I have looked carefully at every place in imps.vim where
strlen and strpart were used, and I changed them to there
s:MuliByte-variants ONLY when I was sure that it was needed (I left strlen
and strpart also when it did not make any difference to use them or
s:MultiByte*, for example when they are called only to test wether or not a
string is empty). 

The result of this better strategy is the attached patch.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3057689&group_id=52322

[Vim-latex-devel] [ vim-latex-Patches-3057689 ] IMAP with mulitbyte lhs

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

Patches item #3057689, was opened at 2010-09-01 21:23
Message generated for change (Tracker Item Submitted) made by lux-vim-latex
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3057689&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: LuX (lux-vim-latex)
Assigned to: Nobody/Anonymous (nobody)
Summary: IMAP with mulitbyte lhs

Initial Comment:
The IMAP function, which comes with the latex-suite in the plugin imaps.vim, deals wrongly with multibyte left hand side (so-called lhs). The attached patch fixes this. 

Version number:
imaps.vim 997 2006-03-20 09:45:45Z srinathava $
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Dec  1 2008)

Example: 
You want to chain IMAP mapping, as follows: 
        call IMAP("\\subset", "⊂", "")
        call IMAP("⊂eq", "⊆", "")
Type "1234\subset", you see "1234⊂" (good). But if you add "eq", you see "12⊆" (bad) instead of "1234⊆".

Description:
The attached patch adds to imaps.vim two functions called s:MultiByteStrlen and s:MultiByteStrpart, analogous to Vim's functions strlen and strpart but which deal with strings character per character instead of byte per byte. Every call to strlen and strpart is then replaced by a call to these variants, and as far as I can see it solved the problem. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3057689&group_id=52322

Re: [Vim-latex-devel] PATCH: Fold all %%fake, not just %%fakesection

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

Hi,

On Wed, Aug 11, 2010 at 10:51:58AM -0400, Ted Pavlic wrote:

> Either way, I'd be excited to see this merged into the devel branch
> ASAP. I currently have my old version (which deferred to the nested

you should now have commit access to the SVN repo on sourceforge, so you can
commit the patch. Maybe you could also commit other patches, if there is a
consensus for them here on the mailing list. Otherwise I hope to spend some time
again on vim-latex within a month.

Regards
Till