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

[Vim-latex-devel] latexsuite compile target

[nicolas <nic...@ma...>]

To be able to compile a *.tex file to pdf, ps and dvi I edit my .vim/ftplugin/texrc in the following way and I obtain the right file formats but I still don't understand why compile to target does not compile at all. If I specify the target format nothing happen. Please tell me how I can correct this problem since I saw one of my friend specifying html as target and obtaining an html file out of tex file.
 Thanks in advance

 TexLet g:Tex_DefaultTargetFormat = 'pdf'
 elsec
 TexLet g:Tex_DefaultTargetFormat = 'dvi'

 relaced by

 TexLet g:Tex_DefaultTargetFormat = 'pdf'
 endif


 I replace

 " TexLet g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*'

 by

 TexLet g:Tex_CompileRule_pdf = 'latex -interaction=nonstopmode $* && dvips -o $*.ps $*.dvi && ps2pdf $*.ps'

Re: [Vim-latex-devel] failed to forward search with Skim in Mac OS

[Peter V. <mai...@pe...>]

Hi,

works here.

I have also in my .vimrc this:

let g:Tex_ViewRule_pdf = 'Skim'

Maybe it works for you too.

Peter


On Mon, Apr 9, 2012 at 5:47 PM, Dengyu Liu <ld...@gm...> wrote:
> Hi all,
>
> I would like to do forward search with Skim in my Mac OS, but when I did command "\ls" in MacVim, there is only output of "call Tex_ForwardSearch()", but Skim didn't open(viewing wih "\lv" in Skim is fine).
>
> I am using Latex-Suite 1.8.23, and I included "-synctex" in my tex compile file. Does anyone know what the problem here? Thanks.
>
>
> Dengyu
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] failed to forward search with Skim in Mac OS

[Dengyu L. <ld...@gm...>]

Hi all,

I would like to do forward search with Skim in my Mac OS, but when I did command "\ls" in MacVim, there is only output of "call Tex_ForwardSearch()", but Skim didn't open(viewing wih "\lv" in Skim is fine).

I am using Latex-Suite 1.8.23, and I included "-synctex" in my tex compile file. Does anyone know what the problem here? Thanks.


Dengyu

Re: [Vim-latex-devel] How Do I Enable Latex-Suite on Styles (cls, sty)?

[Alessandro P. <ale...@la...>]

Hello,
did you put "filetype plugin on" before any autocmd in your .vimrc?

Alessandro

-- 
If God had intended for email to be written in HTML, then the
traditional signoff of prayers would be </amen> -- Tom Liston

[Vim-latex-devel] How Do I Enable Latex-Suite on Styles (cls, sty)?

[Alex X. A. S. <ber...@gm...>]

Hi,
I'm a new and novice user of Latex-Suite, and can't seem to find a way to
activate latex-suite for cls or sty files. How can I do this?

Thanks before.

[Vim-latex-devel] [PATCH] main.vim: \iota IMAP was missing

[<ale...@la...>]

Although documented, e.g. in ":Tshortcuts m" output, the "`i" mapping is
missing from main.vim.

Regards,
Alessandro P.

---
 ftplugin/latex-suite/main.vim |    1 +
 1 file changed, 1 insertion(+)

diff --git a/ftplugin/latex-suite/main.vim b/ftplugin/latex-suite/main.vim
index 65588c9..ad27b91 100644
--- a/ftplugin/latex-suite/main.vim
+++ b/ftplugin/latex-suite/main.vim
@@ -97,6 +97,7 @@ if !exists('s:doneMappings')
 	call IMAP(g:Tex_Leader.'f', '\varphi', 'tex')
 	call IMAP(g:Tex_Leader.'g', '\gamma', 'tex')
 	call IMAP(g:Tex_Leader.'h', '\eta', 'tex')
+	call IMAP(g:Tex_Leader.'i', '\iota', 'tex')
 	call IMAP(g:Tex_Leader.'k', '\kappa', 'tex')
 	call IMAP(g:Tex_Leader.'l', '\lambda', 'tex')
 	call IMAP(g:Tex_Leader.'m', '\mu', 'tex')
-- 
1.7.9.4

[Vim-latex-devel] latexsuite

[nicolas <nic...@ma...>]

Hello,
 I have problem compiling tex file with latexsuite on Ubuntu. 
 in my .vimrc, I have the following lines : 

 filetype plugin on
 set grepprg=grep\ -nH\ $*
 filetype indent on
 let g:tex_flavor='latex'


 When I go to the menu and ask compile target if I put dvi, a dvi file is
 generated but I ask for *.pdf nothing happen.


 Can anyone give me some pointers on this?

[Vim-latex-devel] Bug report about cite completion

[Raniere G. S. <r.g...@gm...>]

Hello all,
I notice that when the folder name where my .tex file is locate has ':',
'[', ']' or any other special character the cite completion don't work.
When I rename the folder without the special character the cite completion
work fine.
That's all.

Raniere Gaia Costa da Silva

Re: [Vim-latex-devel] vim-latex menu disappeared after gvim upgrade

[ahmet n. <ahm...@ya...>]

Dear List,
I have found that latex-menu reappears if I use vim-gtk instead of vim-gnome.  I removed ".gnome2/vim (or .gnome/vim" file and the menu displayed again. So,
vim-gnome displays latex-menu again.

I have solved my previous problem posted on the list. 

Regards,
Ahmet


----- Original Message -----
From: ahmet nurlu <ahm...@ya...>
To: "vim...@li..." <vim...@li...>
Cc: 
Sent: Thursday, March 8, 2012 8:33 PM
Subject: vim-latex menu disappeared after gvim upgrade

Hi List,
After a recent upgrade on my system(debian-testing), vim-latex menu doesn't show on gvim (version 7.3.429)  Even though vim-latex commands have no problem to run, I don't know why the latex-menu disappeared. After downgrading gvim, the menu is back again.

Any solution is welcome.

Regards,
Ahmet 

[Vim-latex-devel] how to set search and inverse-search between suite-latex and sumatraPDF

[yanzhisheng <yan...@ya...>]

hi, everyone
I want to search and inverse-search between suite-latex and sumatraPDF, what should I do?
 
I have read a lot of blogs, and much of them is about the patch command, but it fails in my computer. Has anyone succeed?
 
the vim is v7.3, and the suite-latex is the newest version: vim-latex-1.8.23-20120125.768-git8b62284
 
thanks.
 
---yakex

[Vim-latex-devel] vim-latex menu disappeared after gvim upgrade

[ahmet n. <ahm...@ya...>]

Hi List,
After a recent upgrade on my system(debian-testing), vim-latex menu doesn't show on gvim (version 7.3.429)  Even though vim-latex commands have no problem to run, I don't know why the latex-menu disappeared. After downgrading gvim, the menu is back again.

Any solution is welcome.

Regards,
Ahmet 

Re: [Vim-latex-devel] how to stop jumping to quickfix/ log views and keep the source file viewable?

[Julien C. <jul...@gm...>]

> Yeah, but then you have to use Eclipse... [qed]

Point taken, hahaha.

> (and yet you're still reading the list... :) )

That's a good company, hard to leave it ;)

All the best,

Julien

Re: [Vim-latex-devel] how to stop jumping to quickfix/ log views and keep the source file viewable?

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

> reason for having regretfully stopped using vim-latex and moved to
> Texlipse.

Yeah, but then you have to use Eclipse... [qed]

(and yet you're still reading the list... :) )

--Ted

> All the best,
> 
> Julien
> 
> On Sun, Feb 26, 2012 at 4:53 PM, Ted Pavlic <te...@te...> wrote:
>> This is a well known problem with Vim (and not just Vim-LaTeX).
>> Certainly the problem and several solutions have been archived in many
>> places. It's too bad there's not a more visible FAQ that could address
>> it. Maybe there would be a way for vim-latex to detect a likely instance
>> of this problem and give appropriate instructions.
>>
>> Regardless, you can find more information about the problem and some
>> solutions at:
>>
>> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>>
>> I recommend:
>>
>> * Using the latest version of Vim-LaTeX from git. That way you'll have
>> the most updated errorformat strings.
>>
>> * Adding -file-line-error to your latex or pdflatex CompileRule (maybe
>> this shouldn't be done by default). For example, you can use:
>>
>> let g:Tex_CompileRule_pdf = 'pdflatex -file-line-error
>> -interaction=nonstopmode $*'
>>
>> in your .vimrc.
>>
>> * If it's an option for your operation system, install the vimlatex (or
>> vimlatex.py) scripts on your system and add them to your CompileRule as
>> well.
>>
>> Doing at least the first two of those will greatly improve Vim-LaTeX's
>> ability to properly catch errors and not direct you to unrelated files.
>>
>> Best --
>> Ted
>>
>> On 02/26/2012 08:40 AM, yanzhisheng wrote:
>>> hi, everyone
>>> The GVim I used now is v7.3.46.
>>> I use pdflatex to compile the *.tex source file. After it's completed,
>>> the gvim automatically open three split windows ,
>>> (1)  *.sty
>>> (2) quickfix
>>> (3)  *.log
>>> and the cursor is placed in the quickfix window indicating there is a waring
>>> related to the *.sty file in the first window.
>>> I thought this is very very uncomfortable!!! Because the *.tex window is
>>> hidden
>>>  (has become background).
>>>  How should I do the keep the *.tex window is viewable even if
>>> there is a waring or a error encountered in the compiling process?
>>> thanks.
>>> ---yakex
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Virtualization & Cloud Management Using Capacity Planning
>>> Cloud computing makes use of virtualization - but cloud computing
>>> also focuses on allowing computing to be delivered as a service.
>>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>>>
>>>
>>>
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>> --
>> Ted Pavlic <te...@te...>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

Re: [Vim-latex-devel] how to stop jumping to quickfix/ log views and keep the source file viewable?

[Julien C. <jul...@gm...>]

And, as I was told years ago when I grumbled about the same problem,
there's the possibility to hit Ctrl-O to go back to your latest entry
point, i.e. go back to the tex file. Not beautiful, but does the
trick.

To be honest, this kind of bother (along with another frequent problem
mentioned on this list: the keyboard shortcuts messing with the
accents -- which you can fix but keeps getting in the way) is my main
reason for having regretfully stopped using vim-latex and moved to
Texlipse.

All the best,

Julien

On Sun, Feb 26, 2012 at 4:53 PM, Ted Pavlic <te...@te...> wrote:
> This is a well known problem with Vim (and not just Vim-LaTeX).
> Certainly the problem and several solutions have been archived in many
> places. It's too bad there's not a more visible FAQ that could address
> it. Maybe there would be a way for vim-latex to detect a likely instance
> of this problem and give appropriate instructions.
>
> Regardless, you can find more information about the problem and some
> solutions at:
>
> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>
> I recommend:
>
> * Using the latest version of Vim-LaTeX from git. That way you'll have
> the most updated errorformat strings.
>
> * Adding -file-line-error to your latex or pdflatex CompileRule (maybe
> this shouldn't be done by default). For example, you can use:
>
> let g:Tex_CompileRule_pdf = 'pdflatex -file-line-error
> -interaction=nonstopmode $*'
>
> in your .vimrc.
>
> * If it's an option for your operation system, install the vimlatex (or
> vimlatex.py) scripts on your system and add them to your CompileRule as
> well.
>
> Doing at least the first two of those will greatly improve Vim-LaTeX's
> ability to properly catch errors and not direct you to unrelated files.
>
> Best --
> Ted
>
> On 02/26/2012 08:40 AM, yanzhisheng wrote:
>> hi, everyone
>> The GVim I used now is v7.3.46.
>> I use pdflatex to compile the *.tex source file. After it's completed,
>> the gvim automatically open three split windows ,
>> (1)  *.sty
>> (2) quickfix
>> (3)  *.log
>> and the cursor is placed in the quickfix window indicating there is a waring
>> related to the *.sty file in the first window.
>> I thought this is very very uncomfortable!!! Because the *.tex window is
>> hidden
>>  (has become background).
>>  How should I do the keep the *.tex window is viewable even if
>> there is a waring or a error encountered in the compiling process?
>> thanks.
>> ---yakex
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>>
>>
>>
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
> --
> Ted Pavlic <te...@te...>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] how to stop jumping to quickfix/ log views and keep the source file viewable?

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

This is a well known problem with Vim (and not just Vim-LaTeX).
Certainly the problem and several solutions have been archived in many
places. It's too bad there's not a more visible FAQ that could address
it. Maybe there would be a way for vim-latex to detect a likely instance
of this problem and give appropriate instructions.

Regardless, you can find more information about the problem and some
solutions at:

http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html

I recommend:

* Using the latest version of Vim-LaTeX from git. That way you'll have
the most updated errorformat strings.

* Adding -file-line-error to your latex or pdflatex CompileRule (maybe
this shouldn't be done by default). For example, you can use:

let g:Tex_CompileRule_pdf = 'pdflatex -file-line-error
-interaction=nonstopmode $*'

in your .vimrc.

* If it's an option for your operation system, install the vimlatex (or
vimlatex.py) scripts on your system and add them to your CompileRule as
well.

Doing at least the first two of those will greatly improve Vim-LaTeX's
ability to properly catch errors and not direct you to unrelated files.

Best --
Ted

On 02/26/2012 08:40 AM, yanzhisheng wrote:
> hi, everyone
> The GVim I used now is v7.3.46.
> I use pdflatex to compile the *.tex source file. After it's completed,
> the gvim automatically open three split windows ,
> (1)  *.sty
> (2) quickfix
> (3)  *.log
> and the cursor is placed in the quickfix window indicating there is a waring
> related to the *.sty file in the first window.
> I thought this is very very uncomfortable!!! Because the *.tex window is
> hidden
>  (has become background). 
>  How should I do the keep the *.tex window is viewable even if
> there is a waring or a error encountered in the compiling process?
> thanks.
> ---yakex
>  
> 
> 
> 
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

[Vim-latex-devel] how to stop jumping to quickfix/ log views and keep the source file viewable?

[yanzhisheng <yan...@ya...>]

hi, everyone
The GVim I used now is v7.3.46.
I use pdflatex to compile the *.tex source file. After it's completed, 
the gvim automatically open three split windows , 
(1)  *.sty 
(2) quickfix
(3)  *.log
and the cursor is placed in the quickfix window indicating there is a waring
related to the *.sty file in the first window. 
I thought this is very very uncomfortable!!! Because the *.tex window is hidden
 (has become background). 
 How should I do the keep the *.tex window is viewable even if
there is a waring or a error encountered in the compiling process?
thanks.
---yakex
 

[Vim-latex-devel] Cite completion does not work in included tex file

[Peter V. <mai...@pe...>]

Hi List,

As the subject says cite completion does not work in included files.
When trying to complete a cite a quickfix window opens with an empty
__OUTLINE__ buffer. Also every time I hit F9 a new empty buffer is
created and remains open.

When I hit F9 in the master file cite completion works and after that
cite completion in included files works also.

Thanks,
Peter

Re: [Vim-latex-devel] Compilation creates empty buffers

[Peter V. <mai...@pe...>]

Ok, found out that the empty buffers are not generated from compiling.

The empty buffers appear after opening quickfix window for cite completion.

Peter

On Sat, Feb 11, 2012 at 4:02 PM, Peter Vasil
<mai...@pe...> wrote:
> It is strange, but I can't reproduce the problem anymore. Somehow the
> compilation doesn't create empty buffers anymore. Maybe it was some
> other setting which caused this. And yes I always create a file which
> has .latexmain as extension. i.e if my main file is main.tex then I
> create a file which is called main.tex.latexmain and everything works.
>
> Sorry for the noise, but the empty buffers were quite annoying.
>
> Peter
>
>
> On Wed, Feb 8, 2012 at 9:45 PM, Ted Pavlic <te...@te...> wrote:
>> Peter --
>>
>>        Can you give a minimal working example?
>>
>>        Also, let's say you have a file called:
>>
>> test.tex
>>
>> and you created a latexmain called:
>>
>> test.latexmain
>>
>> It is known that Vim-LaTeX will create an empty buffer called "test." To
>> get around this, name your latexmain:
>>
>> test.tex.latexmain
>>
>> This is the name that Vim-LaTeX expects. It just happens that getting
>> rid of the "tex" mostly works...
>>
>> --Ted
>>
>> On 01/27/2012 06:58 AM, Peter Vasil wrote:
>>> Hi,
>>>
>>> I dont know if its just me but compilation creates an empty buffer
>>> with the same name as the .tex file I compile.
>>>
>>> Peter
>>>
>>> ------------------------------------------------------------------------------
>>> Try before you buy = See our experts in action!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-dev2
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>> --
>> Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] é problem

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

Il 21/02/2012 07:49, Pierre-Alain Bourdil ha scritto:
>
>
>   Hi, what if you unmap the<Plug>Tex_LeftRight  ?

nothing, I still get \label{}<++>
Maybe I'm editing the wrong file?

Re: [Vim-latex-devel] é problem

[Pierre-Alain B. <pab...@la...>]

 

 Hi, what if you unmap the <Plug>Tex_LeftRight  ? 



+
 
Le Lundi 20 Février 2012 22:19 CET, Guido Milanese <gui...@un...> a écrit: 
 
> Il 20/02/2012 10:18, Gerd Wachsmuth ha scritto:
> > Hi Guido,
> >
> > Vim cannot distinguish between "ì" and<M-l>  (meta/alt + l). Hence,
> > typing ì is superseeded by the mapping to<Plug>Tex_LeftRight in the
> > file "ftplugin/latex-suite/brackets.vim".
> >
> > A workaround would be the mapping similar
> >
> > imap<buffer>  <leader>lr<Plug>Tex_LeftRight
> >
> > in "~/.vim/ftplugin/tex.vim".
> 
> Thanks! not solved, unfortunately: still getting \label{}
> I really cannot remember what I did in the previous installation... I 
> changed also the backup with the new version and I have no copy left.
> 
> g.
> 
> -- 
> Guido Milanese - Professor of Latin
> Universita' Cattolica del Sacro Cuore, Milano and Brescia, Italy
> http://docenti.unicatt.it/ita/guido_fabrizio_milanese/
> http://www.arsantiqua.org
> 
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!

> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
 
 
 
 

Re: [Vim-latex-devel] é problem

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

Il 20/02/2012 10:18, Gerd Wachsmuth ha scritto:
> Hi Guido,
>
> Vim cannot distinguish between "ì" and<M-l>  (meta/alt + l). Hence,
> typing ì is superseeded by the mapping to<Plug>Tex_LeftRight in the
> file "ftplugin/latex-suite/brackets.vim".
>
> A workaround would be the mapping similar
>
> imap<buffer>  <leader>lr<Plug>Tex_LeftRight
>
> in "~/.vim/ftplugin/tex.vim".

Thanks! not solved, unfortunately: still getting \label{}
I really cannot remember what I did in the previous installation... I 
changed also the backup with the new version and I have no copy left.

g.

-- 
Guido Milanese - Professor of Latin
Universita' Cattolica del Sacro Cuore, Milano and Brescia, Italy
http://docenti.unicatt.it/ita/guido_fabrizio_milanese/
http://www.arsantiqua.org

Re: [Vim-latex-devel] é problem

[Germain V. <ger...@un...>]

Hi all

In this discussion, there is a post with a table which shows all pairs 
accent+character.

https://groups.google.com/group/vim_use/browse_thread/thread/d7d53c2aabb72640/589754392c22bd8f?hl=fr&lnk=gst&q=germain#589754392c22bd8f

Regards

Germain

Le 20/02/2012 10:18, Gerd Wachsmuth a écrit :
> Hi Guido,
>
> Vim cannot distinguish between "ì" and<M-l>  (meta/alt + l). Hence,
> typing ì is superseeded by the mapping to<Plug>Tex_LeftRight in the
> file "ftplugin/latex-suite/brackets.vim".
>
> A workaround would be the mapping similar
>
> imap<buffer>  <leader>lr<Plug>Tex_LeftRight
>
> in "~/.vim/ftplugin/tex.vim".
>
>
> @all: Is there a table which shows all those pairs of accent+character
> and<M-character>  which are linked in Vim? However, this should be added
> to the FAQ.
>
> Best regards
> Gerd
>
>
> On 02/10/2012 12:30 AM, Guido Milanese wrote:
>> I am sorry to return to this ultra-faq question, but after a new
>> installation I cannot find the solution to another well known problem,
>> the accented i (ì) producing 'label{}'. I added the usual customisations
>> to the ftplugin/tex.vim as suggested in the FAQ, but to no success. The
>> 'ì' key still produces "label{}" and not the required accented letter.
>>
>> Thanks for your help!
>> guido, italy
>>
>> ------------------------------------------------------------------------------
>> Virtualization&  Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Maître de Conférence
Université de Pau et des pays de l'Adour
Institut Pluridisciplinaire de Recherche sur l'Environnement et les
Matériaux
Équipe de Chimie Physique
email  : ger...@un...
Tel    : 05 59 40 78 51
page   : http://gvallver.perso.univ-pau.fr
Le bonheur de ta vie dépend de la qualité de tes pensées (Marc Aurèle)

Re: [Vim-latex-devel] é problem

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

Hi Guido,

Vim cannot distinguish between "ì" and <M-l> (meta/alt + l). Hence,
typing ì is superseeded by the mapping to <Plug>Tex_LeftRight in the
file "ftplugin/latex-suite/brackets.vim".

A workaround would be the mapping similar

imap <buffer> <leader>lr <Plug>Tex_LeftRight

in "~/.vim/ftplugin/tex.vim".


@all: Is there a table which shows all those pairs of accent+character
and <M-character> which are linked in Vim? However, this should be added
to the FAQ.

Best regards
Gerd


On 02/10/2012 12:30 AM, Guido Milanese wrote:
> I am sorry to return to this ultra-faq question, but after a new 
> installation I cannot find the solution to another well known problem, 
> the accented i (ì) producing 'label{}'. I added the usual customisations 
> to the ftplugin/tex.vim as suggested in the FAQ, but to no success. The 
> 'ì' key still produces "label{}" and not the required accented letter.
> 
> Thanks for your help!
> guido, italy
> 
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] [PATCH] Okular needs absolut path of tex file for forward search.

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

Applied. Thanks.

On Sun, Feb 19, 2012 at 5:35 PM,  <mai...@pe...> wrote:
> From: ptrv <ma...@pe...>
>
> ---
>  ftplugin/latex-suite/compiler.vim |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/ftplugin/latex-suite/compiler.vim b/ftplugin/latex-suite/compiler.vim
> index b67fd2b..28213fa 100644
> --- a/ftplugin/latex-suite/compiler.vim
> +++ b/ftplugin/latex-suite/compiler.vim
> @@ -392,7 +392,7 @@ function! Tex_ForwardSearchLaTeX()
>
>                        elseif viewer =~ '^ *okular'
>
> -                               let execString = 'silent! !'.viewer.' --unique '.mainfnameRoot.'.'.s:target.'\#src:'.line('.').expand("%")
> +                               let execString = 'silent! !'.viewer.' --unique '.mainfnameRoot.'.'.s:target.'\#src:'.line('.').expand("%:p")
>
>                        endif
>
> --
> 1.7.9
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel



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

[Vim-latex-devel] [PATCH] Okular needs absolut path of tex file for forward search.

[<mai...@pe...>]

From: ptrv <ma...@pe...>

---
 ftplugin/latex-suite/compiler.vim |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/ftplugin/latex-suite/compiler.vim b/ftplugin/latex-suite/compiler.vim
index b67fd2b..28213fa 100644
--- a/ftplugin/latex-suite/compiler.vim
+++ b/ftplugin/latex-suite/compiler.vim
@@ -392,7 +392,7 @@ function! Tex_ForwardSearchLaTeX()
 
 			elseif viewer =~ '^ *okular'
 
-				let execString = 'silent! !'.viewer.' --unique '.mainfnameRoot.'.'.s:target.'\#src:'.line('.').expand("%")
+				let execString = 'silent! !'.viewer.' --unique '.mainfnameRoot.'.'.s:target.'\#src:'.line('.').expand("%:p")
 
 			endif
 
-- 
1.7.9