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

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

[Manuel Pégourié-G. <mp...@el...>]

Julien Cornebise a écrit :
> Some are reading us (hi Manuel): they are  *everywhere* ! ;-)
> Still, I can see their point.
> 
Hey, I'm not a ConTeXtualist, I only attend ConTeXt meetings for the
nice people, the mountains and the Czech beer :-)

Still, LaTeX is actually the most widespread TeX format, I think it
should be the default, but anyway.

Manuel.

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
>

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

[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

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

> In particular, when Vim7 came out, after some lobbying from ConTeXtualists
> and TeX purists,

Some are reading us (hi Manuel): they are  *everywhere* ! ;-)
Still, I can see their point.

> So you're actually short-circuiting Vim7 with that setting.

Clever short-circuit, thanks !

Julien

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

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

>> let g:tex_flavor='latex'
>
> Sorry, my very mistake ! I had incorrectly capitalized it the texsuite
> way (i.e. let g:Tex_Flavor). It now works as angel. All my apologies,
> and all my thanks :)

It's interesting to note that "tex_flavor" has nothing to do with the 
LaTeX-Suite, and that's why the capitalization convention is broken.

In particular, when Vim7 came out, after some lobbying from 
ConTeXtualists and TeX purists, it was decided that it was cruel and 
unusual for Vim7 to default to assuming that tex files were LaTeX. So 
instead they added that silly "see if we can find some LaTeX code, and 
otherwise default to plain tex".

So you're actually short-circuiting Vim7 with that setting.

--Ted

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

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

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

> That's interesting. It works for me. That is, I have
> let g:tex_flavor='latex'

Sorry, my very mistake ! I had incorrectly capitalized it the texsuite
way (i.e. let g:Tex_Flavor). It now works as angel. All my apologies,
and all my thanks :)

> Additionally, if you haven't figured this out already (I assume you have),
(...)
> \ll would build main.tex.

Thanks, I already had found this (very useful indeed). Besides, it
also works for me when using either "main.latexmain" or
"main.tex.latexmain".

Many thanks for your help.

Julien

PS: Sorry Ted for double posting the first part.

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

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

>> If you put let g:tex_flavor='latex'
>> into your .vimrc, then you'll never have to ":set ft=tex" again.
>
> Thank you, but it does not seem to help the small file intro.tex
> trigger the launch of Latex-Suite when I open it. Anyway, this is a
> minor problem, as I rarely have such small files (though I agree this
> is intriguing).

That's interesting. It works for me. That is, I have

let g:tex_flavor='latex'

in my .vimrc, and even if I open an *empty* file that ends in .tex, 
Latex-Suite is loaded. In fact, just yesterday I had a colleague at that 
to his .vimrc to fix exactly the problem you were having and it did on 
his next Vim load.

Additionally, if you haven't figured this out already (I assume you 
have), as long as you have a file ending in ".latexmain" and starting 
with the root of the file that latex should build, doing "\ll" 
*anywhere* in that directory will cause Vim-LaTeX to build the right file.

For example, I might have a main.tex and an included.tex. I would touch 
a file called main.latexmain, and then from either main.tex or 
included.tex, \ll would build main.tex.

--Ted


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

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

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

> I'll try to comment on the other parts of the message later today,

thanks !

> If you put let g:tex_flavor='latex'
> into your .vimrc, then you'll never have to ":set ft=tex" again.

Thank you, but it does not seem to help the small file intro.tex
trigger the launch of Latex-Suite when I open it. Anyway, this is a
minor problem, as I rarely have such small files (though I agree this
is intriguing).

Julien

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

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

I'll try to comment on the other parts of the message later today, but 
in the meanwhile...

> 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

If you put:

	let g:tex_flavor='latex'

into your .vimrc, then you'll never have to ":set ft=tex" again.

--Ted

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

[Vim-latex-devel] Feature suggestion: distinct tw for normal/math modes

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

Dear all,

I suggest this feature to be added : allow two distinct "tw" settings for
normal and math modes.

Personnally, I often want my paragraphsto be tw=72, but to wrap my math
formulas myself (i.e. tw=0), regardless of the length of line -- some
intricate math expressions can sometimes be more appreciated on a very long
line by themselves, when the things around matter more.

I don't know how easy this is to implement, though.
Best, and thanks for this great tool !

Julien

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...>

[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] UNSUBSCRIBE

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

See the footer of every Vim-LaTeX message.

https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Use the on-line tool to unsubscribe. You're the only one reading the 
list who has the authority to remove you from it.

On 1/5/09 9:18 AM, Schneeberger Niklaus wrote:
>
>

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

Re: [Vim-latex-devel] multiple file project - (\ll) can't find main.tex

[Michael T. <mic...@gm...>]

Hi,

I found the error, which might have been difficult to figure out from my
previous mail.

I had put

let g:Tex_CompileRule_dvi = 'latex -src-specials -interaction=nonstopmode %'

and now changed it to:

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

Thanks for the help!

Michael



On Mon, Jan 5, 2009 at 2:52 PM, Ted Pavlic <te...@te...> wrote:

> Alternatively, if you drop a Makefile in the directory, Vim-LaTeX will use
> it instead. It builds with "make (target_format)" where (target_format) is
> pdf, dvi, or ps.
>
> --Ted
>
>
> On 1/5/09 8:50 AM, Ted Pavlic wrote:
>
>> main.tex.latexmain
>>>>
>>>
>> Use
>>
>> main.latexmain
>>
>> (not main.tex.latexmain)
>>
>>
>> --Ted
>>
>>
>>
> --
> Ted Pavlic <te...@te...>
>

Re: [Vim-latex-devel] multiple file project - (\ll) can't find main.tex

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

Alternatively, if you drop a Makefile in the directory, Vim-LaTeX will 
use it instead. It builds with "make (target_format)" where 
(target_format) is pdf, dvi, or ps.

--Ted

On 1/5/09 8:50 AM, Ted Pavlic wrote:
>>> main.tex.latexmain
>
> Use
>
> main.latexmain
>
> (not main.tex.latexmain)
>
>
> --Ted
>
>

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

Re: [Vim-latex-devel] multiple file project - (\ll) can't find main.tex

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

>>main.tex.latexmain

Use

main.latexmain

(not main.tex.latexmain)


--Ted


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

[Vim-latex-devel] multiple file project - (\ll) can't find main.tex

[Michael T. <mic...@gm...>]

Dear,

when compiling, the main file of a multiple file project isn't found.
However, viewing or forward searching does work (main.dvi is
displayed).

directory structure:
main/
>main.tex

>main.tex.latexmain
>a/
>>a.tex
>b/
>>b.tex

below main.tex:
\documentclass[a4paper]{article}
\begin{document}
\input{a/a.tex}
\input{b/b.tex}
\end{document}

I'm working on Linux:

Linux pc5347 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT 2006 i686
i686 i386 GNU/Linux

Can anybody help?

thanks,

Michael

[Vim-latex-devel] vim-latex treats bibtex fields case sensitive

[Nicholas P. <Nic...@ni...>]

Hi,

First of all thanks for the great plugin!

Hovewer, I am using vim-latex in combination with Bibdesk for OSX  
which capitalizes field names. This shouldn't be a problem as these  
field names should be treated case insensitive. However, vim-latex  
doesn't. It can be easily fixed by changing line 46 in bibtools.py:

from: field = m.group(1)
to: field = m.group(1).lower()

This also means that all subsequent calls to lower() are redundant and  
can be removed. Without this patch vim-latex will find the entry but  
it cannot view the specifics or filter on them.

Kind regards,
Nicholas

-- 
A small patch:

--- bibtools.py.old	2008-12-22 11:22:51.000000000 +0100
+++ bibtools.py	2008-12-22 11:25:18.000000000 +0100
@@ -43,7 +43,7 @@
              if not m:
                  break

-            field = m.group(1)
+            field = m.group(1).lower()

              body = body[(m.start(2)+1):]
              if m.group(2) == '{':
@@ -90,7 +90,7 @@
              body = body[(mn.start(0)+1):]

              self['bodytext'] += ('  %s: %s\n' % (field, value))
-            if self['bibtype'].lower() == 'string':
+            if self['bibtype'] == 'string':
                  self['macro'] = {field: value}

          self['bodytext'] = self['bodytext'].rstrip()
@@ -103,34 +103,34 @@
              return ''

      def __str__(self):
-        if self['bibtype'].lower() == 'string':
+        if self['bibtype'] == 'string':
              return 'String: %(macro)s' % self

-        elif self['bibtype'].lower() == 'article':
+        elif self['bibtype'] == 'article':
              return ('Article [%(key)s]\n' +
                      'TI "%(title)s"\n' +
                      'AU %(author)s\n' +
                      'IN In %(journal)s, %(year)s') % self

-        elif self['bibtype'].lower() == 'conference':
+        elif self['bibtype'] == 'conference':
              return ('Conference [%(key)s]\n' +
                      'TI "%(title)s"\n' +
                      'AU %(author)s\n' +
                      'IN In %(booktitle)s, %(year)s') % self

-        elif self['bibtype'].lower() == 'mastersthesis':
+        elif self['bibtype'] == 'mastersthesis':
              return ('Masters [%(key)s]\n' +
                      'TI "%(title)s"\n' +
                      'AU %(author)s\n' +
                      'IN In %(school)s, %(year)s') % self

-        elif self['bibtype'].lower() == 'phdthesis':
+        elif self['bibtype'] == 'phdthesis':
              return ('PhD [%(key)s]\n' +
                      'TI "%(title)s"\n' +
                      'AU %(author)s\n' +
                      'IN In %(school)s, %(year)s') % self

-        elif self['bibtype'].lower() == 'book':
+        elif self['bibtype'] == 'book':
              return ('Book [%(key)s]\n' +
                      'TI "%(title)s"\n' +
                      'AU %(author)s\n' +

Re: [Vim-latex-devel] Spell-check not working with latex-suite

[Raffi K. <kha...@cs...>]

Eyolf Østrem <eyolf <at> oestrem.com> writes: 
> I've discovered that the built-in spell checker in vim doesn't work if
> ft=tex is set. It's not just the syntax highlighting -- ]s doesn't jump to
> the next spelling mistake.

Has anyone ever found a solution to this?

Re: [Vim-latex-devel] auto indentation advice,

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

> For example, if I type:
> \section{blah} \label{sec:blah},
> I find latex-suite indenting the block for me, when I don't want it.

When I type that, LaTeX suite does nothing. My cursor sits at the end of 
that line. If I hit return, I'm brought to the beginning of the next line.

So I don't notice any section-indenting with LaTeX-suite.

Can you give a more complete example?

> Is there a way of disabling these actions? Or is there a setting that
> will make latexsuite indent the way I want it to?

What way do you want LaTeX to indent?

You can turn off auto-indenting with:

:set noai

You can also tune the indentation spacing and whether or not to use tabs.

--Ted


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

[Vim-latex-devel] Tiny patch to handle spaces in .bib files

[yabo <ya...@lr...>]

Hello,

I've been using vim-latex for a while and was always annoyed by the
problem of spaces in .bib entries like :

@InProceedings{   key,
...

This was not handled properly and completly broke auto-completion.

I propose this tiny patch that solves the problem :

$ diff -u bibtools.old.py bibtools.py
--- bibtools.old.py     2008-11-19 15:33:22.000000000 +0100
+++ bibtools.py 2008-11-19 15:29:31.000000000 +0100
@@ -28,7 +28,7 @@
             for k, v in macros.iteritems():
                 txt = txt.replace(k, '{'+v+'}')

-        m = re.match(r'\s*@(\w+){((\S+),)?(.*)}\s*', txt, re.MULTILINE
| re.DOTALL)
+        m = re.match(r'\s*@(\w+){\s*((\S+),)?(.*)}\s*', txt,
re.MULTILINE | re.DOTALL)
         if not m:
             return None

$

Thanks for this great plugin :)

-- 
yabo

[Vim-latex-devel] auto indentation advice,

[Soroosh Y. <sya...@ma...>]

Hi,

first of all, thanks for the vim latex suite. This is probably one of
the most useful packages I have ever installed on my computer. I have
a question regarding the auto indentation though. I find it useful to
indent, say \section and \subsections,
and I find myself arguing with VIM regularly when it decides to
automatically indent or unindent the blocks for me.

For example, if I type:
\section{blah} \label{sec:blah},
I find latex-suite indenting the block for me, when I don't want it.

Is there a way of disabling these actions? Or is there a setting that
will make latexsuite indent the way I want it to?

Cheers,
Soroosh

Re: [Vim-latex-devel] Math mode: how to disable textwrap

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

> Is there a way to automatically set tw=0 when entering math mode, and
> resetting it to whatever it was (e.g. 72)  when exiting math mode ?
> That's a feature I'd love to have (didn't found it in the manual) :
> long mathematical equations are usually much easier to read when not
> automatically wrapped.
> 
> Is there any easy way to do so ?

I don't know HOW, but I think I know where you should start looking.


**Idea 1** In Vim, you can use "autocmd" to automatically fire off a 
command on a specific event. Try:

	:help autocmd

Ideally, you would like entering mathmode to trigger some event, and Vim 
would fire off an autocmd. Exiting mathmode would turn off that event.


**Idea 2** Do you use the LaTeX-Suite IMAP macros to enter equations? 
For example, do you type EEQ to start a new equation environment?

If you do, you could redefine EEQ to not only build the equation 
environment and reposition the cursor but *ALSO* turn off wrapping. You 
could then define some other combination to turn wrapping back ON and 
issue the Cntrl+J that brings you to the final <++> placeholder.


I hope someone else has some better ideas for you. Personally, I either...

*) deal with it and issue SHIFT+J's whenever I need to join lines

OR

*) Turn on paste mode (:set paste) and then turn it off when I'm done 
(:set nopaste).

	--Ted 	


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

[Vim-latex-devel] Math mode: how to disable textwrap

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

Dear all,

Is there a way to automatically set tw=0 when entering math mode, and
resetting it to whatever it was (e.g. 72)  when exiting math mode ?
That's a feature I'd love to have (didn't found it in the manual) :
long mathematical equations are usually much easier to read when not
automatically wrapped.

Is there any easy way to do so ?

Thanks for any feedback,

Julien