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

Re: [Vim-latex-devel] VEnclose and ignorecase

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

On Sun, Feb 13, 2011 at 10:49:22PM +0100, Philipp Hartwig wrote:

> the function VEnclose of the imaps plugin uses the test
> 	if (visualmode() == 'v' && (a:vstart != '' || a:vend != '')) || (a:VStart == '' && a:VEnd == '')
> to determine if characterwise or linewise selection was used. However if 
> a user has set "ignorecase" the operator "==" is case-insensitive and 
> hence
>     visualmode() == 'v'
> will always be true.
> 
> Using "==#" instead of "==" fixes this.

Thank you, this has been fixed in a recent git commit.

Regards
Till

[Vim-latex-devel] migration from svn to git

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

Hello everyone,

vim-latex is now using git instead of svn. I hope the migration worked
without major problems. If you find any irregularities, please report
them.

Checkout instructions can be found here:
https://sourceforge.net/scm/?type=git&group_id=52322

Regards
Till

Re: [Vim-latex-devel] 2 small Patches

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

On Tue, Jan 04, 2011 at 03:38:18PM +0100, Gerd Wachsmuth wrote:

> I attached two small patches:
> 
> - the first will correct the behavior of < <M-L>, there was one "\"
> missing.
>  - the other one will correct the behaviour with bib-files with
> capital entries.

Thank you, the patches have been applied recently into the new git
repository.

Regards
Till

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

On Mon, 2011-02-14 at 15:13 +0800, Ng Oon-Ee wrote:
> I've got the following setup (simplified)
> 
> .
> ..
> main.tex
> chap1/
>    chap1.tex
> 
> When editing main.tex, \ll works fine, everything comes out correct.
> 
> When editing chap1.tex, \ll gives the following.
> 
> || I can't find file `main.tex'. main.tex 
> || Emergency stop.
> 
> There is no main.log, only a chap1.log in the chap1/ folder. I conclude that latexsuite is trying to compile inside the chap1/ folder. My CompileRule is as follows:-
> 
> g:Tex_CompileRule_dvi  latex -interaction=nonstopmode --src-specials $*  
> 
> Please advise what else I can do to check this. Am using 64-bit Arch Linux, am using svn revision 1115 with vim 7.3.102
> 
Sorry, I got contacted off-list, just to confirm, I do have
main.tex.latexmain as per the wiki in the root directory. That's why the
error refers to 'main.tex' rather than 'chap1.tex'

[Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

I've got the following setup (simplified)

.
..
main.tex
chap1/
   chap1.tex

When editing main.tex, \ll works fine, everything comes out correct.

When editing chap1.tex, \ll gives the following.

|| I can't find file `main.tex'. main.tex 
|| Emergency stop.

There is no main.log, only a chap1.log in the chap1/ folder. I conclude that latexsuite is trying to compile inside the chap1/ folder. My CompileRule is as follows:-

g:Tex_CompileRule_dvi  latex -interaction=nonstopmode --src-specials $*  

Please advise what else I can do to check this. Am using 64-bit Arch Linux, am using svn revision 1115 with vim 7.3.102

[Vim-latex-devel] Able to do compilation in a sub-directory?

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

Hi,

I'm coming from a texlipse (Eclipse plug-in) background. Been through
the Latex-Suite Reference, but could not find this particular 'feature'.

Would it be possible to do a compile in a specific subdirectory (by
default ./tmp in texlipse). This helps prevent clutter in the main
directory.

I've not checked, but I believe texlipse does this using the
--output-directory option of tex/pdflatex. Would changing
g:Tex_CompileRule_* allow me to have this behaviour (all the temporary
files like aux,bbl,blg,log,out,toc in ./tmp but the final output dvi/pdf
in ./)?

[Vim-latex-devel] VEnclose and ignorecase

[Philipp H. <phi...@un...>]

Hello,

the function VEnclose of the imaps plugin uses the test
	if (visualmode() == 'v' && (a:vstart != '' || a:vend != '')) || (a:VStart == '' && a:VEnd == '')
to determine if characterwise or linewise selection was used. However if 
a user has set "ignorecase" the operator "==" is case-insensitive and 
hence
    visualmode() == 'v'
will always be true.

Using "==#" instead of "==" fixes this.

Regards, 
Philipp

[Vim-latex-devel] Using a %!TEX directive

[Vijay K. <vij...@gm...>]

Hi all! I was looking at XeLaTeX recently, and being a vim-latex user,
was then looking to see how to either rebind "\ll" or create new
binding ("\lx" maybe?) for compiling with xelatex.

Then I had a thought:

It would be great if the latex-suite could compile, via "\ll", using a
directive at the top of the source file something like TeXShop's
"%!TEX TS-program = xelatex" directives.

Does that make sense? Would it be easy/straightforward to implement?

Anyway, I just thought I'd throw this out there.

Thanks!
-Vijay

Re: [Vim-latex-devel] Question regarding synctex support (pdf)

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

On Sat, 2011-02-05 at 11:35 +0100, Mario Santagiuliana wrote:
> In data 5/2/2011 11:19:21, Ng Oon-Ee ha scritto:
> > Hi all, regarding the above:-
> > 
> > https://facwiki.cs.byu.edu/nlp/index.php/Vim%2BLaTeX_on_Linux
> > seems to be the only good resource I can find on this. Can't seem to get
> > it working with okular though. pdflatex runs with -synctex=1 and
> > generates main.synctex.gz, but \ls just opens the pdf without going to
> > the specified location.
> > 
> > Anyone gotten this working on okular (or any other linux editor)? I
> > can't find the appropriate code to change as mentioned in the above
> > blog.
> > 
> > 
> > ------------------------------------------------------------------------
> > ------ The modern datacenter depends on network connectivity to access
> > resources and provide services. The best practices for maximizing a
> > physical server's connectivity to a physical network are well
> > understood - see how these rules translate into the virtual world?
> > http://p.sf.net/sfu/oracle-sfdevnlfb
> There is a patch to use okular in vim-latex:
> http://sourceforge.net/tracker/?func=detail&aid=3004833&group_id=52322&atid=466458
> This patch is not included in the latest vim-latex stable release, you 
> should use vim-latex from git-repository.
Thanks Mario, this seems to be dvi specific. Is pdf possible as well?

Re: [Vim-latex-devel] Question regarding synctex support (pdf)

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

On Sat, 2011-02-05 at 18:19 +0800, Ng Oon-Ee wrote:
> Hi all, regarding the above:-
> 
> https://facwiki.cs.byu.edu/nlp/index.php/Vim%2BLaTeX_on_Linux
> seems to be the only good resource I can find on this. Can't seem to get
> it working with okular though. pdflatex runs with -synctex=1 and
> generates main.synctex.gz, but \ls just opens the pdf without going to
> the specified location.
> 
> Anyone gotten this working on okular (or any other linux editor)? I
> can't find the appropriate code to change as mentioned in the above
> blog.
> 
http://comments.gmane.org/gmane.comp.editors.vim.latex.devel/868

This states that support has gone in to SVN, I compiled vim-latex from
SVN and sure enough dvi works. Will pdf support be forthcoming?

Re: [Vim-latex-devel] Question regarding synctex support (pdf)

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

In data 5/2/2011 11:19:21, Ng Oon-Ee ha scritto:
> Hi all, regarding the above:-
> 
> https://facwiki.cs.byu.edu/nlp/index.php/Vim%2BLaTeX_on_Linux
> seems to be the only good resource I can find on this. Can't seem to get
> it working with okular though. pdflatex runs with -synctex=1 and
> generates main.synctex.gz, but \ls just opens the pdf without going to
> the specified location.
> 
> Anyone gotten this working on okular (or any other linux editor)? I
> can't find the appropriate code to change as mentioned in the above
> blog.
> 
> 
> ------------------------------------------------------------------------
> ------ The modern datacenter depends on network connectivity to access
> resources and provide services. The best practices for maximizing a
> physical server's connectivity to a physical network are well
> understood - see how these rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

There is a patch to use okular in vim-latex:
http://sourceforge.net/tracker/?func=detail&aid=3004833&group_id=52322&atid=466458
This patch is not included in the latest vim-latex stable release, you 
should use vim-latex from git-repository.
-- 
Mario Santagiuliana
www.marionline.it

[Vim-latex-devel] Question regarding synctex support (pdf)

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

Hi all, regarding the above:-

https://facwiki.cs.byu.edu/nlp/index.php/Vim%2BLaTeX_on_Linux
seems to be the only good resource I can find on this. Can't seem to get
it working with okular though. pdflatex runs with -synctex=1 and
generates main.synctex.gz, but \ls just opens the pdf without going to
the specified location.

Anyone gotten this working on okular (or any other linux editor)? I
can't find the appropriate code to change as mentioned in the above
blog.

Re: [Vim-latex-devel] Log file reloading on compilation

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

Great :) Thanks for the feedback, glad to have helped !
Cheers,

Ju

On Mon, Jan 31, 2011 at 7:55 PM, martin throw <mar...@gm...> wrote:
> Hi,
>
> That works beautifully. Thanks!
>
> On Wed, Jan 26, 2011 at 2:45 AM, Julien Cornebise
> <jul...@gm...> wrote:
>>
>> Maybe putting the setting it in a file-type file for *.log via
>> ftplugin or, much simpler, in global but using autocommand: you may
>> try
>> autocmd BufRead *.log set ar
>> (no guarantee, haven't tried)
>>
>> Hope this helps!
>> Julien
>>
>> On Tue, Jan 25, 2011 at 9:50 PM, martin throw <mar...@gm...>
>> wrote:
>> > Thanks for the comment, that works but I was hoping to not set the
>> > autoreload behavior globally, but only on the loaded log file. But I
>> > guess
>> > it is not a big deal to have the autoreload behavior to be global.
>> >
>> > Thanks
>> >
>> > On Mon, Jan 24, 2011 at 11:34 PM, Julien Cornebise
>> > <jul...@gm...> wrote:
>> >>
>> >> Did you try
>> >> set ar
>> >> ?
>> >> Best regards
>> >>
>> >> Julien
>> >>
>> >> On Tue, Jan 25, 2011 at 3:18 AM, martin throw <mar...@gm...>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > Every time I compile using \ll (with multiple passes), the
>> >> > corresponding
>> >> > log
>> >> > file gets loaded into the buffer.
>> >> > It gets distracting when I recompile again as VIM warns about the
>> >> > file
>> >> > changing since editing started (W11). Is there a missing autoreload
>> >> > behavior
>> >> > for opening the log file?
>> >> >
>> >> > I am using gVim on Windows with the latest vim-latex suite package.
>> >> > Below is
>> >> > my vimrc file
>> >> >
>> >> > Thanks!
>> >> >
>> >> >
>> >> > set expandtab
>> >> > set tabstop=2
>> >> > set shiftwidth=2
>> >> > set autoindent
>> >> > set smartindent
>> >> > set number
>> >> > set hidden
>> >> > colorscheme rdark
>> >> > set so=5
>> >> > set wrap linebreak textwidth=0
>> >> > syntax on
>> >> >
>> >> > set gfn=DejaVu\ Sans\ Mono\ 11
>> >> >
>> >> > " REQUIRED. This makes vim invoke Latex-Suite when you open a tex
>> >> > file.
>> >> > filetype plugin on
>> >> >
>> >> > " IMPORTANT: win32 users will need to have 'shellslash' set so that
>> >> > latex
>> >> > " can be called correctly.
>> >> > set shellslash
>> >> >
>> >> > " IMPORTANT: grep will sometimes skip displaying the file name if you
>> >> > " search in a singe file. This will confuse Latex-Suite. Set your
>> >> > grep
>> >> > " program to always generate a file-name.
>> >> > set grepprg=grep\ -nH\ $*
>> >> >
>> >> > " OPTIONAL: This enables automatic indentation as you type.
>> >> > filetype indent on
>> >> >
>> >> > " OPTIONAL: Starting with Vim 7, the filetype of empty .tex files
>> >> > defaults
>> >> > to
>> >> > " 'plaintex' instead of 'tex', which results in vim-latex not being
>> >> > loaded.
>> >> > " The following changes the default filetype back to 'tex':
>> >> > let g:tex_flavor='latex'
>> >> >
>> >> > let g:Tex_DefaultTargetFormat='pdf'
>> >> > let g:Tex_MultipleCompileFormats='pdf'
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>> >> > Finally, a world-class log management solution at an even better
>> >> > price-free!
>> >> > Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>> >> > February 28th, so secure your free ArcSight Logger TODAY!
>> >> > http://p.sf.net/sfu/arcsight-sfd2d
>> >> > _______________________________________________
>> >> > Vim-latex-devel mailing list
>> >> > Vim...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>> >> >
>> >> >
>> >
>> >
>
>

Re: [Vim-latex-devel] Log file reloading on compilation

[martin t. <mar...@gm...>]

Hi,

That works beautifully. Thanks!

On Wed, Jan 26, 2011 at 2:45 AM, Julien Cornebise <
jul...@gm...> wrote:

> Maybe putting the setting it in a file-type file for *.log via
> ftplugin or, much simpler, in global but using autocommand: you may
> try
> autocmd BufRead *.log set ar
> (no guarantee, haven't tried)
>
> Hope this helps!
> Julien
>
> On Tue, Jan 25, 2011 at 9:50 PM, martin throw <mar...@gm...>
> wrote:
> > Thanks for the comment, that works but I was hoping to not set the
> > autoreload behavior globally, but only on the loaded log file. But I
> guess
> > it is not a big deal to have the autoreload behavior to be global.
> >
> > Thanks
> >
> > On Mon, Jan 24, 2011 at 11:34 PM, Julien Cornebise
> > <jul...@gm...> wrote:
> >>
> >> Did you try
> >> set ar
> >> ?
> >> Best regards
> >>
> >> Julien
> >>
> >> On Tue, Jan 25, 2011 at 3:18 AM, martin throw <mar...@gm...>
> >> wrote:
> >> > Hi,
> >> >
> >> > Every time I compile using \ll (with multiple passes), the
> corresponding
> >> > log
> >> > file gets loaded into the buffer.
> >> > It gets distracting when I recompile again as VIM warns about the file
> >> > changing since editing started (W11). Is there a missing autoreload
> >> > behavior
> >> > for opening the log file?
> >> >
> >> > I am using gVim on Windows with the latest vim-latex suite package.
> >> > Below is
> >> > my vimrc file
> >> >
> >> > Thanks!
> >> >
> >> >
> >> > set expandtab
> >> > set tabstop=2
> >> > set shiftwidth=2
> >> > set autoindent
> >> > set smartindent
> >> > set number
> >> > set hidden
> >> > colorscheme rdark
> >> > set so=5
> >> > set wrap linebreak textwidth=0
> >> > syntax on
> >> >
> >> > set gfn=DejaVu\ Sans\ Mono\ 11
> >> >
> >> > " REQUIRED. This makes vim invoke Latex-Suite when you open a tex
> file.
> >> > filetype plugin on
> >> >
> >> > " IMPORTANT: win32 users will need to have 'shellslash' set so that
> >> > latex
> >> > " can be called correctly.
> >> > set shellslash
> >> >
> >> > " IMPORTANT: grep will sometimes skip displaying the file name if you
> >> > " search in a singe file. This will confuse Latex-Suite. Set your grep
> >> > " program to always generate a file-name.
> >> > set grepprg=grep\ -nH\ $*
> >> >
> >> > " OPTIONAL: This enables automatic indentation as you type.
> >> > filetype indent on
> >> >
> >> > " OPTIONAL: Starting with Vim 7, the filetype of empty .tex files
> >> > defaults
> >> > to
> >> > " 'plaintex' instead of 'tex', which results in vim-latex not being
> >> > loaded.
> >> > " The following changes the default filetype back to 'tex':
> >> > let g:tex_flavor='latex'
> >> >
> >> > let g:Tex_DefaultTargetFormat='pdf'
> >> > let g:Tex_MultipleCompileFormats='pdf'
> >> >
> >> >
> >> >
> >> >
> ------------------------------------------------------------------------------
> >> > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> >> > Finally, a world-class log management solution at an even better
> >> > price-free!
> >> > Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> >> > February 28th, so secure your free ArcSight Logger TODAY!
> >> > http://p.sf.net/sfu/arcsight-sfd2d
> >> > _______________________________________________
> >> > Vim-latex-devel mailing list
> >> > Vim...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> >> >
> >> >
> >
> >
>

Re: [Vim-latex-devel] Log file reloading on compilation

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

Maybe putting the setting it in a file-type file for *.log via
ftplugin or, much simpler, in global but using autocommand: you may
try
autocmd BufRead *.log set ar
(no guarantee, haven't tried)

Hope this helps!
Julien

On Tue, Jan 25, 2011 at 9:50 PM, martin throw <mar...@gm...> wrote:
> Thanks for the comment, that works but I was hoping to not set the
> autoreload behavior globally, but only on the loaded log file. But I guess
> it is not a big deal to have the autoreload behavior to be global.
>
> Thanks
>
> On Mon, Jan 24, 2011 at 11:34 PM, Julien Cornebise
> <jul...@gm...> wrote:
>>
>> Did you try
>> set ar
>> ?
>> Best regards
>>
>> Julien
>>
>> On Tue, Jan 25, 2011 at 3:18 AM, martin throw <mar...@gm...>
>> wrote:
>> > Hi,
>> >
>> > Every time I compile using \ll (with multiple passes), the corresponding
>> > log
>> > file gets loaded into the buffer.
>> > It gets distracting when I recompile again as VIM warns about the file
>> > changing since editing started (W11). Is there a missing autoreload
>> > behavior
>> > for opening the log file?
>> >
>> > I am using gVim on Windows with the latest vim-latex suite package.
>> > Below is
>> > my vimrc file
>> >
>> > Thanks!
>> >
>> >
>> > set expandtab
>> > set tabstop=2
>> > set shiftwidth=2
>> > set autoindent
>> > set smartindent
>> > set number
>> > set hidden
>> > colorscheme rdark
>> > set so=5
>> > set wrap linebreak textwidth=0
>> > syntax on
>> >
>> > set gfn=DejaVu\ Sans\ Mono\ 11
>> >
>> > " REQUIRED. This makes vim invoke Latex-Suite when you open a tex file.
>> > filetype plugin on
>> >
>> > " IMPORTANT: win32 users will need to have 'shellslash' set so that
>> > latex
>> > " can be called correctly.
>> > set shellslash
>> >
>> > " IMPORTANT: grep will sometimes skip displaying the file name if you
>> > " search in a singe file. This will confuse Latex-Suite. Set your grep
>> > " program to always generate a file-name.
>> > set grepprg=grep\ -nH\ $*
>> >
>> > " OPTIONAL: This enables automatic indentation as you type.
>> > filetype indent on
>> >
>> > " OPTIONAL: Starting with Vim 7, the filetype of empty .tex files
>> > defaults
>> > to
>> > " 'plaintex' instead of 'tex', which results in vim-latex not being
>> > loaded.
>> > " The following changes the default filetype back to 'tex':
>> > let g:tex_flavor='latex'
>> >
>> > let g:Tex_DefaultTargetFormat='pdf'
>> > let g:Tex_MultipleCompileFormats='pdf'
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>> > Finally, a world-class log management solution at an even better
>> > price-free!
>> > Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>> > February 28th, so secure your free ArcSight Logger TODAY!
>> > http://p.sf.net/sfu/arcsight-sfd2d
>> > _______________________________________________
>> > Vim-latex-devel mailing list
>> > Vim...@li...
>> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>> >
>> >
>
>

Re: [Vim-latex-devel] Log file reloading on compilation

[martin t. <mar...@gm...>]

Thanks for the comment, that works but I was hoping to not set the
autoreload behavior globally, but only on the loaded log file. But I guess
it is not a big deal to have the autoreload behavior to be global.

Thanks

On Mon, Jan 24, 2011 at 11:34 PM, Julien Cornebise <
jul...@gm...> wrote:

> Did you try
> set ar
> ?
> Best regards
>
> Julien
>
> On Tue, Jan 25, 2011 at 3:18 AM, martin throw <mar...@gm...>
> wrote:
> > Hi,
> >
> > Every time I compile using \ll (with multiple passes), the corresponding
> log
> > file gets loaded into the buffer.
> > It gets distracting when I recompile again as VIM warns about the file
> > changing since editing started (W11). Is there a missing autoreload
> behavior
> > for opening the log file?
> >
> > I am using gVim on Windows with the latest vim-latex suite package. Below
> is
> > my vimrc file
> >
> > Thanks!
> >
> >
> > set expandtab
> > set tabstop=2
> > set shiftwidth=2
> > set autoindent
> > set smartindent
> > set number
> > set hidden
> > colorscheme rdark
> > set so=5
> > set wrap linebreak textwidth=0
> > syntax on
> >
> > set gfn=DejaVu\ Sans\ Mono\ 11
> >
> > " REQUIRED. This makes vim invoke Latex-Suite when you open a tex file.
> > filetype plugin on
> >
> > " IMPORTANT: win32 users will need to have 'shellslash' set so that latex
> > " can be called correctly.
> > set shellslash
> >
> > " IMPORTANT: grep will sometimes skip displaying the file name if you
> > " search in a singe file. This will confuse Latex-Suite. Set your grep
> > " program to always generate a file-name.
> > set grepprg=grep\ -nH\ $*
> >
> > " OPTIONAL: This enables automatic indentation as you type.
> > filetype indent on
> >
> > " OPTIONAL: Starting with Vim 7, the filetype of empty .tex files
> defaults
> > to
> > " 'plaintex' instead of 'tex', which results in vim-latex not being
> loaded.
> > " The following changes the default filetype back to 'tex':
> > let g:tex_flavor='latex'
> >
> > let g:Tex_DefaultTargetFormat='pdf'
> > let g:Tex_MultipleCompileFormats='pdf'
> >
> >
> >
> ------------------------------------------------------------------------------
> > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> > Finally, a world-class log management solution at an even better
> price-free!
> > Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> > February 28th, so secure your free ArcSight Logger TODAY!
> > http://p.sf.net/sfu/arcsight-sfd2d
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> >
> >
>

Re: [Vim-latex-devel] Log file reloading on compilation

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

Did you try
set ar
?
Best regards

Julien

On Tue, Jan 25, 2011 at 3:18 AM, martin throw <mar...@gm...> wrote:
> Hi,
>
> Every time I compile using \ll (with multiple passes), the corresponding log
> file gets loaded into the buffer.
> It gets distracting when I recompile again as VIM warns about the file
> changing since editing started (W11). Is there a missing autoreload behavior
> for opening the log file?
>
> I am using gVim on Windows with the latest vim-latex suite package. Below is
> my vimrc file
>
> Thanks!
>
>
> set expandtab
> set tabstop=2
> set shiftwidth=2
> set autoindent
> set smartindent
> set number
> set hidden
> colorscheme rdark
> set so=5
> set wrap linebreak textwidth=0
> syntax on
>
> set gfn=DejaVu\ Sans\ Mono\ 11
>
> " REQUIRED. This makes vim invoke Latex-Suite when you open a tex file.
> filetype plugin on
>
> " IMPORTANT: win32 users will need to have 'shellslash' set so that latex
> " can be called correctly.
> set shellslash
>
> " IMPORTANT: grep will sometimes skip displaying the file name if you
> " search in a singe file. This will confuse Latex-Suite. Set your grep
> " program to always generate a file-name.
> set grepprg=grep\ -nH\ $*
>
> " OPTIONAL: This enables automatic indentation as you type.
> filetype indent on
>
> " OPTIONAL: Starting with Vim 7, the filetype of empty .tex files defaults
> to
> " 'plaintex' instead of 'tex', which results in vim-latex not being loaded.
> " The following changes the default filetype back to 'tex':
> let g:tex_flavor='latex'
>
> let g:Tex_DefaultTargetFormat='pdf'
> let g:Tex_MultipleCompileFormats='pdf'
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

[Vim-latex-devel] Log file reloading on compilation

[martin t. <mar...@gm...>]

Hi,

Every time I compile using \ll (with multiple passes), the corresponding log
file gets loaded into the buffer.
It gets distracting when I recompile again as VIM warns about the file
changing since editing started (W11). Is there a missing autoreload behavior
for opening the log file?

I am using gVim on Windows with the latest vim-latex suite package. Below is
my vimrc file

Thanks!


set expandtab
set tabstop=2
set shiftwidth=2
set autoindent
set smartindent
set number
set hidden
colorscheme rdark
set so=5
set wrap linebreak textwidth=0
syntax on

set gfn=DejaVu\ Sans\ Mono\ 11

" REQUIRED. This makes vim invoke Latex-Suite when you open a tex file.
filetype plugin on

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

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

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

" OPTIONAL: Starting with Vim 7, the filetype of empty .tex files defaults
to
" 'plaintex' instead of 'tex', which results in vim-latex not being loaded.
" The following changes the default filetype back to 'tex':
let g:tex_flavor='latex'

let g:Tex_DefaultTargetFormat='pdf'
let g:Tex_MultipleCompileFormats='pdf'

[Vim-latex-devel] cursor position after backlash

[Cesar R. <ces...@gm...>]

I'm using vim 7.3.105 on Win XP.
If I press \\ the cursor remains between the backslashes, not after the
second backslash. If I press one backslash and wait a couple of seconds,
and then press the second backslash, then I get the cursor after the
second backslash.
That happens only with filetype set to tex, not when it is set to
plaintex.

Many thanks in advance,

-- 
Cesar

Re: [Vim-latex-devel] \cite{<F9> completion does not work

[Robson R. S. P. <rob...@gm...>]

On Sun, Jan 23, 2011 at 9:59 AM, Peter Volkov <pv...@ge...> wrote:
> В Вск, 23/01/2011 в 09:14 -0300, Robson Roberto Souza Peixoto пишет:
>> On Sun, Jan 23, 2011 at 7:37 AM, Peter Volkov <pv...@ge...> wrote:
>> >
>> > Hi. I saw thread with exactly same name and have "fixed" vim-latex suite
>> > installed here (1.8.23.20101027). Anyway if I write \cite{F9 the window
>> > to select reference opens but after I select reference and press <enter>
>> > nothing appears after \cite{. Testcase to reproduce the problem is in
>> > attachment. Also note: I'm using xelatex and thus I have the following
>> > customization inside ~/.vimrc:
>> >
>> > "vim-latex for xetex!
>> > let g:Tex_DefaultTargetFormat = 'pdf'
>> > let g:Tex_ViewRule_pdf='evince'
>> > let g:Tex_CompileRule_pdf = 'xelatex --interaction=nonstopmode $*'
>> > map <f2> :w<cr><leader>ll
>> > let g:Tex_MultipleCompileFormats = 'pdf'
>> >
>>
>> Are you have the 'grep' installed?
>
> Sure.
> $ grep -V
> GNU grep 2.5.4
>
>>  After install, do it.
>>
>> " IMPORTANT: grep will sometimes skip displaying the file name if you
>> " search in a singe file. This will confuse Latex-Suite. Set your grep
>> " program to always generate a file-name.
>> set grepprg=grep\ -nH\ $*
>
> I've tried to put this into ~/.vimrc but still no luck. BTW, I have
> VIM 7.3 installed here.

I'm using VIM 7.1.102 and are working very well.
BTW, from my vimrc:
  " {{{ Latex
  au FileType tex setl spell spelllang=pt grepprg=grep\ -nH\ $*
makeprg=make\ $* sw=2 ts=2 sts=2 et iskeyword+=:
  au FileType bib setl spell spelllang=pt makeprg=make\ $* sw=2 ts=2 sts=2 et
  let g:tex_flavor = "latex"
  " }}}

and from ~/.vim/ftplugin/tex.vim
" Q: I cannot insert the e-acute (é) character! HELP!
imap <buffer> <leader>it <Plug>Tex_InsertItemOnThisLine
" Q: Typing some European characters becomes problematic in
Latex-suite because those characters seem to be mapped to something.
imap <C-b> <Plug>Tex_MathBF
imap <C-c> <Plug>Tex_MathCal
imap <C-l> <Plug>Tex_LeftRight


But for my latex project work well, I need to create the a empty file
dissertacao.tex.latexmain because the dissertacao.tex is my main file.
And the cwd(current working directory) is where the main file are.

I don't know if it is necessary, but I do it.


> --
> Peter.
>
>



-- 
Robson Roberto Souza Peixoto
Robinho
Computer Science Master's degree student, University of Campinas
Linux Counter #395633
IRC: robsonpeixoto
Twitter: http://twitter.com/rrspba
github: https://github.com/robsonpeixoto

Re: [Vim-latex-devel] \cite{<F9> completion does not work

[Peter V. <pv...@ge...>]

В Вск, 23/01/2011 в 09:14 -0300, Robson Roberto Souza Peixoto пишет:
> On Sun, Jan 23, 2011 at 7:37 AM, Peter Volkov <pv...@ge...> wrote:
> >
> > Hi. I saw thread with exactly same name and have "fixed" vim-latex suite
> > installed here (1.8.23.20101027). Anyway if I write \cite{F9 the window
> > to select reference opens but after I select reference and press <enter>
> > nothing appears after \cite{. Testcase to reproduce the problem is in
> > attachment. Also note: I'm using xelatex and thus I have the following
> > customization inside ~/.vimrc:
> >
> > "vim-latex for xetex!
> > let g:Tex_DefaultTargetFormat = 'pdf'
> > let g:Tex_ViewRule_pdf='evince'
> > let g:Tex_CompileRule_pdf = 'xelatex --interaction=nonstopmode $*'
> > map <f2> :w<cr><leader>ll
> > let g:Tex_MultipleCompileFormats = 'pdf'
> >
> 
> Are you have the 'grep' installed?

Sure.
$ grep -V
GNU grep 2.5.4

>  After install, do it.
> 
> " IMPORTANT: grep will sometimes skip displaying the file name if you
> " search in a singe file. This will confuse Latex-Suite. Set your grep
> " program to always generate a file-name.
> set grepprg=grep\ -nH\ $*

I've tried to put this into ~/.vimrc but still no luck. BTW, I have 
VIM 7.3 installed here.

-- 
Peter.

Re: [Vim-latex-devel] \cite{<F9> completion does not work

[Robson R. S. P. <rob...@gm...>]

On Sun, Jan 23, 2011 at 7:37 AM, Peter Volkov <pv...@ge...> wrote:
>
> Hi. I saw thread with exactly same name and have "fixed" vim-latex suite
> installed here (1.8.23.20101027). Anyway if I write \cite{F9 the window
> to select reference opens but after I select reference and press <enter>
> nothing appears after \cite{. Testcase to reproduce the problem is in
> attachment. Also note: I'm using xelatex and thus I have the following
> customization inside ~/.vimrc:
>
> "vim-latex for xetex!
> let g:Tex_DefaultTargetFormat = 'pdf'
> let g:Tex_ViewRule_pdf='evince'
> let g:Tex_CompileRule_pdf = 'xelatex --interaction=nonstopmode $*'
> map <f2> :w<cr><leader>ll
> let g:Tex_MultipleCompileFormats = 'pdf'
>

Are you have the 'grep' installed? After install, do it.

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


[ ]s

>
> Thanks in advance for any help,
> --
> Peter.
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>



--
Robson Roberto Souza Peixoto
Robinho
Computer Science Master's degree student, University of Campinas
Linux Counter #395633
IRC: robsonpeixoto
Twitter: http://twitter.com/rrspba
github: https://github.com/robsonpeixoto

[Vim-latex-devel] \cite{<F9> completion does not work

[Peter V. <pv...@ge...>]

Hi. I saw thread with exactly same name and have "fixed" vim-latex suite
installed here (1.8.23.20101027). Anyway if I write \cite{F9 the window
to select reference opens but after I select reference and press <enter>
nothing appears after \cite{. Testcase to reproduce the problem is in
attachment. Also note: I'm using xelatex and thus I have the following
customization inside ~/.vimrc:

"vim-latex for xetex!
let g:Tex_DefaultTargetFormat = 'pdf'
let g:Tex_ViewRule_pdf='evince'
let g:Tex_CompileRule_pdf = 'xelatex --interaction=nonstopmode $*'
map <f2> :w<cr><leader>ll
let g:Tex_MultipleCompileFormats = 'pdf'

Thanks in advance for any help,
-- 
Peter.

[Vim-latex-devel] Template names missing in MacVim

[Tony M. <to...@to...>]

I'm running MacVim 7.3 (53) on MacOS X 10.6.5 on a Core2Duo MacBook. I 
only recently started learning Vim, and was working through the 
tutorials for Vim-LaTeX when I noticed that the template names don't 
show up in the menu.

You can see how it looks here: 
http://www.tonymcdaniel.com/uploads/template_menu.jpeg

I tried editing the templates.vim file to remove the ':' and <Tab>, 
thinking that perhaps those were the problem, but it didn't help. The 
only difference was that the numbers were in the menu without the ':' 
afterward.

This seems to be happening in other menus where a list of items should 
be enumerated. For example, in the Macros menu, the last entry is '1: '.

Thanks for any help you can provide.

-- 
Tony

www.tonymcdaniel.com <http://www.tonymcdaniel.com>

[Vim-latex-devel] 2 small Patches

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

Hi all,

I attached two small patches:

- the first will correct the behavior of < <M-L>, there was one "\" 
missing.
  - the other one will correct the behaviour with bib-files with capital 
entries.


Best Regards
Gerd