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

Re: [Vim-latex-devel] show warnings after compiling

[Andreas G. <and...@tu...>]

Hello,

I figured out that the missing of the undefined citation warnings 
depends on my used bibliography package. I use the package natbib which 
produces a warning starting with "Package natbib Warning: Citation ... 
on page ... undefined". This warning is not shown by the latex-suite. If 
I disable natbib the warning looks like "Latex Warning: Citation ...." 
and this warning is recognised an display by the latex-suite.

Is there a way the make the latex-suite sensitive for these kind of 
warnings (e.g. editing .vim/compiler/tex.vim)?

Cheers

Andreas

On 01/17/2013 05:59 PM, Andreas Groh wrote:
> Hello list,
>
> I am new to the vim latex-suite. I set everything up and it works fine
> so far. But I can not figure out how to show latex warning after
> compiling the document using \ll. If there are errors they are shown in
> thw "Quickfix list" with a preview window below. But in the case of
> warnings (e.g. undefined references) I end up in the normal vim window
> without having the warnings shown. I set "TCLevel strict" which sets
> Tex_IgnoreLevel to 0, but it doesn't change anything.
>
> Any ideas what I am doing wrong? Or is it the normal way that warnings
> are not shown? Any help is appreciated.
>
> Thanks and best regards.
>
> Andreas
>

-- 
------------------------------------------------------------------------
Andreas Groh                       phone : +49-351-463.34974
Institut fuer Planetare Geodaesie  fax   : +49-351-463.37063
Technische Universitaet Dresden    email : and...@tu...
D-01062 Dresden, Germany           web   : tpg.geo.tu-dresden.de
------------------------------------------------------------------------

[Vim-latex-devel] (no subject)

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

http://www.kstar.de/images/bestways.php





*
ahmet nurlu

Re: [Vim-latex-devel] show warnings after compiling

[Andreas G. <and...@tu...>]

Dear Alessandro,

Thanks for the hint. I will give it a try and report the result.

Andreas

On 01/17/2013 08:12 PM, Alessandro Pezzoni wrote:
> 2013/1/17 Alessandro Pezzoni <ale...@la...>:
>> You could try using something like 'rubber' [1], which is a latex
>> wrapper that is able to "sanitize" error and warning messages for vim,
>> i.e. that can print them on a single line. This should also fix the
>> annoying issue of vim opening an .aux file upon compilation errors.
>
> Sorry for double-posting, but I forgot to say that to use a different
> compiler is easy as changing a vim variable, e.g. for dvi or pdf
> output:
>
> let g:Tex_CompileRule_dvi = "rubber -s $*"
> let g:Tex_CompileRule_pdf = "rubber -s --pdf $*"
>
> The '-s' option is there to tell it to display one error message per line.
>
> Alessandro
>

-- 
------------------------------------------------------------------------
Andreas Groh                       phone : +49-351-463.34974
Institut fuer Planetare Geodaesie  fax   : +49-351-463.37063
Technische Universitaet Dresden    email : and...@tu...
D-01062 Dresden, Germany           web   : tpg.geo.tu-dresden.de
------------------------------------------------------------------------

Re: [Vim-latex-devel] show warnings after compiling

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

2013/1/17 Alessandro Pezzoni <ale...@la...>:
> You could try using something like 'rubber' [1], which is a latex
> wrapper that is able to "sanitize" error and warning messages for vim,
> i.e. that can print them on a single line. This should also fix the
> annoying issue of vim opening an .aux file upon compilation errors.

Sorry for double-posting, but I forgot to say that to use a different
compiler is easy as changing a vim variable, e.g. for dvi or pdf
output:

let g:Tex_CompileRule_dvi = "rubber -s $*"
let g:Tex_CompileRule_pdf = "rubber -s --pdf $*"

The '-s' option is there to tell it to display one error message per line.

Alessandro

Re: [Vim-latex-devel] show warnings after compiling

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

> On 01/17/2013 12:41 PM, Andreas Groh wrote:
>> Hello,
>>
>> thanks for your reply. I also have let g:Tex_IgnoreLevel=0 in my
>> .vimrc. As far as I understood the TCLevel command is just a short cut
>> for let g:Tex_IgnoreLevel=x to be used from within vim. However, the
>> warnings are not shown. In my case the warnings are mainly due to
>> undefined citations.
>>
>> Meanwhile I started working on another latex project without undefined
>> citations. In this case the warnings for underfull boxes etc. are
>> shown. That is strange. If I include an undefined citation the
>> corresponding warning is also not shown.
>>
>> Why is that? Are the warnings for undefined citations treated in a
>> different way?

Well, I'm not sure about why the warnings for one of your projects get
displayed and those for the other do not, but vim's quickfix mode is
known to not play nicely with with latex, since it is unable to parse
multi-linear error messages (or warnings).
You could try using something like 'rubber' [1], which is a latex
wrapper that is able to "sanitize" error and warning messages for vim,
i.e. that can print them on a single line. This should also fix the
annoying issue of vim opening an .aux file upon compilation errors.

Cheers,
Alessandro

[1] https://launchpad.net/rubber/

Re: [Vim-latex-devel] show warnings after compiling

[Peng S. <sha...@gm...>]

On 01/17/2013 01:00 PM, Andreas Groh wrote:
> Hello Peng Shao,
>
> Sorry, my last reply was only to you and not to the list.
It is fine, I very often forgot to reply to the list as well :)
> I tried your settings but it doesn't change the situation. The problem
> is that the undefined citation warnings are not shown  (not references,
> like I wrote in my initial post, sorry for that). If I include a
> reference which is not defined the warning is correctly shown. But even
> for let g:Tex_IgnoreLevel = 0 the undefined citation warnings are still
> absent.
>
> Best
> Andreas
Okay I think I understand your situation: you want latex-suite to raise 
the warning which was originally undefined.
In this case I am sorry since I don't think I can help you very much... 
I have never encountered an issue like this as what I
needed the most was to ignore some undesired warnings.

Anyway, could you please send me a sample of latex file and tell me what 
kind of warning you want to see, so that I
may give it a try? But don't expect too much...

-- 
Peng Shao

Re: [Vim-latex-devel] show warnings after compiling

[Andreas G. <and...@tu...>]

Hello Peng Shao,

Sorry, my last reply was only to you and not to the list.

I tried your settings but it doesn't change the situation. The problem 
is that the undefined citation warnings are not shown  (not references, 
like I wrote in my initial post, sorry for that). If I include a 
reference which is not defined the warning is correctly shown. But even 
for let g:Tex_IgnoreLevel = 0 the undefined citation warnings are still 
absent.

Best

Andreas

On 01/17/2013 06:48 PM, Peng Shao wrote:
>
> On 01/17/2013 12:41 PM, Andreas Groh wrote:
>> Hello,
>>
>> thanks for your reply. I also have let g:Tex_IgnoreLevel=0 in my
>> .vimrc. As far as I understood the TCLevel command is just a short cut
>> for let g:Tex_IgnoreLevel=x to be used from within vim. However, the
>> warnings are not shown. In my case the warnings are mainly due to
>> undefined citations.
>>
>> Meanwhile I started working on another latex project without undefined
>> citations. In this case the warnings for underfull boxes etc. are
>> shown. That is strange. If I include an undefined citation the
>> corresponding warning is also not shown.
>>
>> Why is that? Are the warnings for undefined citations treated in a
>> different way?
>>
>> Cheers.
>>
>> Andreas
>>
> Dear Andreas,
>
> Here is the warning-level-related settings in my vimrc
>
>
> let g:Tex_IgnoredWarnings =
> \"Underfull\n".
> \"Overfull\n".
> \"specifier changed to\n".
> \"You have requested\n".
> \"Missing number, treated as zero.\n".
> \"Citation %.%# undefined\n".
> \"Unused\n".
> \"LaTeX Font Warning:\n"
> \"There were undefined references\n".
> " This number N indicates that latex-suite should ignore the first N of
> the above.
> let g:Tex_IgnoreLevel = 8
>
> Would you please try to see if it can detect the undefined references?
>
> Btw, I cc this mail to the maillist so other people may also see it,
> just in case in future someone else ran into a similar problem.
>

-- 
------------------------------------------------------------------------
Andreas Groh                       phone : +49-351-463.34974
Institut fuer Planetare Geodaesie  fax   : +49-351-463.37063
Technische Universitaet Dresden    email : and...@tu...
D-01062 Dresden, Germany           web   : tpg.geo.tu-dresden.de
------------------------------------------------------------------------

Re: [Vim-latex-devel] show warnings after compiling

[Peng S. <sha...@gm...>]

On 01/17/2013 12:41 PM, Andreas Groh wrote:
> Hello,
>
> thanks for your reply. I also have let g:Tex_IgnoreLevel=0 in my 
> .vimrc. As far as I understood the TCLevel command is just a short cut 
> for let g:Tex_IgnoreLevel=x to be used from within vim. However, the 
> warnings are not shown. In my case the warnings are mainly due to 
> undefined citations.
>
> Meanwhile I started working on another latex project without undefined 
> citations. In this case the warnings for underfull boxes etc. are 
> shown. That is strange. If I include an undefined citation the 
> corresponding warning is also not shown.
>
> Why is that? Are the warnings for undefined citations treated in a 
> different way?
>
> Cheers.
>
> Andreas
>
Dear Andreas,

Here is the warning-level-related settings in my vimrc


let g:Tex_IgnoredWarnings =
\"Underfull\n".
\"Overfull\n".
\"specifier changed to\n".
\"You have requested\n".
\"Missing number, treated as zero.\n".
\"Citation %.%# undefined\n".
\"Unused\n".
\"LaTeX Font Warning:\n"
\"There were undefined references\n".
" This number N indicates that latex-suite should ignore the first N of 
the above.
let g:Tex_IgnoreLevel = 8

Would you please try to see if it can detect the undefined references?

Btw, I cc this mail to the maillist so other people may also see it, 
just in case in future someone else ran into a similar problem.

-- 
Peng Shao

Re: [Vim-latex-devel] show warnings after compiling

[Peng S. <sha...@gm...>]

On 01/17/2013 11:59 AM, Andreas Groh wrote:
> Hello list,
>
> I am new to the vim latex-suite. I set everything up and it works fine
> so far. But I can not figure out how to show latex warning after
> compiling the document using \ll. If there are errors they are shown in
> thw "Quickfix list" with a preview window below. But in the case of
> warnings (e.g. undefined references) I end up in the normal vim window
> without having the warnings shown. I set "TCLevel strict" which sets
> Tex_IgnoreLevel to 0, but it doesn't change anything.
>
> Any ideas what I am doing wrong? Or is it the normal way that warnings
> are not shown? Any help is appreciated.
>
> Thanks and best regards.
>
> Andreas
>

Dear Andreas,

I just tested on my machine x86_64 arch linux with vim 7.3.754 and what 
I needed to do was simply putting

let g:Tex_IgnoreLevel = 0

in my .vimrc then the undefined references will be listed after 
compilation. I didn't have to use TCLevel at all.

Did you try the line I mentioned?

-- 
Peng Shao

[Vim-latex-devel] show warnings after compiling

[Andreas G. <and...@tu...>]

Hello list,

I am new to the vim latex-suite. I set everything up and it works fine 
so far. But I can not figure out how to show latex warning after 
compiling the document using \ll. If there are errors they are shown in 
thw "Quickfix list" with a preview window below. But in the case of 
warnings (e.g. undefined references) I end up in the normal vim window 
without having the warnings shown. I set "TCLevel strict" which sets 
Tex_IgnoreLevel to 0, but it doesn't change anything.

Any ideas what I am doing wrong? Or is it the normal way that warnings 
are not shown? Any help is appreciated.

Thanks and best regards.

Andreas

-- 
------------------------------------------------------------------------
Andreas Groh                       phone : +49-351-463.34974
Institut fuer Planetare Geodaesie  fax   : +49-351-463.37063
Technische Universitaet Dresden    email : and...@tu...
D-01062 Dresden, Germany           web   : tpg.geo.tu-dresden.de
------------------------------------------------------------------------

[Vim-latex-devel] GVim crashes with Latex files.

[J S <drs...@go...>]

Hi guys,

I would like to report a strange bug in vim-latex. The issue was asked on
stackexchange here:
http://stackoverflow.com/questions/7034254/plugin-vim-latex-crashing-gvim-on-startup

I found out after a little testing that the plugin crashes vim as soon as
it encounters a \begin{...} statement*. *A tex file with the
begin{} statement commented out is not crashing!*
*
Hope this helps pinpoint the culprit...
Thanks,
John*
*
-- 
http://dynamic.xkcd.com/random/comic/

Re: [Vim-latex-devel] Problems with templates

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

2012/12/29 David Woodfall <da...@da...>:
> Original:
>
>    7 \usepackage[strict=true, style=british]{csquotes}
>   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Textclass specific LaTeX commands.
>   10 \newif\ifletterclosed
>   11 \AtEndDocument{\ifletterclosed\else\end{letter}\fi}
>   12 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% User specified LaTeX commands.
>   13 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>   14 %% Here you can modify the layout of your letter
>   15 %% Have a look at the KOMA script documentation
>   16 %% for details. Most commands are commented out
>   17 %% here (i.e. we use default settings)
>   18 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>   19 %% Load an *.lco style file (see KOMA documentation)
>   20 \LoadLetterOption{DIN}%
>
> The result:
>
>    7 \usepackage[strict=true, style=british]{csquotes}
>    8 0
>    9 %% Here you can modify the layout of your letter
>   10 %% Have a look at the KOMA script documentation
>   11 %% for details. Most commands are commented out
>   12 %% here (i.e. we use default settings)
>   13 0
>   14 %% Load an *.lco style file (see KOMA documentation)
>   15 \LoadLetterOption{DIN}%
>
> It seems to have deleted some lines and replaced some with '0'.

Please, try deleting some comment signs, e.g. using something like:

\usepackage[strict=true, style=british]{csquotes}
%% Textclass specific LaTeX commands.
\newif\ifletterclosed
\AtEndDocument{\ifletterclosed\else\end{letter}\fi}
%% User specified LaTeX commands.
%%%
% Here you can modify the layout of your letter
% Have a look at the KOMA script documentation
% for details. Most commands are commented out
% here (i.e. we use default settings)
%%%
% Load an *.lco style file (see KOMA documentation)
\LoadLetterOption{DIN}%

This since the missing lines are mostly those with most '%' in them.
This is not really a solution, but it can help pinpoint the issue.

Alessandro

Re: [Vim-latex-devel] Problems with templates

[David W. <da...@da...>]

On (19:36 28/12/12), David Woodfall <da...@da...> put forth the proposition:
>On (13:35 28/12/12), Ruthard Baudach <rut...@we...> put forth the proposition:
>>>== Auszüge aus der Nachricht von  David Woodfall vom 2012-12-26 01:59:
>>> I'm having a problem that when I choose a template it ends up with
>>> several lines at the top snipped off and the spacing/indentation is
>>> messed up too.
>>I've had the same observation with my templates. If you analyze the generic templates -
>>they all start with some lines producing a file header, and the first
>>line -- only the first one -- is stripped. I think this line is for a
>>comment on the template file that is not part of the file. Thus, my
>>custom templates start with
>>
>>%
>>
>>as first line.
>>
>>The latter is a problem of vim when you do pasting with automatic
>>indentation turned on (as is default with most filetype plugins) -- the
>>indentations of the pasted text and the autoindent induced indentations
>>sum up, messing the format.
>>
>>see
>>  :help paste
>>for detail,
>>use
>>  :set paste
>>before pasting text
>>and
>>  :set nopaste
>>to return to normal behaviour.
>
>Strangely, the problem has gone. I had tried :set paste and turning
>off autoindent, but it didn't seem to make any difference. Obviously
>something I did fixed it, but I don't know what...

I spoke too soon I think. Something strange is going on here. Compare
my koma-letter template original to what gets pasted into vim:

Original:

   7 \usepackage[strict=true, style=british]{csquotes}
  %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Textclass specific LaTeX commands.
  10 \newif\ifletterclosed
  11 \AtEndDocument{\ifletterclosed\else\end{letter}\fi}
  12 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% User specified LaTeX commands.
  13 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
  14 %% Here you can modify the layout of your letter
  15 %% Have a look at the KOMA script documentation
  16 %% for details. Most commands are commented out
  17 %% here (i.e. we use default settings)
  18 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
  19 %% Load an *.lco style file (see KOMA documentation)
  20 \LoadLetterOption{DIN}%

The result:

   7 \usepackage[strict=true, style=british]{csquotes}
   8 0
   9 %% Here you can modify the layout of your letter
  10 %% Have a look at the KOMA script documentation
  11 %% for details. Most commands are commented out
  12 %% here (i.e. we use default settings)
  13 0
  14 %% Load an *.lco style file (see KOMA documentation)
  15 \LoadLetterOption{DIN}%

It seems to have deleted some lines and replaced some with '0'.

Re: [Vim-latex-devel] Problems with templates

[David W. <da...@da...>]

On (13:35 28/12/12), Ruthard Baudach <rut...@we...> put forth the proposition:
>>== Auszüge aus der Nachricht von  David Woodfall vom 2012-12-26 01:59:
>> I'm having a problem that when I choose a template it ends up with
>> several lines at the top snipped off and the spacing/indentation is
>> messed up too.
>I've had the same observation with my templates. If you analyze the generic templates -
>they all start with some lines producing a file header, and the first
>line -- only the first one -- is stripped. I think this line is for a
>comment on the template file that is not part of the file. Thus, my
>custom templates start with
>
>%
>
>as first line.
>
>The latter is a problem of vim when you do pasting with automatic
>indentation turned on (as is default with most filetype plugins) -- the
>indentations of the pasted text and the autoindent induced indentations
>sum up, messing the format.
>
>see
>  :help paste
>for detail,
>use
>  :set paste
>before pasting text
>and
>  :set nopaste
>to return to normal behaviour.

Strangely, the problem has gone. I had tried :set paste and turning
off autoindent, but it didn't seem to make any difference. Obviously
something I did fixed it, but I don't know what...

Re: [Vim-latex-devel] Problems with templates

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

2012/12/28 Ruthard Baudach <rut...@we...>:
> use
>   :set paste
> before pasting text
> and
>   :set nopaste
> to return to normal behaviour.

You could also paste text from the system 'clipboard' using the '*'
buffer (in command mode):
"*p

For more information see the vim help pages on *registers* [1] and
*x11-selection* [2].

Alessandro

[1] http://vimdoc.sourceforge.net/htmldoc/change.html#registers
[2] http://vimdoc.sourceforge.net/htmldoc/gui_x11.html#x11-selection

Re: [Vim-latex-devel] Problems with templates

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

>== Auszüge aus der Nachricht von  David Woodfall vom 2012-12-26 01:59:
> I'm having a problem that when I choose a template it ends up with
> several lines at the top snipped off and the spacing/indentation is
> messed up too.
I've had the same observation with my templates. If you analyze the generic templates -
they all start with some lines producing a file header, and the first
line -- only the first one -- is stripped. I think this line is for a
comment on the template file that is not part of the file. Thus, my
custom templates start with

%

as first line.

The latter is a problem of vim when you do pasting with automatic
indentation turned on (as is default with most filetype plugins) -- the
indentations of the pasted text and the autoindent induced indentations
sum up, messing the format.

see
  :help paste
for detail,
use
  :set paste
before pasting text
and
  :set nopaste
to return to normal behaviour.

regards

Ruthard

[Vim-latex-devel] Problems with templates

[David W. <da...@da...>]

I'm having a problem that when I choose a template it ends up with
several lines at the top snipped off and the spacing/indentation is
messed up too.

Any help be great, thanks

[Vim-latex-devel] [ vim-latex-Bugs-3597243 ] Multiple file ref not quite working

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

Bugs item #3597243, was opened at 2012-12-18 09:25
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3597243&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: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Multiple file ref not quite working

Initial Comment:
I have created a multifile LaTeX document. I have included the main.tex.latexmain file and everything compiles correctly. However, when trying to using completion in eqref the only thing that comes up are the labels defined in main.tex. Any label that has been defined in an input file does not appear.

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

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

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

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

I've imported three changesets from Gerd's repo into the official 
repo... In particular:

1. Do not open a new buffer on \cite-completion
2. ref and cite completion with multiple windows.
3. Unified usage of s:winnum and s:pos in texviewer.vim

I imported 1 so that 2 and 3 would better apply (and 1 seemed like a 
good change). I made a minor modification to 2 and 3 to get them to 
apply without pulling in a lot of other changes from the repo.

(having said that, given the amount of effort Gerd has put into updating 
vim-latex for the 21st century, maybe we should look into pulling all of 
those patches into the official repo...)

--Ted

On 11/22/2012 08:01 AM, Ted Pavlic wrote:
> Those look like reasonable changes. I can import them into the official
> repo the next time I'm by my computer.
>
>    --Ted
>
> --
> Sent from the mobile device of Ted Pavlic.
> Please excuse typos, swypos, or very brief responses.
>
> On Nov 22, 2012 1:05 AM, "Gerd Wachsmuth"
> <ger...@ma...
> <mailto:ger...@ma...>> wrote:
>
>     Hi,
>
>     I can confirm that this issue remains fer the current official version
>     of latex-suite, but is fixed in my repo
>
>     https://github.com/gerw/vim-latex-suite
>
>     See in particular the commits
>
>     https://github.com/gerw/vim-latex-suite/commit/ae303c1f0df77583d685cf4b81cb6f8914ee070c
>     https://github.com/gerw/vim-latex-suite/commit/5971587dfc9389fd688b267cc90455b604c3b301
>
>     Best Regards
>     Gerd
>
>
>     On 11/21/2012 04:51 PM, Alan Grossfield wrote:
>      > Hi all,
>      >
>      > Just an update: I just updated to the current version on the web
>     site(vim-latex-1.8.23-20121116.784-git1c17b37) and can reproduce the
>     same behavior.
>      >
>      > Happy Thanksgiving,
>      >
>      > Alan
>      >
>      >
>
>
>     ------------------------------------------------------------------------------
>     Monitor your physical, virtual and cloud infrastructure from a single
>     web console. Get in-depth insight into apps, servers, databases, vmware,
>     SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>     Pricing starts from $795 for 25 servers or applications!
>     http://p.sf.net/sfu/zoho_dev2dev_nov
>     _______________________________________________
>     Vim-latex-devel mailing list
>     Vim...@li...
>     <mailto:Vim...@li...>
>     https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

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

Re: [Vim-latex-devel] project/file specific settings

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

Hi Alessandro,

thanks for the answer. I didn't think about it. I'll try that.

Cheers,
Francesco



2012/11/23 Alessandro Pezzoni <ale...@la...>

> 2012/11/23 Francesco Montesano <fra...@gm...>:
> > Is there some way to switch easely between latex and pdflatex or some
> > mechanism like localvimrc?
>
> As you probably are not switching between latex and pdflatex within
> the same project, you can simply put your project-specific settings in
> a master (.latexmain) file.
> For example, suppose that you generally use latex, but occasionally
> use pdflatex. Then you could leave the default settings as they are
> and, supposing that the main file of your pdflatex project is called
> "main.tex", create a new file called "main.tex.latexmain" in the same
> directory, putting your pdf-specific settings in it. You can put any
> kind of (latex-suite) project-specific settings in it as, quoting the
> latex-suite manual [1]:
>
> > If a master file is found, then Latex-Suite :sources the file.
> > Thus this file needs to contain valid Vim commands.
> > This file is typically used to store project specific settings.
>
> Regards,
> Alessandro
>
> [1]
> http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project-settings.html
>
>

Re: [Vim-latex-devel] project/file specific settings

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

2012/11/23 Francesco Montesano <fra...@gm...>:
> Is there some way to switch easely between latex and pdflatex or some
> mechanism like localvimrc?

As you probably are not switching between latex and pdflatex within
the same project, you can simply put your project-specific settings in
a master (.latexmain) file.
For example, suppose that you generally use latex, but occasionally
use pdflatex. Then you could leave the default settings as they are
and, supposing that the main file of your pdflatex project is called
"main.tex", create a new file called "main.tex.latexmain" in the same
directory, putting your pdf-specific settings in it. You can put any
kind of (latex-suite) project-specific settings in it as, quoting the
latex-suite manual [1]:

> If a master file is found, then Latex-Suite :sources the file.
> Thus this file needs to contain valid Vim commands.
> This file is typically used to store project specific settings.

Regards,
Alessandro

[1] http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project-settings.html

[Vim-latex-devel] project/file specific settings

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

Dear list,

this is the first time for me on this list.

I began to use vim-latex recently, and I like it very much.
I looked on the web for an easy way to switch between latex and pdflatex,
but I couldn't find any suggestion
My standard settings in ~/.vim/ftplugin/tex.vim are the following

"set targets
> let g:Tex_DefaultTargetFormat = 'dvi'
> let g:Tex_MultipleCompileFormats = 'dvi'
> let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
> "set compilation rules
> let g:Tex_CompileRule_dvi = 'latex -scr-special -synctex=1 $*'
> let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
> let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'


As now, if I want to use pdflatex, I modify the above file

> "set targets
> let g:Tex_DefaultTargetFormat = 'pdf'
> let g:Tex_MultipleCompileFormats = 'pdf'
> let g:Tex_FormatDependency_pdf = 'pdf'
> "set compilation rules
> let g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*'


This is very prone to errors if I work on more than a tex file at a time.

I've tried opening a tex file and insert the commands for pdf in the vim
command line (with the idea of save the session) without success [1].

I have found the plugin 'localvimrc' and created a local vimrc file in the
project directory with the pdf specifications, but didn't work as (I think)
the vimrc is loaded before the latex-vim files are.

Is there some way to switch easely between latex and pdflatex or some
mechanism like localvimrc?
An idea could be to put the default settings into ~/.vimrc (with a check
for a tex file) and the pdflatex one in a local vimrc, but to me is not
very neat and I don't know if it would work (if the latex-vim plugin is
loaded after the vimrc the g:Tex_* would be undefined)

Thanks in advance for any help or suggestion

Cheers,
Francesco


[1] error :
PDF mode expected, but DVI mode detected!\MessageBreak
    If you are using `latex', then call `pdflatex'.\MessageBreak
    Otherwise check and  correct the driver options.\MessageBreak
    Error recovery by switching to PDF mode%

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

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

Hi,

I can confirm that this issue remains fer the current official version 
of latex-suite, but is fixed in my repo

https://github.com/gerw/vim-latex-suite

See in particular the commits

https://github.com/gerw/vim-latex-suite/commit/ae303c1f0df77583d685cf4b81cb6f8914ee070c
https://github.com/gerw/vim-latex-suite/commit/5971587dfc9389fd688b267cc90455b604c3b301

Best Regards
Gerd


On 11/21/2012 04:51 PM, Alan Grossfield wrote:
> Hi all,
>
> Just an update: I just updated to the current version on the web site(vim-latex-1.8.23-20121116.784-git1c17b37) and can reproduce the same behavior.
>
> Happy Thanksgiving,
>
> Alan
>
>

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

[Alan G. <agr...@gm...>]

Hi all,

Just an update: I just updated to the current version on the web site(vim-latex-1.8.23-20121116.784-git1c17b37) and can reproduce the same behavior.

Happy Thanksgiving,

Alan


On Nov 21, 2012, at 6:57 AM, vim...@li... wrote:

> Send Vim-latex-devel mailing list submissions to
> 	vim...@li...
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> or, via email, send a message with subject or body 'help' to
> 	vim...@li...
> 
> You can reach the person managing the list at
> 	vim...@li...
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Vim-latex-devel digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: citation completion goes to wrong window with vsplit
>      (Gerd Wachsmuth)
>   2. Re: citation completion goes to wrong window with	vsplit
>      (Raniere Gaia Silva)
>   3. Re: citation completion goes to wrong window with vsplit
>      (Gerd Wachsmuth)
>   4. Re: citation completion goes to wrong window with	vsplit
>      (Alessandro Pezzoni)
>   5. Re: citation completion goes to wrong window with vsplit
>      (Till Maas)
>   6. Re: citation completion goes to wrong window with vsplit
>      (Gerd Wachsmuth)
>   7. question mark (yuejun yin)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 16 Nov 2012 13:57:09 +0100
> From: Gerd Wachsmuth <ger...@ma...>
> Subject: Re: [Vim-latex-devel] citation completion goes to wrong
> 	window with vsplit
> To: Alan Grossfield <agr...@gm...>
> Cc: vim...@li...
> Message-ID: <50A...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> For me this works as expected. Which version of latex-suite do you use?
> 
> On 11/16/2012 01:44 PM, Alan Grossfield wrote:
>> When I write longish latex documents, I often break them into pieces
>> (using \input) and keep multiple files open using gvim's vsplit
>> command. I've noticed that if I do this and use F9 to invoke
>> completion (for example on a \cite{}) the text is always inserted in
>> the leftmost window, regardless of which window I invoked the
>> completion from.  If the same file is opened in both windows, it
>> seems to work correctly, and it works correctly if the completion
>> command is invoked from the left side window.  It's only if the
>> command is invoked from a different window that this breaks.
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 16 Nov 2012 11:50:39 -0200
> From: Raniere Gaia Silva <r.g...@gm...>
> Subject: Re: [Vim-latex-devel] citation completion goes to wrong
> 	window with	vsplit
> To: Gerd Wachsmuth <ger...@ma...>
> Cc: Alan Grossfield <agr...@gm...>,
> 	vim...@li...
> Message-ID:
> 	<CANP2DtW6Kkpk8d6HjOyxUQ1VHiW0t=mejY3HBdQuHe=xA...@ma...>
> Content-Type: text/plain; charset=UTF-8
> 
> Gerd,
> sorry for the stupid question, but how I can get the latex-suite version?
> 
> Raniere
> 
> On Fri, Nov 16, 2012 at 10:57 AM, Gerd Wachsmuth
> <ger...@ma...> wrote:
>> For me this works as expected. Which version of latex-suite do you use?
>> 
>> On 11/16/2012 01:44 PM, Alan Grossfield wrote:
>>> When I write longish latex documents, I often break them into pieces
>>> (using \input) and keep multiple files open using gvim's vsplit
>>> command. I've noticed that if I do this and use F9 to invoke
>>> completion (for example on a \cite{}) the text is always inserted in
>>> the leftmost window, regardless of which window I invoked the
>>> completion from.  If the same file is opened in both windows, it
>>> seems to work correctly, and it works correctly if the completion
>>> command is invoked from the left side window.  It's only if the
>>> command is invoked from a different window that this breaks.
>> 
>> 
>> ------------------------------------------------------------------------------
>> Monitor your physical, virtual and cloud infrastructure from a single
>> web console. Get in-depth insight into apps, servers, databases, vmware,
>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>> Pricing starts from $795 for 25 servers or applications!
>> http://p.sf.net/sfu/zoho_dev2dev_nov
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 16 Nov 2012 15:08:19 +0100
> From: Gerd Wachsmuth <ger...@ma...>
> Subject: Re: [Vim-latex-devel] citation completion goes to wrong
> 	window with vsplit
> To: Raniere Gaia Silva <r.g...@gm...>
> Cc: Alan Grossfield <agr...@gm...>,
> 	vim...@li...
> Message-ID: <50A...@ma...>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> latex-suite does not have a version number (any more). So the question 
> reduces to "Where (and possibly when) did you get latex-suite from?".
> 
> Gerd
> 
> On 11/16/2012 02:50 PM, Raniere Gaia Silva wrote:
>> Gerd,
>> sorry for the stupid question, but how I can get the latex-suite version?
>> 
>> Raniere
>> 
>> On Fri, Nov 16, 2012 at 10:57 AM, Gerd Wachsmuth
>> <ger...@ma...> wrote:
>>> For me this works as expected. Which version of latex-suite do you use?
>>> 
>>> On 11/16/2012 01:44 PM, Alan Grossfield wrote:
>>>> When I write longish latex documents, I often break them into pieces
>>>> (using \input) and keep multiple files open using gvim's vsplit
>>>> command. I've noticed that if I do this and use F9 to invoke
>>>> completion (for example on a \cite{}) the text is always inserted in
>>>> the leftmost window, regardless of which window I invoked the
>>>> completion from.  If the same file is opened in both windows, it
>>>> seems to work correctly, and it works correctly if the completion
>>>> command is invoked from the left side window.  It's only if the
>>>> command is invoked from a different window that this breaks.
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Monitor your physical, virtual and cloud infrastructure from a single
>>> web console. Get in-depth insight into apps, servers, databases, vmware,
>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>> Pricing starts from $795 for 25 servers or applications!
>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 16 Nov 2012 18:02:20 +0100
> From: Alessandro Pezzoni <ale...@la...>
> Subject: Re: [Vim-latex-devel] citation completion goes to wrong
> 	window with	vsplit
> To: Gerd Wachsmuth <ger...@ma...>
> Cc: Alan Grossfield <agr...@gm...>,
> 	vim...@li...
> Message-ID:
> 	<CAJ...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> 2012/11/16 Gerd Wachsmuth <ger...@ma...>:
>> latex-suite does not have a version number (any more). So the question
>> reduces to "Where (and possibly when) did you get latex-suite from?".
> 
> Well, he did say "as distributed under Fedora"...
> By looking for Fedora packages I came to this page [1] where, while
> it's not really clear how to get a version info from there, I found a
> link to their build script repository for vim-latex. There is a
> changelog in the build script, from which I gather that they use git
> snapshots. In particular, the one corresponding to the version
> Grossfield is using is:
> 
> 1.8.23-6.20110214.1049-git089726a
> 
> So he has a git snapshot from a bit more than one year and a half ago.
> By the way, there is a newer entry (in the script for Fedora 17, the
> current stable release) dated 2012-01-25 saying that they updated that
> one to:
> 
> 1.8.23-7.20120125.768-git8b62284
> 
> I don't have any idea about the issue at hand, though.
> 
> Alessandro
> 
> [1] https://admin.fedoraproject.org/pkgdb/acls/name/vim-latex?_csrf_token=75695c0b53d7e1dbefa6eca5638f5eb988da891e
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Fri, 16 Nov 2012 20:06:18 +0100
> From: Till Maas <ope...@ti...>
> Subject: Re: [Vim-latex-devel] citation completion goes to wrong
> 	window with vsplit
> To: vim...@li...
> Message-ID: <201...@ge...valid>
> Content-Type: text/plain; charset=us-ascii
> 
> On Fri, Nov 16, 2012 at 06:02:20PM +0100, Alessandro Pezzoni wrote:
>> 2012/11/16 Gerd Wachsmuth <ger...@ma...>:
>>> latex-suite does not have a version number (any more). So the question
>>> reduces to "Where (and possibly when) did you get latex-suite from?".
> 
>> So he has a git snapshot from a bit more than one year and a half ago.
>> By the way, there is a newer entry (in the script for Fedora 17, the
>> current stable release) dated 2012-01-25 saying that they updated that
>> one to:
>> 
>> 1.8.23-7.20120125.768-git8b62284
> 
> There will be an updated package in the updates-testing repository soon:
> https://admin.fedoraproject.org/updates/vim-latex-1.8.23-9.20121116.784.git1c17b37.fc17
> 
> Regards
> Till
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Fri, 16 Nov 2012 22:10:44 +0100 (CET)
> From: Gerd Wachsmuth <ger...@ma...>
> Subject: Re: [Vim-latex-devel] citation completion goes to wrong
> 	window with vsplit
> To: vim...@li...
> Message-ID:
> 	<alp...@ga...>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
> 
> I think some bug still remains in the official latex-suite. I tested only 
> my version. When Tex_WordComplete is invoked, the window number is not 
> restored. See also
> 
> https://github.com/gerw/vim-latex-suite/commit/5971587dfc9389fd688b267cc90455b604c3b301
> 
> Best Regards
> Gerd
> 
> On Fri, 16 Nov 2012, Alessandro Pezzoni wrote:
> 
>> 2012/11/16 Gerd Wachsmuth <ger...@ma...>:
>>> latex-suite does not have a version number (any more). So the question
>>> reduces to "Where (and possibly when) did you get latex-suite from?".
>> 
>> Well, he did say "as distributed under Fedora"...
>> By looking for Fedora packages I came to this page [1] where, while
>> it's not really clear how to get a version info from there, I found a
>> link to their build script repository for vim-latex. There is a
>> changelog in the build script, from which I gather that they use git
>> snapshots. In particular, the one corresponding to the version
>> Grossfield is using is:
>> 
>> 1.8.23-6.20110214.1049-git089726a
>> 
>> So he has a git snapshot from a bit more than one year and a half ago.
>> By the way, there is a newer entry (in the script for Fedora 17, the
>> current stable release) dated 2012-01-25 saying that they updated that
>> one to:
>> 
>> 1.8.23-7.20120125.768-git8b62284
>> 
>> I don't have any idea about the issue at hand, though.
>> 
>> Alessandro
>> 
>> [1] https://admin.fedoraproject.org/pkgdb/acls/name/vim-latex?_csrf_token=75695c0b53d7e1dbefa6eca5638f5eb988da891e
>> 
>> 
>> 
> 
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Wed, 21 Nov 2012 06:57:11 -0500
> From: yuejun yin <yj...@gm...>
> Subject: [Vim-latex-devel] question mark
> To: vim...@li...
> Message-ID: <EFD...@gm...>
> Content-Type: text/plain; charset=us-ascii
> 
> Hi
> when i input a question mark (?) in macvim, it will be automatically replaced by a dollar sign ($). anyone knows how this happens? thanks.
> YJ
> 
> 
> ------------------------------
> 
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> 
> ------------------------------
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> End of Vim-latex-devel Digest, Vol 69, Issue 3
> **********************************************

___________________________________
Dr. Alan Grossfield
Assistant Professor
Department of Biochemistry and Biophysics
University of Rochester Medical Center
610 Elmwood Ave, Box 712
Rochester, NY 14642
Phone: 585 276 4193
http://membrane.urmc.rochester.edu

[Vim-latex-devel] View rule when use Makefile

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

Hi,
I'm using a Makefile for compile my document and eventually I type
`\lv` not in the master document (say, `aux.tex`) and it try to open
the `aux.pdf`.
There is some thing to fix this behavior that is not set the `*.latexmain`?

Thanks,
Raniere