vim-latex-devel

[Vim-latex-devel] Some problems with <F5>

[Manu H. <man...@gm...>]

Hi,

After I updated to Vim 7, I cannot use the <F5> command because if I add the
usepackage line, it appeared like

<++>]{amsmath}``usepackage[X

If I add an environment, it looked like

\begin{eqnarray*}
    "
\end{eqnarray*}<++>

There is " there and needed to delete it before starting to type.

Re: [Vim-latex-devel] Some problems with <F5>

[Christian E. <bla...@gm...>]

* Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400:
> After I updated to Vim 7, I cannot use the <F5> command because if I add the
> usepackage line, it appeared like
> 
> <++>]{amsmath}``usepackage[X

I can confirm this. Exept I get double quotes " instead of `` --
perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not
the cause I just toggled the setting to test.
 
> If I add an environment, it looked like
> 
> \begin{eqnarray*}
>     "
> \end{eqnarray*}<++>

Not here.

c
-- 
_B A U S T E L L E N_ lesen!  --->> <http://www.blacktrash.org/baustellen.html>

Re: [Vim-latex-devel] Some problems with <F5>

[Aditya M. <ad...@ii...>]

On Mon, 7 Aug 2006, Christian Ebert wrote:

> * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400:
>> After I updated to Vim 7, I cannot use the <F5> command because if I add the
>> usepackage line, it appeared like
>>
>> <++>]{amsmath}``usepackage[X
>
> I can confirm this. Exept I get double quotes " instead of `` --
> perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not
> the cause I just toggled the setting to test.

I also get this. I can not fully understand why this is happening, but 
here is a quick fix.

Open .vim/ftplugin/latex-suite/env-macros.tex and comment line 700

"      return Tex_pack_one(pack)

and add

       let a=Tex_pack_one(pack)
       return a

AFAIK, both these statements should be equivalent, but the second one 
gets rid of the problem.


>> If I add an environment, it looked like
>>
>> \begin{eqnarray*}
>>     "
>> \end{eqnarray*}<++>
>
> Not here.

enviornment inserts work fine here also.

Aditya

Re: [Vim-latex-devel] Some problems with <F5>

[Christian E. <bla...@gm...>]

* Aditya Mahajan on Monday, August 07, 2006 at 18:18:19 -0400:
> On Mon, 7 Aug 2006, Christian Ebert wrote:
>> * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400:
>>> After I updated to Vim 7, I cannot use the <F5> command because if I add the
>>> usepackage line, it appeared like
>>> 
>>> <++>]{amsmath}``usepackage[X
>> 
>> I can confirm this. Exept I get double quotes " instead of `` --
>> perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not
>> the cause I just toggled the setting to test.
> 
> I also get this. I can not fully understand why this is happening, but 
> here is a quick fix.
> 
> Open .vim/ftplugin/latex-suite/env-macros.tex and comment line 700
> 
> "      return Tex_pack_one(pack)
> 
> and add
> 
>        let a=Tex_pack_one(pack)
>        return a
> 
> AFAIK, both these statements should be equivalent, but the second one 
> gets rid of the problem.

Good for you. Here both statements indeed *are* equivalent, as
the second one does not get rid of the problem ;)

c
-- 
_B A U S T E L L E N_ lesen!  --->> <http://www.blacktrash.org/baustellen.html>

Re: [Vim-latex-devel] Some problems with <F5>

[Aditya M. <ad...@um...>]

On Tue, 8 Aug 2006, Christian Ebert wrote:

> * Aditya Mahajan on Monday, August 07, 2006 at 18:18:19 -0400:
>> On Mon, 7 Aug 2006, Christian Ebert wrote:
>>> * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400:
>>>> After I updated to Vim 7, I cannot use the <F5> command because if I add the
>>>> usepackage line, it appeared like
>>>>
>>>> <++>]{amsmath}``usepackage[X
>>>
>>> I can confirm this. Exept I get double quotes " instead of `` --
>>> perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not
>>> the cause I just toggled the setting to test.
>>
>> I also get this. I can not fully understand why this is happening, but
>> here is a quick fix.
>>
>> Open .vim/ftplugin/latex-suite/env-macros.tex and comment line 700
>>
>> "      return Tex_pack_one(pack)
>>
>> and add
>>
>>        let a=Tex_pack_one(pack)
>>        return a
>>
>> AFAIK, both these statements should be equivalent, but the second one
>> gets rid of the problem.
>
> Good for you. Here both statements indeed *are* equivalent, as
> the second one does not get rid of the problem ;)

Yes it does not. I was later testing with some other packages, and 
they work fine. The problem is still there when I try amsmath. 
Whenever a package has Tex_package_option_packname set I get the same 
error as you.

Sorry for the noise.

Aditya