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

Re: [Vim-latex-devel] Viewing pdf

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

>== Auszüge aus der Nachricht von  Mario D vom 2016-03-07 19:26:
> More or less I have solved the problem I asked about: the solution is as
> follows (from my tex.vim):
> 
> ---------------------------------------------------------
> function! Set_PDF()
>     let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_ViewRule_pdf =  'okular --unique 2>/dev/null 1>&2 '
>     let g:Tex_DefaultTargetFormat = 'pdf'
>     exec 'TTarget '.g:Tex_DefaultTargetFormat
> endfunction
> function! Set_LaTeX()
>     let g:Tex_CompileRule_dvi = 'latex -src-specials
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_ViewRule_dvi = 'xdvi 2>/dev/null 1>&2 '
>     let g:Tex_DefaultTargetFormat = 'dvi'
>     exec 'TTarget '.g:Tex_DefaultTargetFormat
> endfunction
> noremap <leader>latex :call Set_LaTeX()
> noremap <leader>pdf   :call Set_PDF()
> if getline(1) =~ "PDFLaTeX" | :call Set_PDF() | endif
> -------------------------------------------------------------
> 
> Now, from within a file I am able to switch pdf/latex compilation and
> correct visualization.
> 
> The only thing that I can not fix is the following: I would like to have
> the file recognized upon opening. For this, if a file is meant to be
> pdflatex it has the first line equal to
> 
> %PDFLaTeX
> 
> so that it should trigger the "if getline..." in tex.vim
> 
> The problem is that when I open such file I get the following error:
> 
> "file.tex"  194L, 5881C
> Error detected while processing function Set_PDF:
> line    4:
> E492: Not an editor command: TTarget pdf

Obviously, your tex.vim is loaded before TTarget is defined.

`grep -rn TTarget ~/.vim` reveals TTarget is defined on line 86 in
~/.vim/ftplugin/latex-suite/compiler.vim, and a

`find ~/.vim -name tex.vim` shows me three tex.vim in my installation,
so that the location "my tex.vim" is not exactly unambiguous. I've no
idea in which order vim loads these files.

> 
> How do I fix this?

Did you put your customization in the "after" folder?
(i.e. ~/.vim/after/ftplugin/tex.vim?) This file should be loaded *after*
all other so that TTarget should be defined on this time.

> 
> TIA

Transitory Ischemic Attack?

Regards, Ruthard

-- 

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

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

Re: [Vim-latex-devel] Viewing pdf

[Mario D <eg...@gm...>]

More or less I have solved the problem I asked about: the solution is as
follows (from my tex.vim):

---------------------------------------------------------
function! Set_PDF()
    let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1
-interaction=nonstopmode -file-line-error-style $*'
    let g:Tex_ViewRule_pdf =  'okular --unique 2>/dev/null 1>&2 '
    let g:Tex_DefaultTargetFormat = 'pdf'
    exec 'TTarget '.g:Tex_DefaultTargetFormat
endfunction
function! Set_LaTeX()
    let g:Tex_CompileRule_dvi = 'latex -src-specials
-interaction=nonstopmode -file-line-error-style $*'
    let g:Tex_ViewRule_dvi = 'xdvi 2>/dev/null 1>&2 '
    let g:Tex_DefaultTargetFormat = 'dvi'
    exec 'TTarget '.g:Tex_DefaultTargetFormat
endfunction
noremap <leader>latex :call Set_LaTeX()
noremap <leader>pdf   :call Set_PDF()
if getline(1) =~ "PDFLaTeX" | :call Set_PDF() | endif
-------------------------------------------------------------

Now, from within a file I am able to switch pdf/latex compilation and
correct visualization.

The only thing that I can not fix is the following: I would like to have
the file recognized upon opening. For this, if a file is meant to be
pdflatex it has the first line equal to

%PDFLaTeX

so that it should trigger the "if getline..." in tex.vim

The problem is that when I open such file I get the following error:

"file.tex"  194L, 5881C
Error detected while processing function Set_PDF:
line    4:
E492: Not an editor command: TTarget pdf

How do I fix this?

TIA


2016-02-23 9:21 GMT+01:00 Mario D <eg...@gm...>:

> In my ~/.vim/ftplugin/tex.vim I defined the following:
>
> function! Set_PDF()
>     let g:Tex_DefaultTargetFormat = 'pdf'
>     let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_CompileRule_dvi = 'pdflatex --synctex=1
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_ViewRule_pdf =  'okular --unique 2>/dev/null 1>&2 '
>     let g:Tex_ViewRule_dvi = 'okular --unique 2>/dev/null 1>&2 '
>     let g:Tex_MultipleCompileFormats = ''
> endfunction
>
> function! Set_LaTeX()
>     let g:Tex_DefaultTargetFormat = 'dvi'
>     let g:Tex_CompileRule_dvi = 'latex -src-specials
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_ViewRule_dvi = 'xdvi 2>/dev/null 1>&2 '
>     let g:Tex_MultipleCompileFormats = ''
> endfunction
>
> noremap <leader>latex :call Set_LaTeX()
> noremap <leader>pdf   :call Set_PDF()
>
> My intention is the following: if I use ,pdf  (my leader is ,), then vim
> should be set up to produce pdf whereas if I use ,latex then it should
> produce dvi.
>
> Now I open a latex file which should produce pdf, I call ,pdf and I
> compile using ,ll
> Everything is fine.
> My problem is when I try see the resulting pdf: if I use ,lv then what I
> get is the dvi file displayed by xdvi whereas if I use ,ls then I get again
> the dvi file but this time it is displayed by okular.
> What I would like is that by either I should get displayed the pdf by
> means of okular.
> What am I doing wrong?
>
> Thanks
>

Re: [Vim-latex-devel] no effect of g:Tex_SmartQuoteOpen when using \DeclareLanguageMapping in a tex-file

[<c....@po...>]

No one has an idea about it or tested that?

Should I open an official BugTracker ticket for that?

[Vim-latex-devel] no effect of g:Tex_SmartQuoteOpen when using \DeclareLanguageMapping in a tex-file

[<c....@po...>]

Not sure but maybe I found a exotic problem. ;)

The tex-code I attached explains itself.

I setup my vimrc like this:

   let g:Tex_SmartQuoteOpen = '„'
   let g:Tex_SmartQuoteClose = '“'

In an (nearly) empty tex-file this work fine and is correct shown in
the PDF file produced with xelatex.

But when using biblatex with apa-style and especially this line
	
   \DeclareLanguageMapping{german}{german-apa}

vim produce quotes like this, while typing

    "`test"'

This is explained in the code, too.

I am not sure from which package this \DeclareLanguageMapping comes
from. But I need it using the apa-style with German translation.

What happens there behind my vim?

Re: [Vim-latex-devel] templates user commands on several lines

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

Hello,

Not related to vim-latex, but to vim reading the template as typed and
thus adding automatically indents. You have to set the "paste" option
first (:set paste)(:set nopaste to turn off) to be able to paste without
indenting.


I've got:

~/.vim/after/ftplugin/tex.vim
----------------%<------------------
""" set paste for TTemplate
function TexTemplateWithPasteSet()
	set paste
	TTemplate
	set nopaste
endfunction
command Template call TexTemplateWithPasteSet()
----------------%<------------------

and use my command :Template rather than :TTemplate to avoid the
annoying setting and unsetting of paste.

Regards, Ruthard

>== Auszüge aus der Nachricht von  pierrO vom 2016-02-28 16:55:
> Hello,
> In a template, I want to put a command as :
> 
> \newcommand{\me}{%
> \par%
> -- Moi :}
> 
> When I load this template in a document, the command is indented, and if 
> there are multiple commands beside, indents increase each line.
> Could you give me a way to understand how indentation works in 
> vim-latex, because sometimes when I write text with user commands, lines 
> become indented but  I understand why ?
> Thank you.
> 

-- 

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

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

[Vim-latex-devel] templates user commands on several lines

[pierrO <car...@ov...>]

Hello,
In a template, I want to put a command as :

\newcommand{\me}{%
\par%
-- Moi :}

When I load this template in a document, the command is indented, and if 
there are multiple commands beside, indents increase each line.
Could you give me a way to understand how indentation works in 
vim-latex, because sometimes when I write text with user commands, lines 
become indented but  I understand why ?
Thank you.

-- 
pierrO

Re: [Vim-latex-devel] German quotes

[<c....@po...>]

Not sure but maybe I found a exotic problem. ;)

The tex-code I attached explains itself.

I setup my vimrc like this:

   let g:Tex_SmartQuoteOpen = '„'
   let g:Tex_SmartQuoteClose = '“'

In an (nearly) empty tex-file this work fine and is correct shown in
the PDF file produced with xelatex.

But when using biblatex with apa-style and escpecialy this line
	
   \DeclareLanguageMapping{german}{german-apa}

vim produce quotes like this, while typing

    "`test"'

This is explained in the code, too.

I am not sure from which package this \DeclareLanguageMapping comes
from. But I need it using the apa-style with German translation.

Re: [Vim-latex-devel] German quotes

[<c....@po...>]

On 2016-02-26 18:41 Bodo Graumann <ma...@bo...> wrote:
> let g:Tex_SmartQuoteOpen = "\\enquote{"
> let g:Tex_SmartQuoteClose = "}"

Using LaTeX it would be fine, but with XeTeX I would value that only as
a workaround. :) I don't want to use to much macros for such simple
things. This makes the code easier to read.
A quote is a character nothing more. And XeTeX can interpret each
unicode-character itself without any help. The problem is only that the
keyboard doesn't know about a open-quote-character. ;)

I prefer the solution with ,,ligatures''.

kind regards
Christian

Re: [Vim-latex-devel] German quotes

[Bodo G. <ma...@bo...>]

Hi,

you could also consider using the csquotes package. This way it is easy
to switch quoting styles. The vim settings for it, that I use, are:

let g:Tex_SmartQuoteOpen = "\\enquote{"
let g:Tex_SmartQuoteClose = "}"

Though in contrast to Gay, I keep them in

.vim/after/ftplugin/tex/latex_suite.vim

together with my IMAPs etc.
The tex code for loading the package could be something like:

\usepackage[autostyle,german=quotes]{csquotes}

best regards,
Bodo

Am Fri, 26 Feb 2016 08:56:11 -0800
schrieb Gary Johnson <gar...@sp...>:

| On 2016-02-26, c.buhtz wrote:
| > When I use the quote-key on my keyboard vim-latexsuite generates
| > this out of it
| > 
| >   ``test''
| > 
| > This would generate non-german (only on top) quotes in the XeLaTeX
| > outputed PDF-file.
| > 
| > I would need
| > 
| >   ,,test''
| > 
| > because this is interpreted as german-quotest (first buttom, last
| > top).
| > 
| > How can I realize this in the settings of vim-latexsuite. My
| > underlying system is a german(!) Kubuntu 14.04.4 LTS. Vim itself
| > knows I am German because it offers the German spellchecker.
| 
| This should do it:
| 
|     let b:Tex_SmartQuoteOpen  = ",,"
| 
| I put settings like that in ~/.vim/ftplugin/tex.vim.
| 
| Regards,
| Gay
| 
| 
| ------------------------------------------------------------------------------
| Site24x7 APM Insight: Get Deep Visibility into Application Performance
| APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
| Monitor end-to-end web transactions and take corrective actions now
| Troubleshoot faster and improve end-user experience. Signup Now!
| http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
| _______________________________________________
| Vim-latex-devel mailing list
| Vim...@li...
| https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] German quotes

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

On 2016-02-26, c.buhtz wrote:
> When I use the quote-key on my keyboard vim-latexsuite generates  this
> out of it
> 
>   ``test''
> 
> This would generate non-german (only on top) quotes in the XeLaTeX
> outputed PDF-file.
> 
> I would need
> 
>   ,,test''
> 
> because this is interpreted as german-quotest (first buttom, last top).
> 
> How can I realize this in the settings of vim-latexsuite. My underlying
> system is a german(!) Kubuntu 14.04.4 LTS. Vim itself knows I am German
> because it offers the German spellchecker.

This should do it:

    let b:Tex_SmartQuoteOpen  = ",,"

I put settings like that in ~/.vim/ftplugin/tex.vim.

Regards,
Gay

[Vim-latex-devel] German quotes

[<c....@po...>]

When I use the quote-key on my keyboard vim-latexsuite generates  this
out of it

  ``test''

This would generate non-german (only on top) quotes in the XeLaTeX
outputed PDF-file.

I would need

  ,,test''

because this is interpreted as german-quotest (first buttom, last top).

How can I realize this in the settings of vim-latexsuite. My underlying
system is a german(!) Kubuntu 14.04.4 LTS. Vim itself knows I am German
because it offers the German spellchecker.

Re: [Vim-latex-devel] Viewing pdf

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

Hello Mario,

I cannot tell what you are doing wrong, as the vim-latex style of
compiling and viewing is not very intuitive to me.

My solution is to use the latex binaries directly:

In .vim/after/ftplugin/tex.vim I have:
(pdf is a link to my pdf-viewer of the day -- usually mupdf)

--------------------%<--------------------------    
""" compile and display
function TexCompileAndDisplayPdf()
	:write
	:!xelatex % && pdf %<.pdf
endfunction
command Compile call TexCompileAndDisplayPdf()

""" display
function TexDisplayPdf()
	:!pdf %<.pdf
endfunction
command Display call TexDisplayPdf()
--------------------%<--------------------------    


By the way, the -vim/after/{ftplugin,plugin,...} tree is the intended
place for customization.  The files in the .vim/after tree are loaded
AFTER (hence the name) the main files thus overriding the default
settings.  Furthermore customizations of the main plugin files will be
lost on updates, the ./vim/after tree is left untouched on update.

Regards, Ruthard


>== Auszüge aus der Nachricht von  Mario D vom 2016-02-23 09:21:
> In my ~/.vim/ftplugin/tex.vim I defined the following:
> 
> function! Set_PDF()
>     let g:Tex_DefaultTargetFormat = 'pdf'
>     let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_CompileRule_dvi = 'pdflatex --synctex=1
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_ViewRule_pdf =  'okular --unique 2>/dev/null 1>&2 '
>     let g:Tex_ViewRule_dvi = 'okular --unique 2>/dev/null 1>&2 '
>     let g:Tex_MultipleCompileFormats = ''
> endfunction
> 
> function! Set_LaTeX()
>     let g:Tex_DefaultTargetFormat = 'dvi'
>     let g:Tex_CompileRule_dvi = 'latex -src-specials
> -interaction=nonstopmode -file-line-error-style $*'
>     let g:Tex_ViewRule_dvi = 'xdvi 2>/dev/null 1>&2 '
>     let g:Tex_MultipleCompileFormats = ''
> endfunction
> 
> noremap <leader>latex :call Set_LaTeX()
> noremap <leader>pdf   :call Set_PDF()
> 
> My intention is the following: if I use ,pdf  (my leader is ,), then vim
> should be set up to produce pdf whereas if I use ,latex then it should
> produce dvi.
> 
> Now I open a latex file which should produce pdf, I call ,pdf and I compile
> using ,ll
> Everything is fine.
> My problem is when I try see the resulting pdf: if I use ,lv then what I
> get is the dvi file displayed by xdvi whereas if I use ,ls then I get again
> the dvi file but this time it is displayed by okular.
> What I would like is that by either I should get displayed the pdf by means
> of okular.
> What am I doing wrong?
> 
> Thanks
>    In my ~/.vim/ftplugin/tex.vim I defined the following:
> 
>    function! Set_PDF()
>        let g:Tex_DefaultTargetFormat = 'pdf'
>        let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1
>    -interaction=nonstopmode -file-line-error-style $*'
>        let g:Tex_CompileRule_dvi = 'pdflatex --synctex=1
>    -interaction=nonstopmode -file-line-error-style $*'
>        let g:Tex_ViewRule_pdf =  'okular --unique 2>/dev/null 1>&2 '
>        let g:Tex_ViewRule_dvi = 'okular --unique 2>/dev/null 1>&2 '
>        let g:Tex_MultipleCompileFormats = ''
>    endfunction
> 
>    function! Set_LaTeX()
>        let g:Tex_DefaultTargetFormat = 'dvi'
>        let g:Tex_CompileRule_dvi = 'latex -src-specials
>    -interaction=nonstopmode -file-line-error-style $*'
>        let g:Tex_ViewRule_dvi = 'xdvi 2>/dev/null 1>&2 '
>        let g:Tex_MultipleCompileFormats = ''
>    endfunction
> 
>    noremap <leader>latex :call Set_LaTeX()
>    noremap <leader>pdf   :call Set_PDF()
> 
>    My intention is the following: if I use ,pdf  (my leader is ,), then vim
>    should be set up to produce pdf whereas if I use ,latex then it should
>    produce dvi.
> 
>    Now I open a latex file which should produce pdf, I call ,pdf and I
>    compile using ,ll
>    Everything is fine.
>    My problem is when I try see the resulting pdf: if I use ,lv then what I
>    get is the dvi file displayed by xdvi whereas if I use ,ls then I get
>    again the dvi file but this time it is displayed by okular.
>    What I would like is that by either I should get displayed the pdf by
>    means of okular.
>    What am I doing wrong?
> 
>    Thanks

-- 

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

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

[Vim-latex-devel] Bug: ref completion in muli-file documents not working correctly

[Felix K. <fe...@bi...>]

Hi,

there is a bug in the vim-latex-1.8.23-20141116.812 
<https://sourceforge.net/projects/vim-latex/files/snapshots/vim-latex-1.8.23-20141116.812-gitd0f31c9.tar.gz/download> 
snaphot of the LaTeX Suite preventing the autocompletion of labels in 
multi-document latex projects. I found the solution to this issue here:

     http://ubuntuforums.org/showthread.php?t=2139228

Labels in \input'ed documents are recognized only if the \input command 
starts at the beginning of the line in the master file, i.e. with a 
child file world_doc.tex

%%%%%%%%%%%%%%%%%%%%%%%%
% % % world_doc.tex
\section{World section} \label{world_label}
world!
%%%%%%%%%%%%%%%%%%%%%%%%

and a master file main.tex

%%%%%%%%%%%%%%%%%%%%%%%%
% % % main.tex:
\documentclass{scrartcl}

\begin{document}
\input{world_doc}      % no whitespace before input

\section{Hello}
     Hello, section \ref{<+PRESS F9 HERE+>}.
\end{document}
%%%%%%%%%%%%%%%%%%%%%%%%

pressing F9 in the marked place opens the __OUTLINE__ window with label 
"world_label" as expected, but when changing the file to

%%%%%%%%%%%%%%%%%%%%%%%%
% % % main.tex:
\documentclass{scrartcl}

\begin{document}
     \input{world_doc}      % added whitespace here

\section{Hello}
     Hello, section \ref{<+PRESS F9 HERE+>}.
\end{document}
%%%%%%%%%%%%%%%%%%%%%%%%

the __OUTLINE__ window will not display the label anymore. It this a 
known issue? Since it is desirable to have leading whitespace before 
commands to allow a visual structuring of the document, it would be 
great if this could be fixed. It took me quite some time to figure out 
where the problem lies, and I assume that others have the same issue.

Regards,
Felix Kuehnl

[Vim-latex-devel] Viewing pdf

[Mario D <eg...@gm...>]

In my ~/.vim/ftplugin/tex.vim I defined the following:

function! Set_PDF()
    let g:Tex_DefaultTargetFormat = 'pdf'
    let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1
-interaction=nonstopmode -file-line-error-style $*'
    let g:Tex_CompileRule_dvi = 'pdflatex --synctex=1
-interaction=nonstopmode -file-line-error-style $*'
    let g:Tex_ViewRule_pdf =  'okular --unique 2>/dev/null 1>&2 '
    let g:Tex_ViewRule_dvi = 'okular --unique 2>/dev/null 1>&2 '
    let g:Tex_MultipleCompileFormats = ''
endfunction

function! Set_LaTeX()
    let g:Tex_DefaultTargetFormat = 'dvi'
    let g:Tex_CompileRule_dvi = 'latex -src-specials
-interaction=nonstopmode -file-line-error-style $*'
    let g:Tex_ViewRule_dvi = 'xdvi 2>/dev/null 1>&2 '
    let g:Tex_MultipleCompileFormats = ''
endfunction

noremap <leader>latex :call Set_LaTeX()
noremap <leader>pdf   :call Set_PDF()

My intention is the following: if I use ,pdf  (my leader is ,), then vim
should be set up to produce pdf whereas if I use ,latex then it should
produce dvi.

Now I open a latex file which should produce pdf, I call ,pdf and I compile
using ,ll
Everything is fine.
My problem is when I try see the resulting pdf: if I use ,lv then what I
get is the dvi file displayed by xdvi whereas if I use ,ls then I get again
the dvi file but this time it is displayed by okular.
What I would like is that by either I should get displayed the pdf by means
of okular.
What am I doing wrong?

Thanks

[Vim-latex-devel] Mac OSX configuration

[Ruben Di B. <rub...@gm...>]

Hello,

I'm setting up the environment on my OSX 10.11.3 machine to write agily in
LaTex.

The problems I'm facing now are related to the keys. F5 (Typing FN+F5) and
F9 (FN+F9) are not working in vim (I'm using vim on the terminal). It just
prints "<F5>" or "<F9">.
I installed the plugin with Vundle putting 'Plugin
LaTeX-Suite-aka-Vim-LaTeX' in the ~/.vimrc.

There's someone that is using vim-latex on OSX that can share his
configuration?

-- 
                                 _..,..,..
                                 .'
                             _-.'
\                          _."
 \                _._  .-'
  \          _.-'"   |
   \      .-'        |
    \   .'           |
     \_/             |
                     |
         R  D  B     |
                     |
     _               |
    / \              |
   /   '-,           |
  /       "._        |
 /           "._     |
/                "-._|
                      '-._
                          '-_
                             "_
                               '-.
                                  '.,.,..,.

[Vim-latex-devel] g:Tex_GotoError=0 has no effect

[Luke M. <Luk...@al...>]

Hi - I have a multi-file project with warnings, so the default behavior of
jumping to the first error is annoying. I see there's a setting, but it
seems to have no effect. I added "let g:Tex_GotoError=0" to both .vimrc and
.vim/ftplugin/tex.vim. And still, when I compile from any file, it jumps to
the file with the first error (thus clearing my undo history even if I
Ctrl-O). Is there a bug? This is version 2014-1116.812-2 (from the Ubuntu
Wily repo).

- Luke

[Vim-latex-devel] On inverse and forward search

[Mario D <eg...@gm...>]

I have forward and inverse search working in vim with the following
settings:
compile rule is

let g:Tex_CompileRule_dvi = 'latex -src-specials -interaction=nonstopmode
-file-line-error-style $*'

in ~/.Xresources I have

xdvi.editor:            gvim  --servername xdvi --remote +%l %f

and I launch gvim with the command

gvim  --servername xdvi $@ file.tex


The point is that all of this works fine only within gvim: if I open
file.tex in the shell with vim I still have forward search but I do not
have inverse search any longer.
My question is: is there a way to define settings so that reverse search
works regardless of the fact that I use vim or gvim?

TIA

[Vim-latex-devel] Strange mapping behaviour

[Mario D <eg...@gm...>]

Hi,

I put these mappings in my tex.vim:

map <buffer> <F11> :w<cr><leader>ll
imap <buffer> <F11> <ESC>:w<cr><leader>lli
map <buffer> <F10> <leader>ls
imap <buffer> <F10> <ESC><leader>lsi
map <buffer> <F9> :w<cr><leader>ll<leader>ls
imap <buffer> <F9> <ESC>:w<cr><leader>ll<leader>lsi

I guess my intention is clear: both in normal and insert mode, when I hit
-) F11 I want to compile the file
-) F10 I want to perform forward search
-) F9 I want to do both: compile and forward search.

Well, the strange thing is that 5 out of 6 work but F9 in insert mode
doesn't!

I can't understand why...  :(

[Vim-latex-devel] RemoteOpen function error

[Q. G. <zn...@gm...>]

Hello,

I have the following error when I try to do inverse search in SumtraPDF.
[image: Inline image 1]

The RemoteOpen function calls Tex_Debug function, but cannot find that
function.


Best regards,
 Gao

Re: [Vim-latex-devel] bad indentation after commented lines

[Gaston A. <gar...@sl...>]

Thank you for your response, but without parenthesis got the same problem

\begin{align}
   \sqrt{R^{2}} &= \omega_{\rm a} L
   %\left(\frac{1}{\omega_{\rm a} C}\right)^{2} &= 2 \frac{L}{C}-R^{2} \\
   \end{align}

Gastón


El 05/11/15 a las 16:49, Renliang Gu escibió:
> It is not due to the comment, but the parenthesis that you have above 
> the commented line.
>
> 顾任亮 (Renliang Gu)
>
> On Thu, Nov 5, 2015 at 1:09 PM, Gaston Araguas <gar...@sl... 
> <mailto:gar...@sl...>> wrote:
>
>     Hello all,
>
>     i'm having problems with automatic indentation. The indentation
>     does not
>     perform well if a commented line appears just above an \end command.
>     here is an example
>
>     \begin{align}
>        \sqrt{R^{2}+\left(\omega_{\rm a} L-\frac{1}{\omega_{\rm a}
>     C}\right)^{2}} &= \omega_{\rm a} L
>        %\left(\frac{1}{\omega_{\rm a} C}\right)^{2} &= 2
>     \frac{L}{C}-R^{2} \\
>        \end{align}
>        despejamos $\omega_{\rm a}$
>        \begin{align}
>          \omega_{\rm a} &= \frac{1}{C\sqrt{2 \frac{L}{C}-R^{2}}}.
>          \label{ec:res_frec_L}
>        \end{align}
>
>
>     in my .vimrc i have
>
>     filetype on
>     filetype plugin indent on
>     let g:tex_flavor = "latex"
>
>     thank you,
>     Gastón
>
>     ------------------------------------------------------------------------------
>     _______________________________________________
>     Vim-latex-devel mailing list
>     Vim...@li...
>     <mailto:Vim...@li...>
>     https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

Re: [Vim-latex-devel] bad indentation after commented lines

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

It is not due to the comment, but the parenthesis that you have above the
commented line.

顾任亮(Renliang Gu)

On Thu, Nov 5, 2015 at 1:09 PM, Gaston Araguas <gar...@sl...> wrote:

> Hello all,
>
> i'm having problems with automatic indentation. The indentation does not
> perform well if a commented line appears just above an \end command.
> here is an example
>
> \begin{align}
>    \sqrt{R^{2}+\left(\omega_{\rm a} L-\frac{1}{\omega_{\rm a}
> C}\right)^{2}} &= \omega_{\rm a} L
>    %\left(\frac{1}{\omega_{\rm a} C}\right)^{2} &= 2 \frac{L}{C}-R^{2} \\
>    \end{align}
>    despejamos $\omega_{\rm a}$
>    \begin{align}
>      \omega_{\rm a} &= \frac{1}{C\sqrt{2 \frac{L}{C}-R^{2}}}.
>      \label{ec:res_frec_L}
>    \end{align}
>
>
> in my .vimrc i have
>
> filetype on
> filetype plugin indent on
> let g:tex_flavor = "latex"
>
> thank you,
> Gastón
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] bad indentation after commented lines

[Gaston A. <gar...@sl...>]

Hello all,

i'm having problems with automatic indentation. The indentation does not 
perform well if a commented line appears just above an \end command.
here is an example

\begin{align}
   \sqrt{R^{2}+\left(\omega_{\rm a} L-\frac{1}{\omega_{\rm a} 
C}\right)^{2}} &= \omega_{\rm a} L
   %\left(\frac{1}{\omega_{\rm a} C}\right)^{2} &= 2 \frac{L}{C}-R^{2} \\
   \end{align}
   despejamos $\omega_{\rm a}$
   \begin{align}
     \omega_{\rm a} &= \frac{1}{C\sqrt{2 \frac{L}{C}-R^{2}}}.
     \label{ec:res_frec_L}
   \end{align}


in my .vimrc i have

filetype on
filetype plugin indent on
let g:tex_flavor = "latex"

thank you,
Gastón

Re: [Vim-latex-devel] Customizing latex command

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

Hi Mario,


2015-09-24 11:38 GMT+02:00 Mario D <eg...@gm...>:
> Hi all,
>
> [...]
>
> So, I want to to compile with ",ll" BOTH in normal mode and insert mode. Is
> it possible? How?

You can add your own map. I have remapped <leader>ll to F12 both in
normal and insert mode.
See here: https://github.com/montefra/.vim/blob/vim-plug/ftplugin/tex.vim#L24.
You might be able to ``imap <leader>ll ...``

Ciao,

Fra

>
> One last question: my vim-latex version is 1.8.23-20130116.788. I see that
> the latest is
> 1.8.23-20141116.812.
> Given that I have no issues with my version, is the upgrade worth or
> suggested?
>
> Thank you very much
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] Customizing latex command

[Mario D <eg...@gm...>]

Hi all,

since I use an italian keyboard and the character "`" is a bit
uncomfortable, I changed the TexLeader to ",". No problem for this.

What I am not able to obtain is the following: I would like to have a
shortcut for triggering latex even in insert mode, not only normal mode.
And it would be nice if this shortcut could be the very same ",ll".

So, I want to to compile with ",ll" BOTH in normal mode and insert mode. Is
it possible? How?

One last question: my vim-latex version is 1.8.23-20130116.788. I see that
the latest is
1.8.23-20141116.812.
Given that I have no issues with my version, is the upgrade worth or
suggested?

Thank you very much

Re: [Vim-latex-devel] A Bug in Smart Quote Feature in vim 7.4.640

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

Dear Mani,
may you post your vimrc? to be sure, do you have any  thing in your
vimrc that may effect this behaviour?
Regards,
Rudra
On Thu, 2015-08-06 at 12:19 +0200, Mani Bastani Parizi wrote:
> Dear Rudra and Filip,
> 
> Thank you very much for your replies.
> 
> I tried the newer version (gerw/vim-latex-suite) but didn't solve my
> problem either :-(!
> 
> Best,
> Mani
> 
> 
> On Thu, Aug 6, 2015 at 12:03 PM,
> <vim...@li...> wrote:
> > Date: Thu, 6 Aug 2015 11:03:17 +0100
> > From: Rudra Banerjee <bnr...@li...>
> > Subject: Re: [Vim-latex-devel] A Bug in Smart Quote Feature in vim
> >         7.4.640
> > To: vim...@li...
> > Message-ID: <BLU...@ph...>
> > Content-Type: text/plain; charset="UTF-8"
> > 
> > Oops...sorry. I pressed send button too early.
> > I was also facing the problem with same distro, same vim as the OP.
> > But with the recent update of the plugin (I use Vundle for that), 
> > the
> > problem is solved.
> > I am using 'gerw/vim-latex-suite'  which is "This repo contains an
> > improved version of latex-suite (
> > http://sourceforge.net/projects/vim-latex/)"
> > Hope this helps.
> > Regards,
> > Rudra
> > On Thu, 2015-08-06 at 10:57 +0100, Rudra Banerjee wrote:
> > > I am also facing the problem with same distro, same vim as the 
> > > OP.
> > > On Thu, 2015-08-06 at 10:05 +0200, Filip Kadlec wrote:
> > > > Hello,
> > > >   unfortunately, I don't have a solution to your problem, I 
> > > > just
> > > > can
> > > > state
> > > > that smart quotes work in my vim-latex installation. After 
> > > > hitting
> > > > "
> > > > twice, I get ``''<++> as expected. Rather than vim-version, I 
> > > > think
> > > > it is
> > > > a matter of version of the vim-latex suite; mine comes from the
> > > > OpenSuSE
> > > > 13.2 distribution.
> > > >   Unfortunately, it seems to me that some of such minor
> > > > functionalities
> > > > fail in some cases, depending on distribution, and are quite 
> > > > hard
> > > > to
> > > > track
> > > > if one does not understand quite deeply how vim-latex works.
> > > > Otherwise,
> > > > vim-latex is a nice piece of work.
> > > > 
> > > > Best,
> > > >     Filip
> > > > 
> > > > On Wed, 5 Aug 2015, Mani Bastani Parizi wrote:
> > > > 
> > > > > Date: Wed, 5 Aug 2015 15:14:57
> > > > > From: Mani Bastani Parizi <m.b...@gm...>
> > > > > To: vim...@li...
> > > > > Subject: [Vim-latex-devel] A Bug in Smart Quote Feature in 
> > > > > vim
> > > > > 7.4.640
> > > > > 
> > > > > Dear Developers,
> > > > > 
> > > > > The Smart Quote feature seems not to be working properly in 
> > > > > vim
> > > > > 7.4.640 (on Fedora 22).
> > > > > 
> > > > > Instead of replacing double-quote (") with `` and '' 
> > > > > accordingly,
> > > > > it
> > > > > is replaced with "``" and "''" (i.e., the corresponding two 
> > > > > back
> > > > > -ticks
> > > > > or two apostrophes are enclosed in an extra pair of double
> > > > > -quotes
> > > > > themselves).
> > > > > 
> > > > > I was wondering if there exists a solution for the issue.
> > > > > 
> > > > > Thanks,
> > > > > Mani
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > 
> > > > --
> > > > Upozorneni: Neni-li v teto zprave vyslovne uvedeno jinak, neni 
> > > > tato
> > > > e
> > > > -mailova zprava navrhem na uzavreni smlouvy ani prijetim 
> > > > pripadneho
> > > > navrhu na uzavreni smlouvy a nezaklada predsmluvni odpovednost 
> > > > FZU
> > > > AV
> > > > CR, v. v. i.
> > > > Disclaimer: If not expressly stated otherwise, this e-mail 
> > > > message
> > > > cannot be considered as a proposal to conclude a contract, 
> > > > neither
> > > > the acceptance of a proposal to conclude a contract, nor does 
> > > > it
> > > > create any pre-contractual liability on the part of FZU AV CR, 
> > > > v.
> > > > v.
> > > > i.
> > > > 
> > > > 
> > > > ---------------------------------------------------------------
> > > > ----
> > > > --
> > > > ---------
> > > > _______________________________________________
> > > > Vim-latex-devel mailing list
> > > > Vim...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> > > 
> > > -----------------------------------------------------------------
> > > ----
> > > ---------
> > > _______________________________________________
> > > Vim-latex-devel mailing list
> > > Vim...@li...
> > > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> > 
> > 
> > 
> > ------------------------------
> > 
> > -------------------------------------------------------------------
> > -----------
> > 
> > 
> > ------------------------------
> > 
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> > 
> > 
> > End of Vim-latex-devel Digest, Vol 91, Issue 1
> > **********************************************
> 
> 
>