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

[Vim-latex-devel] [ vim-latex-Patches-3573601 ] Changed begin center end center to centering in figures

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

Patches item #3573601, was opened at 2012-10-01 18:01
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3573601&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: Changed begin center end center to centering in figures

Initial Comment:
In figure environments, \centering should be preferred over the center environment; the latter leaves unwated vertical space. The patch reflects this fact.

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

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

[Vim-latex-devel] Is there any way of checking if a call to IMAP_Jumpfun succeeded?

[Jorge R. <sk...@gm...>]

Hi,

I would like to know if there is a way of checking if a call to
IMAP_Jumpfun has succeeded.
By success I mean that any action was performed, that is either moving
the text, selecting text or deleting text.

A call to this function that would not change anything would in this
sense "not succeed".

It would be nice if we could check the value of a specific global
variable that would be modified inside this function,
according to the result of the function execution.

Say the variable would be called g:imap_jumpfun_res. Then after
calling this function I could check the value of this function
and take appropriate action depending on the value of the variable.


Hope there is a way of doing this, or that the maintainers of the
plugin would consider implementing something something like this
in a future release.

thanks,

Jorge

[Vim-latex-devel] mapping <Tab> to autocomplete

[Gastón A. <gar...@sl...>]

Hello all

I was trying to map<Tab>  to autocomplete, something like
:inoremap<Tab>  <C-n>

but the mapping
imap<C-i>  <Plug>Tex_InsertItemOnThisLine
in $VIM/ftplugin/tex.vim seems to be connected with Tab key, I don't
know how, and there is no way to use Tab in a tex file.

If I change the<C-i>  mapping the completion using Tab key works well,
but i can't insert the e-acute character any more.

somebody knows how can i solve this?
thank you,
Gastón

Re: [Vim-latex-devel] save and compile together

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

>> Is it possible from userside to combine this to command together, i.e.,
>> some keyword mapping that will do the save and compile together?
>>  Or am I asking a magic?
>
> When you run the compilation with \ll, the file is automatically saved, so
> you can skip the "pure vim" part. At least, that is how it works here.

This whole behavior is governed by autowrite:

:help autowrite

which comes from Vim, not Vim-LaTeX. \ll eventually calls a ":make",
which is where autowrite's jurisdiction comes in.

So think of \ll as a specialized frontend to :make.

--Ted

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

Re: [Vim-latex-devel] Automatic redirection to errors

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

Hi Tohiko,

The easiest way to deal with these unwanted jumps is simply to press
<ctrl-o>. Vim doesn't close the file - it just goes to the background.
You shouldn't lose your undo stack unless you re-open it.

Best,
Mike

On Mon, Sep 17, 2012 at 6:07 AM, Alessandro Pezzoni
<ale...@la...> wrote:
> On Mon, Sep 17, 2012 at 11:42:20AM +0300, Tohiko Looka wrote:
>> One of the annoying features of vim-latex is that it automatically
>> goes to the first error or warning after a compilation
>> This is annoying because I lose my undo stack and I have to open the
>> file again. It also sometimes goes to unrelated files like aux files
>> for example.
>>
>> How can I disable this behavior?
>
>> I forgot to mention that I do have
>> Tex_GoToError=0
>> But the quickfix window still pops up and the file with the error is
>> automatically opened
>
> Greetings to you.
> If my memory doesn't fail me, this is issue is actually due to vim's
> error parser and not (directly) to vim-latex. Basically, to properly fix
> this you can sanitize LaTeX's error messages before passing them to vim.
> Here [1] you can find some ideas on that line (the "rubber" link is
> dead, you can find it here [2]).
> Please note that I didn't have a chance to try out this setup, yet.
>
> I hope this helps,
> Alessandro
>
> [1] http://phaseportrait.blogspot.it/2008/03/fixing-vim-latex-compiler-error.html
> [2] https://launchpad.net/rubber
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] save and compile together

[Cédric B. <ced...@gm...>]

Hi!

On Mon, Sep 17, 2012 at 01:37:24PM +0100, Rudra Banerjee wrote:
> Hello Friends,
> I am a new face with vim-latex, realizing a bit too late that its better
> to customize vim for the file  types I am working rather then having a
> bunch of IDE's for each  language.
> Anyway, I am looking for one solution:  compile a file is two step
> process: <:+w>(vim) and \ll(vim-latex).
> Is it possible from userside to combine this to command together, i.e.,
> some keyword mapping that will do the save and compile together?
>  Or am I asking a magic?

When you run the compilation with \ll, the file is automatically saved, so
you can skip the "pure vim" part. At least, that is how it works here.

Regards,

Cédric

[Vim-latex-devel] save and compile together

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

Hello Friends,
I am a new face with vim-latex, realizing a bit too late that its better
to customize vim for the file  types I am working rather then having a
bunch of IDE's for each  language.
Anyway, I am looking for one solution:  compile a file is two step
process: <:+w>(vim) and \ll(vim-latex).
Is it possible from userside to combine this to command together, i.e.,
some keyword mapping that will do the save and compile together?
 Or am I asking a magic?

Re: [Vim-latex-devel] Automatic redirection to errors

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

On Mon, Sep 17, 2012 at 11:42:20AM +0300, Tohiko Looka wrote:
> One of the annoying features of vim-latex is that it automatically
> goes to the first error or warning after a compilation
> This is annoying because I lose my undo stack and I have to open the
> file again. It also sometimes goes to unrelated files like aux files
> for example.
> 
> How can I disable this behavior?

> I forgot to mention that I do have
> Tex_GoToError=0
> But the quickfix window still pops up and the file with the error is
> automatically opened

Greetings to you.
If my memory doesn't fail me, this is issue is actually due to vim's
error parser and not (directly) to vim-latex. Basically, to properly fix
this you can sanitize LaTeX's error messages before passing them to vim.
Here [1] you can find some ideas on that line (the "rubber" link is
dead, you can find it here [2]).
Please note that I didn't have a chance to try out this setup, yet.

I hope this helps,
Alessandro

[1] http://phaseportrait.blogspot.it/2008/03/fixing-vim-latex-compiler-error.html
[2] https://launchpad.net/rubber

Re: [Vim-latex-devel] Automatic redirection to errors

[Tohiko L. <toh...@gm...>]

I forgot to mention that I do have
Tex_GoToError=0
But the quickfix window still pops up and the file with the error is
automatically opened

[Vim-latex-devel] Automatic redirection to errors

[Tohiko L. <toh...@gm...>]

Greetings,

One of the annoying features of vim-latex is that it automatically
goes to the first error or warning after a compilation
This is annoying because I lose my undo stack and I have to open the
file again. It also sometimes goes to unrelated files like aux files
for example.

How can I disable this behavior?

Thank you,

Re: [Vim-latex-devel] autoindent with vimlatex

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

> my .vimrc looks:
> [...]
> "filetype on
> filetype plugin on
> let g:tex_flavor='latex'
> "filetype indent on

Dear Rudra Banerjee,
it seems that you have enabled filetype detection and plugin loading
only (through "filetype plugin on"). Please uncomment the
filetype indent on" line.

>From vim's 'filetype.txt' help file [1]:

						*:filetype-indent-on*
You can enable loading the indent file for specific file types with:
:filetype indent on If filetype detection was not switched on yet, it
will be as well. This actually loads the file "indent.vim" in
'runtimepath'. The result is that when a file is edited its indent file
is loaded (if there is one for the detected filetype).

Regards,
Alessandro

[1] http://vimdoc.sourceforge.net/htmldoc/filetype.html

[Vim-latex-devel] autoindent with vimlatex

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

Dear friends,
I am using vim-latex for a week, and never managed to have autoindent.
I added the line 
set sw=2 
in .vim/ftplugin/tex_latexSuite.vim as there is no tex.vim as told in
recommended settings
page(http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html)

my .vimrc looks:
 cat ~/.vimrc
set number
set autoindent
set smartindent
set hlsearch
set incsearch
set ignorecase
set smartcase
set novisualbell
set paste
set ruler
"set expandtab
"set smarttab
"set shiftwidth=1
"set softtabstop=3
"set mouse=a "enable mouse
"set nu "show line number
"set cul "highlight current line

if version >= 700
set spell spl=en_us
set nospell
nmap <F7> :set spell!
endif

" Fortran stuff
let fortran_do_enddo=1
let fortran_more_precise=1

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

syntax enable

please help.

Re: [Vim-latex-devel] Too much space around equations

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

David --

	In most cases, I get around this problem by making use of visual
selection. For example, hitting "v" at the top of the paragraph and then
using movement keys (e.g., cursor forward or } then cursor backward) to
isolate the section I want. Then I can "gw" that.

	If you're looking for something a little more exotic, I wrote this blog
post a while ago that I think might be applicable here:

http://phaseportrait.blogspot.com/2011/08/using-gobblepars-to-prevent-latex-from.html

You could add a \gobblepars (after defining it in your preamble) before
gaps, and LaTeX should ignore the \par automatically added by the gap.

	--Ted


On 08/23/2012 11:43 AM, David Adley wrote:
> Apologies for posting this here but I've looked everywhere online and
> it's a vim specific latex problem
> 
> When I write tex I separate out my paragraphs and equations as follows
> 
>     and then we find out that (end paragraph 1)
> 
>     \begin{equation}
>     z^2 = x^2 + y^y
>     \end{equation}
> 
>     (start paragraph 2) which is rather nice.
> 
> 
> This is so that I can use 'gwip' to format the paragraph before and
> after the equation without formatting the equation as well. However in
> latex the empty lines introduce \par tokens which adds extra space
> around the equation. I've tried eliminating the displayskip and
> shortskip lengths but there is still a large space around the equation
> due to the \par tokens. 
> 
> I know that the normal solution is to simply replace the empty line with
> a comment '%' but this will break the 'gwip' formatting.
> 
> Any ideas?
> David
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

[Vim-latex-devel] [ vim-latex-Patches-3562199 ] Permit spaces in okular forward search

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

Patches item #3562199, was opened at 2012-08-27 08:10
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3562199&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: Brian McCarter ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Permit spaces in okular forward search

Initial Comment:
Okular cannot execulate a forward search (\ls) if the tex or target file has whitespace in the file name.  This patch protects those file names with double quotes.

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

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

[Vim-latex-devel] Too much space around equations

[David A. <ad...@tc...>]

Apologies for posting this here but I've looked everywhere online and it's
a vim specific latex problem

When I write tex I separate out my paragraphs and equations as follows

and then we find out that (end paragraph 1)

\begin{equation}
z^2 = x^2 + y^y
\end{equation}

(start paragraph 2) which is rather nice.


This is so that I can use 'gwip' to format the paragraph before and after
the equation without formatting the equation as well. However in latex the
empty lines introduce \par tokens which adds extra space around the
equation. I've tried eliminating the displayskip and shortskip lengths but
there is still a large space around the equation due to the \par tokens.

I know that the normal solution is to simply replace the empty line with a
comment '%' but this will break the 'gwip' formatting.

Any ideas?
David

Re: [Vim-latex-devel] [Feature Requests]: Highlight matched pairs under the cursor

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

	At least for braces (as opposed to opening and closing environment
tags), you can use DoMatchParen, which comes with the standard plugin
pi_paren. Add:

:DoMatchParen

to your ~/.vimrc (or to an after/ftplugin/tex.vim file in your ~/.vim
directory). Alternatively, execute that in command mode directly. That
should give you brace matching. See:

:help DoMatchParen

for more information. ":help matchpairs" may also be helpful.

	Again, for braces, an alternative is to set:

:set showmatch

to briefly jump from one brace to another while typing.

	I think you know this already, but jumping (via %) works with
environments. You can jump from a \begin to the matching \end with %.
Likewise, you can fold on environments, which has a very similar feel.
Consequently, because jumping and folding already work on environments
and because many environments wander off the edge of a page, I don't
think there has been the demand for highlighting the matching closing
construct. I think it's possible though.

	--Ted

On 08/14/2012 05:14 AM, 蘇連傑 wrote:
> Dear developer,
> 
> We know that vim can highlight matched parentheses under the cursor,
> this feature help us to know which is the matched pair to the current
> one without a jump (e.g. %). Similiar to this feature, for HTML files
> there exist some plugin, e. g., [
> http://www.vim.org/scripts/script.php?script_id=3818 ] and [
> https://gist.github.com/1386336 ], for highlighting matched tags in
> html/xml file.
> 
> After using such plugins, an idea comes to my mind: why not let vim
> highlight matched pairs in LaTeX? Vim-latex can highlight mismatched
> standard environments as errors, but do not show a dynamic highlight
> when cursor moves. If such a feature can be added in some newer
> version, I will be very grateful. :) The matched pairs can be (mostly)
> environments, and \left \right pairs et al..
> 
> PS thanks for your greate jobs! :)
> 
> Su, greetings from China.
> 
> -- 
> 知识共享，世界大同……
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

Re: [Vim-latex-devel] [BUG REPORT]: highlight issue on inline equations

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

Syntax highlighting of TeX is not handled within vim-latex. The
syntax/tex.vim file is distributed with Vim.

Technically, vim-latex could release patches to syntax/tex.vim with
instructions to install in ~/.vim/after/syntax/, but the best solution
would be to take these bugs up with the maintainer of syntax/tex.vim
inside the Vim distribution.

When I view:

/usr/share/vim/vim73/syntax/tex.vim

on my system, the header says:

" Vim syntax file
" Language:     TeX
" Maintainer:   Dr. Charles E. Campbell, Jr.
<NdrchipO@ScampbellPfamily.AbizM>
" Last Change:  Apr 24, 2012
" Version:      73
" URL:
http://mysite.verizon.net/astronaut/vim/index.html#vimlinks_syntax

However, I also recommend that you take a look at some of the "Notes" in
the leading comments in that file. In particular,

"2. Run-on equations ($..$ and $$..$$, particularly) can also be stopped
by suitable use of %stopzone."

--Ted


On 08/14/2012 05:32 AM, 蘇連傑 wrote:
> Here [
> http://tex.stackexchange.com/questions/52235/vim-latex-with-strange-unwanted-highlighting
> ] is the same issue.
> 
> Although it was said that this is a bug of Ubuntu, but I have tested on
> Windows8 and Windows XP with the latest vim-latex (and gvim 7.3, of
> course), it still exists (see screenshot).
> 
> It is clearly that vim-latex failed on some match on `{}`, I think this
> is the reason of this issue.
> 
> -- 
> 知识共享，世界大同……
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

[Vim-latex-devel] How to call IMAP_JumpForward from a function?

[Jorge R. <sk...@gm...>]

Hi,

I have the imap
imap <silent> <NL> <Plug>IMAP_JumpForward
in after/ftplugin/tex.vim

but when not using latex, I use that key for ultisnips plugin
inoremap <silent> <NL> <c-r>=UltiSnips_ExpandSnippetOrJump()<CR>

I would like to do the following have a mapping that in latex would do
the following:
when I hit <c-j> it would just be like calling
imap <silent> <NL> <Plug>IMAP_JumpForward
but if the cursor doesn't move then call the function for ultisnips.

My initial problem is that I don't know how to call IMAP_JumpForward
from a function.
I have the following right now:

function! SelectImapOrUlti()
  let save_cursor = getpos(".")
  execute "normal \<Plug>IMAP_JumpForward"
  return ''
endfunction
imap <c-l> <c-r>=SelectImapOrUlti()<cr>

If I use the original mapping in text with the placeholders say
<+tag+> then the word tag and the placeholders
are selected visually and I can just delete them by hitting backspace.
If I use the mapping the mapping associated with the function I
defined the cursor just goes to the closing placeholder, but nothing
is selected.

Is there a way of achieving this?

Thanks!

[Vim-latex-devel] [BUG REPORT]: `<C-J>` IMAP_JumpForward issue on empty line

[<su...@gm...>]

I'm using gVim under windows, so here is what I do to reproduce this issue

`Win+R gvim foo.tex` to open a tex file, be sure vim-latex is loaded.
`i` to insert mode, `<F5>3<CR>` to insert a equation template.
Now, press <ENTER> for a newline in this equation environment, THEN, press
<C-J> to jump to the anchor in `\label{}`, you'll see that the default
placeholder is gone as we expected, ---but wait, something's wrong, a `<`
was left inside the `{}`.

My vim-latex is installed in the `bundle` folder, yes I'm pathogen user. :)

-- 
知识共享，世界大同……

[Vim-latex-devel] [Feature Requests]: Highlight matched pairs under the cursor

[<su...@gm...>]

Dear developer,

We know that vim can highlight matched parentheses under the cursor, this
feature help us to know which is the matched pair to the current one
without a jump (e.g. %). Similiar to this feature, for HTML files there
exist some plugin, e. g., [
http://www.vim.org/scripts/script.php?script_id=3818 ] and [
https://gist.github.com/1386336 ], for highlighting matched tags in
html/xml file.

After using such plugins, an idea comes to my mind: why not let vim
highlight matched pairs in LaTeX? Vim-latex can highlight mismatched
standard environments as errors, but do not show a dynamic highlight when
cursor moves. If such a feature can be added in some newer version, I will
be very grateful. :) The matched pairs can be (mostly) environments, and
\left \right pairs et al..

PS thanks for your greate jobs! :)

Su, greetings from China.

-- 
知识共享，世界大同……

[Vim-latex-devel] [ vim-latex-Patches-3551589 ] Improves indentation for 'begin'/'end' while several ones

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

Patches item #3551589, was opened at 2012-07-29 14:20
Message generated for change (Comment added) made by tpavlic
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3551589&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: Benoît Legat (blegat8)
Assigned to: Nobody/Anonymous (nobody)
Summary: Improves indentation for 'begin'/'end' while several ones

Initial Comment:
When several \end and/or \begin of environments lies on the same line, the indentation is not always relevant.
This patch tries to fix it with a little bit of refactoring too (the code for \begin and \end is refactored to one function).
I did some tests and it should normally work now for even the most extreme cases.

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

Comment By: Ted Pavlic (tpavlic)
Date: 2012-08-09 11:19

Message:
Looks OK to me. I'll commit it after a couple of minor changes.

1. Correct spelling of "Exemples" to "Examples" (do a search and replace in
the comments).

2. Correct spelling of "occurence" to "occurrence" (again, in the
comments).

3. Correct spelling of "substraction" to "subtraction" (comments).

4. (not that big of a deal; just for consideration) Change "parameters" to
"arguments" throughout comments.

5. (not that important, but just to consider) I don't really like using
"->" to mean "returns" as it already has a loaded meaning in CS as "gets."
Really, "HasEnv" is a predicate that is either asserted or not. So I'd
almost like to see something like...

"For example, both of the following are asserted (or you could say "true",
I suppose):

HasEnv( ..., ... )
! HasEnv( ..., ...)"

You could do something similar with BeginEnd using double equals in the
comments. Like:

"For example, all of the following are asserted (or, again, true, I
suppose):

BeginEnd( ..., ..., ...) == 1
BeginEnd( ..., ..., ...) == 1
BeginEnd( ..., ..., ...) == 2
BeginEnd( ..., ..., ...) == 0"

Make at least changes 1 through 3, and I'll commit your patch and push it.

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

Comment By: Gerd Wachsmuth (gerw)
Date: 2012-08-01 04:54

Message:
I've also tried to improve the indentation of multiple \begin and \end on
one line. See
https://github.com/gerw/vim-latex-suite/blob/master/indent/tex.vim

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

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

Re: [Vim-latex-devel] opening .aux file

[Christoffer D. <cd...@cs...>]

Hi Ted,

Thanks for your fast response!

On Thu, Aug 9, 2012 at 1:52 PM, Ted Pavlic <te...@te...> wrote:
> Christoffer --
>
>         Please review (including the "UPDATES" at the top):
>
> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>
> and see if you can gain some traction. The problem you're encountering
> is more a fundamental problem with how vim processes error messages. The
> kinds of error messages that LaTeX provides have scopes that span over
> several lines, and it is a little hard for vim to track sometimes.
> Consequently, sometimes it picks the wrong file.
>

I tried this, but unfortunately for some errors, the file is still the
.aux file, for example when defining multiple labels with the same
name.

I added a horrible hack to the vim-latex code though, which some might
benefit from, but there are surely much better ways to do it:


diff --git a/ftplugin/latex-suite/compiler.vim
b/ftplugin/latex-suite/compiler.vim
index 28213fa..d4552c2 100644
--- a/ftplugin/latex-suite/compiler.vim
+++ b/ftplugin/latex-suite/compiler.vim
@@ -784,6 +784,15 @@ endfunction " }}}
 "
 "   The position is both the correct line number and the column number.
 function! Tex_GotoErrorLocation(filename)
+	" HACK ALERT: Avoid opening the .aux file and piss off the author
+	let mainFileName_root = Tex_GetMainFileName(':p:t:r')
+	let auxFileName = escape(mainFileName_root.'.aux', '.')
+	let potAuxLine = getline('.')
+	" let pattern = auxFileName.'||.*'
+	if match(potAuxLine, auxFileName.'||.*') != -1
+		cclose
+		return
+	endif

 	" first use vim's functionality to take us to the location of the error
 	" accurate to the line (not column). This lets us go to the correct file
-- 
1.7.10


Best,
Christoffer

Re: [Vim-latex-devel] 1 little change for kbibtex users

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

I had some reservations over this change (primarily because I wasn't
sure what the grammar of BibTeX was), but I assume that your bibtex has
no trouble playing with spaces before key names... so I guess vim-latex
shouldn't either.

I've checked in your suggested fix (with a tip of the hat to you for
suggesting it).

--Ted

On 07/19/2012 01:25 PM, Simon wrote:
> I had the same probleme than here :
> http://ubuntuforums.org/showthread.php?t=952911
> and as I don't wand to edit my .bib each time kbibtex save the file, I
> change the ftplugin/latex-suite/bibtools.py file in order to allow space
> before the key of the bib entry :
> Line 32 :
> m = re.match(r'\s*@(\w+){((\S+),)?(.*)}\s*', txt,re.MULTILINE | re.DOTALL)
> I just add a \s* 
> m = re.match(r'\s*@(\w+){\s*((\S+),)?(.*)}\s*', txt, re.MULTILINE | re.DOTALL)
> 
> Maybe it can be a good idea to add it into the repository, I spend long
> time to find why I wasn't able to have this beautiful completion
> working, and it's not so much change to do :)
> 
> have a nice week!
> 
> Simon
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

Re: [Vim-latex-devel] opening .aux file

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

Christoffer --

	Please review (including the "UPDATES" at the top):

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

and see if you can gain some traction. The problem you're encountering
is more a fundamental problem with how vim processes error messages. The
kinds of error messages that LaTeX provides have scopes that span over
several lines, and it is a little hard for vim to track sometimes.
Consequently, sometimes it picks the wrong file.

	In many cases, simply adding "-file-line-error" (without the quotes) to
your LaTeX command line string will fix your problems. That doesn't fix
all of the warnings though. That's why you might want to try the
"vimlatex" wrapper described at the blog post above (which will be
easiest on a UNIX (or Mac) machine, but there is a Python port mentioned
there that should be OK on a Windows machine).

	--Ted

On 08/09/2012 09:30 AM, Christoffer Dall wrote:
> Hi vim-latex folks,
> 
> Thanks for the great work with vim-latex, it is an awesome piece of
> software.
> 
> My only problem is that when I have compile errors in my document, the
> .aux file is opened and the cursor jumps to that buffer. I find this
> very disrupting for my workflow and I am looking for a way to disable
> this feature. Can you help me out with this?
> 
> I run vim-latex on Mac OS X using MacVim using the setup
> at: https://github.com/chazy/vim-config
> 
> Thank you for your reponse,
> -Christoffer
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

[Vim-latex-devel] opening .aux file

[Christoffer D. <cd...@cs...>]

Hi vim-latex folks,

Thanks for the great work with vim-latex, it is an awesome piece of
software.

My only problem is that when I have compile errors in my document, the .aux
file is opened and the cursor jumps to that buffer. I find this very
disrupting for my workflow and I am looking for a way to disable this
feature. Can you help me out with this?

I run vim-latex on Mac OS X using MacVim using the setup at:
https://github.com/chazy/vim-config

Thank you for your reponse,
-Christoffer