vim-latex-devel

[Vim-latex-devel] GotoError=0 does not work for multiple files

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

Dear all

I am using vim-latex with a multiple-file project. Setting GotoError=0 only
prevents jumping to the first warning/error when the said warning is in the
file being currently edited. In any other case, the file currently open in
the window is systematically replaced by the file in which resides the first
warning/error.

I am using Vim 7.2, Windows 32 version, and my latex-suite version of
compiler.vim says :
CVS $Id: compiler.vim 997 2006-03-20 09:45:45Z sirathava$

Maybe the error is in compiler.vim, function Tex_SetupErrorWindow(), which
would badly handle the fact that the name of the edited file is not the same
as the file where the first bug resides ? Sorry, packing the writing of my
PhD thesis prevents me from learning vim-scripting to debug :-/

This question has already been asked almost 2 years ago, unfortunately
without answer (
http://sourceforge.net/mailarchive/message.php?msg_name=ebc50aa0704280044u39d0a089wc3da8092b65d214%40mail.gmail.com)

I really hope you'll be able to help me, my PhD advisor is already teasing
me for not using Winedit (sob ... I'm a vim martyr in this lab ;) )
Please let me know of any additional info you might need, and thanks for the
help !

Julien, struggling to import vim into his lab ;-)

Re: [Vim-latex-devel] GotoError=0 does not work for multiple files

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

I don't have a chance to generate an example to test this, but if you 
open your files in buffers, you might be OK.

IIRC, when an error occurs in another file that is already open in a 
buffer, that buffer is focused.

If you get used to editing projects in buffers (e.g., vim *.tex), then I 
*think* that latex suite features will be more convenient.

--Ted

On 1/6/09 1:19 PM, Julien Cornebise wrote:
> Dear all
>
> I am using vim-latex with a multiple-file project. Setting GotoError=0
> only prevents jumping to the first warning/error when the said warning
> is in the file being currently edited. In any other case, the file
> currently open in the window is systematically replaced by the file in
> which resides the first warning/error.
>
> I am using Vim 7.2, Windows 32 version, and my latex-suite version of
> compiler.vim says :
> CVS $Id: compiler.vim 997 2006-03-20 09:45:45Z sirathava$
>
> Maybe the error is in compiler.vim, function Tex_SetupErrorWindow(),
> which would badly handle the fact that the name of the edited file is
> not the same as the file where the first bug resides ? Sorry, packing
> the writing of my PhD thesis prevents me from learning vim-scripting to
> debug :-/
>
> This question has already been asked almost 2 years ago, unfortunately
> without answer
> (http://sourceforge.net/mailarchive/message.php?msg_name=ebc50aa0704280044u39d0a089wc3da8092b65d214%40mail.gmail.com
> )
>
> I really hope you'll be able to help me, my PhD advisor is already
> teasing me for not using Winedit (sob ... I'm a vim martyr in this lab ;) )
> Please let me know of any additional info you might need, and thanks for
> the help !
>
> Julien, struggling to import vim into his lab ;-)
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

Re: [Vim-latex-devel] GotoError=0 does not work for multiple files

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

I have not even tried to find a way to stop LatexSuite from jumping to
files with errors.  I thought about it for a couple seconds, and then
realized that I can just CTRL-O to undo that jump, just as you can use
CTRL-O and CTRL-I to undo and redo most kinds of jumps.

Hopefully that will save you some time and let you focus on your Ph.D.
thesis, which is obviously much more important.

-Mike Richman

P.S.  I lol'd at the idea of someone using Winedit teasing someone
using vim!

On Wed, Jan 7, 2009 at 4:48 AM, Julien Cornebise
<jul...@gm...> wrote:
> Hi Ted
>
> Thanks for your fast answer. The problem persists when editing projects in
> buffers (which I alerady did, through tabs, and now do through "pure"
> buffers).
>
> Included is a complete minimal example :
> 0. let g:Tex_GotoError=0 in the .vimrc
> 1. open the two files "main.tex" and "intro.tex" in two buffers of the same
> window
> 2. set intro.tex the current buffer (and ":set ft=tex" for LatexSuite to be
> loaded, the file seems too short to be correctly autodetected as a latex
> file), stay on first line
> 3. compile with \ll : no problem, the cursor does not jump to the line with
> the warning
> 4. now make main.tex the current buffer
> 5. compile with \ll
> 6. *hop*, here pops intro.tex as the active buffer, cursor on the line with
> the warning.
>
> I would so much like to *always* stay in the same buffer that I was editing
> (as Tex_GotoError=0 should do, as far as I understand the doc) -- in this
> case, this is a minor warning that I will get rid of latr.
>
> Thanks for the time you spend on this problem !
>
> Julien
>
> On Tue, Jan 6, 2009 at 8:42 PM, Ted Pavlic <te...@te...> wrote:
>>
>> I don't have a chance to generate an example to test this, but if you open
>> your files in buffers, you might be OK.
>>
>> IIRC, when an error occurs in another file that is already open in a
>> buffer, that buffer is focused.
>>
>> If you get used to editing projects in buffers (e.g., vim *.tex), then I
>> *think* that latex suite features will be more convenient.
>>
>> --Ted
>>
>> On 1/6/09 1:19 PM, Julien Cornebise wrote:
>>>
>>> Dear all
>>>
>>> I am using vim-latex with a multiple-file project. Setting GotoError=0
>>> only prevents jumping to the first warning/error when the said warning
>>> is in the file being currently edited. In any other case, the file
>>> currently open in the window is systematically replaced by the file in
>>> which resides the first warning/error.
>>>
>>> I am using Vim 7.2, Windows 32 version, and my latex-suite version of
>>> compiler.vim says :
>>> CVS $Id: compiler.vim 997 2006-03-20 09:45:45Z sirathava$
>>>
>>> Maybe the error is in compiler.vim, function Tex_SetupErrorWindow(),
>>> which would badly handle the fact that the name of the edited file is
>>> not the same as the file where the first bug resides ? Sorry, packing
>>> the writing of my PhD thesis prevents me from learning vim-scripting to
>>> debug :-/
>>>
>>> This question has already been asked almost 2 years ago, unfortunately
>>> without answer
>>>
>>> (http://sourceforge.net/mailarchive/message.php?msg_name=ebc50aa0704280044u39d0a089wc3da8092b65d214%40mail.gmail.com
>>> )
>>>
>>> I really hope you'll be able to help me, my PhD advisor is already
>>> teasing me for not using Winedit (sob ... I'm a vim martyr in this lab ;)
>>> )
>>> Please let me know of any additional info you might need, and thanks for
>>> the help !
>>>
>>> Julien, struggling to import vim into his lab ;-)
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It is the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://p.sf.net/sfu/Xq1LFB
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>> --
>> Ted Pavlic <te...@te...>
>
>
> ------------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

Re: [Vim-latex-devel] GotoError=0 does not work for multiple files

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

Sounds like an elegant solution!

Additionally, if you want to prevent Vim-LaTeX from jumping to the WRONG 
file, see:

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

That way if you actually do get an error in the current file that's 
opened, Vim will be less likely to open some unrelated file. Instead, it 
will bring you to the offending line in the current file.

(to make a long story short, the default Lisp-like syntax of LaTeX 
status messages confuses Vim when there are multiple closures next to 
each other)

--Ted


On 1/7/09 12:21 PM, Mike Richman wrote:
> I have not even tried to find a way to stop LatexSuite from jumping to
> files with errors.  I thought about it for a couple seconds, and then
> realized that I can just CTRL-O to undo that jump, just as you can use
> CTRL-O and CTRL-I to undo and redo most kinds of jumps.
>
> Hopefully that will save you some time and let you focus on your Ph.D.
> thesis, which is obviously much more important.

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

Re: [Vim-latex-devel] GotoError=0 does not work for multiple files

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

Thank you very much to both of you for the help !
I ignored that Ctrl-O worked also between buffers, thanks.

Julien

On Wed, Jan 7, 2009 at 6:33 PM, Ted Pavlic <te...@te...> wrote:
> Sounds like an elegant solution!
>
> Additionally, if you want to prevent Vim-LaTeX from jumping to the WRONG
> file, see:
>
> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>
> That way if you actually do get an error in the current file that's
> opened, Vim will be less likely to open some unrelated file. Instead, it
> will bring you to the offending line in the current file.
>
> (to make a long story short, the default Lisp-like syntax of LaTeX
> status messages confuses Vim when there are multiple closures next to
> each other)
>
> --Ted
>
>
> On 1/7/09 12:21 PM, Mike Richman wrote:
>> I have not even tried to find a way to stop LatexSuite from jumping to
>> files with errors.  I thought about it for a couple seconds, and then
>> realized that I can just CTRL-O to undo that jump, just as you can use
>> CTRL-O and CTRL-I to undo and redo most kinds of jumps.
>>
>> Hopefully that will save you some time and let you focus on your Ph.D.
>> thesis, which is obviously much more important.
>
> --
> Ted Pavlic <te...@te...>
>
> ------------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>