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

Re: [Vim-latex-devel] compiling with wrong cross-references

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

Felipe --

	One last note. It turns out that the most recent versions of many latex 
implementations have a flag that can fix this problem for you.

	Check out:

http://linuxwisdom.blogspot.com/2007/08/fixing-latex-suites-jump-to-error.html

In short, you add:

-file-line-error

to your LaTeX build line. You then add:

setlocal efm+=%E%f:%l:\ %m

to your .vim/compiler/tex.vim

file around line 202 (see the link for the exact location).

	--Ted

Felipe G. Nievinski wrote:
> Hi.
> 
> When I'm compiling a .tex file with wrong cross-references (\label{} 
> followed by \ref{}), I get a warning message indicating the offending 
> reference (which I find useful) but then my .tex file gets replaced in 
> vim with the corresponding .lox file (which I find annoying).
> 
> - Is that a bug or a feature? =)
> 
> Thanks,
> Felipe.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

Re: [Vim-latex-devel] compiling with wrong cross-references

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

If you find yourself ":bd"ing very often (for example, for some reason 
your TeX file gets buried or you :bd the wrong window or something like 
that, you might want to use some of the other buffer commands.

Check out:

:help :b

In particular, try things like:

:b file

where "file" is enough of the filename to match it (e.g., the first few 
characters). Or:

:b2

where "2" is the number of your buffer. In particular, your TeX buffer 
will PROBABLY always be 1, so:

:b1

might be the best choice. You COULD even map that to a special key...

:map <F2> :b1<CR>

will make F2 (in command mode) always bring you to the first buffer.

--Ted


Felipe G. Nievinski wrote:
> Oh, :bd is great! Thanks, Felipe.
> 
> Ted Pavlic wrote:
>> Note that the lox file should be brought up in a new *buffer*. That
>> is, you should be able to do
>> 
>> :ls
>> 
>> and see both your original source and the old TeX. Issuing the
>> command:
>> 
>> :bd
>> 
>> should delete the new buffer and bring you back to your original
>> TeX (in most cases). If I'm ever on a machine that doesn't have
>> vimlatex installed, I find myself issuing ":bd" over and over again
>> until I get back to the original TeX.
>> 
>> 
>> Alternatively, you can tell Vim to not pay attention to compiler
>> error messages (or to ignore all but a very very small set of
>> them). Though, if you like the error messages, then that won't be a
>> good thing to do. :)
>> 
>> 
>> --Ted
>> 
>> 
>> Felipe G. Nievinski wrote:
>>> Hi Ted. Thank you for the detailed reply. I think I'll keep
>>> splitting the vim window so that I can close the .lox file when
>>> it's brought up. (I hear you say, "Lazy this guy, eh?"... =)
>>> Thanks for the answer, though. Felipe.
>>> 
>>> Ted Pavlic wrote:
>>>> Check out:
>>>> 
>>>> http://links.tedpavlic.com/shell_scripts/vimlatex
>>>> 
>>>> and/or
>>>> 
>>>> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> LaTeX error messages have an interesting format. They use 
>>>> parentheses to start a block of error messages. For example...
>>>> 
>>>> (file1.tex
>>>> 
>>>> (file2.tex included from file1.tex information message posted
>>>> from file2.tex)
>>>> 
>>>> error from file1.tex
>>>> 
>>>> )
>>>> 
>>>> When parsing these error messages, the parser has to keep track
>>>> of which "block" it's in. Vim's error parsing engine can handle
>>>> this up until the point where there are multiple closing
>>>> parentheses on one line. That is, if three blocks are closed at
>>>> once with ")))" on one line, Vim will only see the first
>>>> parentheses. So, when an error message from file3 comes up,
>>>> sometimes Vim THINKS it's an error message for file2.
>>>> 
>>>> 
>>>> The only good Vim fix to this problem is to pipe the LaTeX
>>>> process through a filter that prevents parentheses from
>>>> stacking up. The "vimlatex" script above will do that.
>>>> Unfortunately, I've only had a chance to implement that script
>>>> for UNIX-like systems. Your e-mail looks like it was generated
>>>> with Thunderbird for Windows, so I'm guessing that you're a
>>>> Windows user. If that's the case, then you'll have to find a
>>>> Windows-compatible way to do the same thing. One solution would
>>>> be to install a few UNIX utilities that have been compiled for
>>>> Windows. Namely:
>>>> 
>>>> *) bash *) sed
>>>> 
>>>> If those two are available, you'll be able to use bash to
>>>> execute that "vimlatex" script.
>>>> 
>>>> 
>>>> To reconfigure Vim to use the vimlatex pipe, you'll have to add
>>>> a line to your .vimrc. See the LaTeX suite manual:
>>>> 
>>>> :help latex-suite
>>>> 
>>>> In particular, try:
>>>> 
>>>> :help compiler-rules
>>>> 
>>>> for more information. You'll have to use a line like...
>>>> 
>>>> let g:Tex_CompileRule_dvi = 'vimlatex latex 
>>>> -interaction=nonstopmode $*'
>>>> 
>>>> or, if you need to prefix it with bash:
>>>> 
>>>> let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex 
>>>> -interaction=nonstopmode $*'
>>>> 
>>>> 
>>>> Does that get you on the right track?
>>>> 
>>>> --Ted
>>>> 
>>>> 
>>>> 
>>>> Felipe G. Nievinski wrote:
>>>>> Hi.
>>>>> 
>>>>> When I'm compiling a .tex file with wrong cross-references 
>>>>> (\label{} followed by \ref{}), I get a warning message
>>>>> indicating the offending reference (which I find useful) but
>>>>> then my .tex file gets replaced in vim with the corresponding
>>>>> .lox file (which I find annoying).
>>>>> 
>>>>> - Is that a bug or a feature? =)
>>>>> 
>>>>> Thanks, Felipe.
>>>>> 
>>>>> -------------------------------------------------------------------------
>>>>> 
>>>>> 
>>>>> This SF.net email is sponsored by: Microsoft Defy all 
>>>>> challenges. Microsoft(R) Visual Studio 2008. 
>>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
>>>>> _______________________________________________
>>>>> Vim-latex-devel mailing list
>>>>> Vim...@li... 
>>>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>>> 
>>> 
> 
> 

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

Re: [Vim-latex-devel] compiling with wrong cross-references

[Felipe G. N. <fgn...@te...>]

Oh, :bd is great!
Thanks,
Felipe.

Ted Pavlic wrote:
> Note that the lox file should be brought up in a new *buffer*. That is, 
> you should be able to do
> 
> :ls
> 
> and see both your original source and the old TeX. Issuing the command:
> 
> :bd
> 
> should delete the new buffer and bring you back to your original TeX (in 
> most cases). If I'm ever on a machine that doesn't have vimlatex 
> installed, I find myself issuing ":bd" over and over again until I get 
> back to the original TeX.
> 
> 
> Alternatively, you can tell Vim to not pay attention to compiler error 
> messages (or to ignore all but a very very small set of them). Though, 
> if you like the error messages, then that won't be a good thing to do. :)
> 
> 
> --Ted
> 
> 
> Felipe G. Nievinski wrote:
>> Hi Ted. Thank you for the detailed reply. I think I'll keep splitting
>> the vim window so that I can close the .lox file when it's brought
>> up. (I hear you say, "Lazy this guy, eh?"... =) Thanks for the
>> answer, though. Felipe.
>>
>> Ted Pavlic wrote:
>>> Check out:
>>>
>>> http://links.tedpavlic.com/shell_scripts/vimlatex
>>>
>>> and/or
>>>
>>> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html 
>>>
>>>
>>>
>>>
>>>
>>> LaTeX error messages have an interesting format. They use
>>> parentheses to start a block of error messages. For example...
>>>
>>> (file1.tex
>>>
>>> (file2.tex included from file1.tex information message posted from
>>> file2.tex)
>>>
>>> error from file1.tex
>>>
>>> )
>>>
>>> When parsing these error messages, the parser has to keep track of
>>> which "block" it's in. Vim's error parsing engine can handle this
>>> up until the point where there are multiple closing parentheses on
>>> one line. That is, if three blocks are closed at once with ")))" on
>>> one line, Vim will only see the first parentheses. So, when an
>>> error message from file3 comes up, sometimes Vim THINKS it's an
>>> error message for file2.
>>>
>>>
>>> The only good Vim fix to this problem is to pipe the LaTeX process
>>>  through a filter that prevents parentheses from stacking up. The 
>>> "vimlatex" script above will do that. Unfortunately, I've only had
>>> a chance to implement that script for UNIX-like systems. Your
>>> e-mail looks like it was generated with Thunderbird for Windows, so
>>> I'm guessing that you're a Windows user. If that's the case, then
>>> you'll have to find a Windows-compatible way to do the same thing.
>>> One solution would be to install a few UNIX utilities that have
>>> been compiled for Windows. Namely:
>>>
>>> *) bash *) sed
>>>
>>> If those two are available, you'll be able to use bash to execute
>>> that "vimlatex" script.
>>>
>>>
>>> To reconfigure Vim to use the vimlatex pipe, you'll have to add a
>>> line to your .vimrc. See the LaTeX suite manual:
>>>
>>> :help latex-suite
>>>
>>> In particular, try:
>>>
>>> :help compiler-rules
>>>
>>> for more information. You'll have to use a line like...
>>>
>>> let g:Tex_CompileRule_dvi = 'vimlatex latex
>>> -interaction=nonstopmode $*'
>>>
>>> or, if you need to prefix it with bash:
>>>
>>> let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex 
>>> -interaction=nonstopmode $*'
>>>
>>>
>>> Does that get you on the right track?
>>>
>>> --Ted
>>>
>>>
>>>
>>> Felipe G. Nievinski wrote:
>>>> Hi.
>>>>
>>>> When I'm compiling a .tex file with wrong cross-references
>>>> (\label{} followed by \ref{}), I get a warning message indicating
>>>> the offending reference (which I find useful) but then my .tex
>>>> file gets replaced in vim with the corresponding .lox file (which
>>>> I find annoying).
>>>>
>>>> - Is that a bug or a feature? =)
>>>>
>>>> Thanks, Felipe.
>>>>
>>>> ------------------------------------------------------------------------- 
>>>>
>>>>  This SF.net email is sponsored by: Microsoft Defy all
>>>> challenges. Microsoft(R) Visual Studio 2008. 
>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
>>>> _______________________________________________ Vim-latex-devel
>>>> mailing list Vim...@li... 
>>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>>
>>
>>
> 

Re: [Vim-latex-devel] compiling with wrong cross-references

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

Note that the lox file should be brought up in a new *buffer*. That is, 
you should be able to do

:ls

and see both your original source and the old TeX. Issuing the command:

:bd

should delete the new buffer and bring you back to your original TeX (in 
most cases). If I'm ever on a machine that doesn't have vimlatex 
installed, I find myself issuing ":bd" over and over again until I get 
back to the original TeX.


Alternatively, you can tell Vim to not pay attention to compiler error 
messages (or to ignore all but a very very small set of them). Though, 
if you like the error messages, then that won't be a good thing to do. :)


--Ted


Felipe G. Nievinski wrote:
> Hi Ted. Thank you for the detailed reply. I think I'll keep splitting
> the vim window so that I can close the .lox file when it's brought
> up. (I hear you say, "Lazy this guy, eh?"... =) Thanks for the
> answer, though. Felipe.
> 
> Ted Pavlic wrote:
>> Check out:
>> 
>> http://links.tedpavlic.com/shell_scripts/vimlatex
>> 
>> and/or
>> 
>> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>> 
>> 
>> 
>> 
>> LaTeX error messages have an interesting format. They use
>> parentheses to start a block of error messages. For example...
>> 
>> (file1.tex
>> 
>> (file2.tex included from file1.tex information message posted from
>> file2.tex)
>> 
>> error from file1.tex
>> 
>> )
>> 
>> When parsing these error messages, the parser has to keep track of
>> which "block" it's in. Vim's error parsing engine can handle this
>> up until the point where there are multiple closing parentheses on
>> one line. That is, if three blocks are closed at once with ")))" on
>> one line, Vim will only see the first parentheses. So, when an
>> error message from file3 comes up, sometimes Vim THINKS it's an
>> error message for file2.
>> 
>> 
>> The only good Vim fix to this problem is to pipe the LaTeX process
>>  through a filter that prevents parentheses from stacking up. The 
>> "vimlatex" script above will do that. Unfortunately, I've only had
>> a chance to implement that script for UNIX-like systems. Your
>> e-mail looks like it was generated with Thunderbird for Windows, so
>> I'm guessing that you're a Windows user. If that's the case, then
>> you'll have to find a Windows-compatible way to do the same thing.
>> One solution would be to install a few UNIX utilities that have
>> been compiled for Windows. Namely:
>> 
>> *) bash *) sed
>> 
>> If those two are available, you'll be able to use bash to execute
>> that "vimlatex" script.
>> 
>> 
>> To reconfigure Vim to use the vimlatex pipe, you'll have to add a
>> line to your .vimrc. See the LaTeX suite manual:
>> 
>> :help latex-suite
>> 
>> In particular, try:
>> 
>> :help compiler-rules
>> 
>> for more information. You'll have to use a line like...
>> 
>> let g:Tex_CompileRule_dvi = 'vimlatex latex
>> -interaction=nonstopmode $*'
>> 
>> or, if you need to prefix it with bash:
>> 
>> let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex 
>> -interaction=nonstopmode $*'
>> 
>> 
>> Does that get you on the right track?
>> 
>> --Ted
>> 
>> 
>> 
>> Felipe G. Nievinski wrote:
>>> Hi.
>>> 
>>> When I'm compiling a .tex file with wrong cross-references
>>> (\label{} followed by \ref{}), I get a warning message indicating
>>> the offending reference (which I find useful) but then my .tex
>>> file gets replaced in vim with the corresponding .lox file (which
>>> I find annoying).
>>> 
>>> - Is that a bug or a feature? =)
>>> 
>>> Thanks, Felipe.
>>> 
>>> -------------------------------------------------------------------------
>>>  This SF.net email is sponsored by: Microsoft Defy all
>>> challenges. Microsoft(R) Visual Studio 2008. 
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
>>> _______________________________________________ Vim-latex-devel
>>> mailing list Vim...@li... 
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>> 
> 
> 

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

Re: [Vim-latex-devel] compiling with wrong cross-references

[Felipe G. N. <fgn...@te...>]

Hi Ted. Thank you for the detailed reply.
I think I'll keep splitting the vim window so that I can close the .lox 
file when it's brought up. (I hear you say, "Lazy this guy, eh?"... =)
Thanks for the answer, though.
Felipe.

Ted Pavlic wrote:
> Check out:
> 
> http://links.tedpavlic.com/shell_scripts/vimlatex
> 
> and/or
> 
> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html 
> 
> 
> 
> LaTeX error messages have an interesting format. They use parentheses to 
> start a block of error messages. For example...
> 
> (file1.tex
> 
> (file2.tex included from file1.tex
> information message posted from file2.tex)
> 
> error from file1.tex
> 
> )
> 
> When parsing these error messages, the parser has to keep track of which 
> "block" it's in. Vim's error parsing engine can handle this up until the 
> point where there are multiple closing parentheses on one line. That is, 
> if three blocks are closed at once with ")))" on one line, Vim will only 
> see the first parentheses. So, when an error message from file3 comes 
> up, sometimes Vim THINKS it's an error message for file2.
> 
> 
> The only good Vim fix to this problem is to pipe the LaTeX process 
> through a filter that prevents parentheses from stacking up. The 
> "vimlatex" script above will do that. Unfortunately, I've only had a 
> chance to implement that script for UNIX-like systems. Your e-mail looks 
> like it was generated with Thunderbird for Windows, so I'm guessing that 
> you're a Windows user. If that's the case, then you'll have to find a 
> Windows-compatible way to do the same thing. One solution would be to 
> install a few UNIX utilities that have been compiled for Windows. Namely:
> 
> *) bash
> *) sed
> 
> If those two are available, you'll be able to use bash to execute that 
> "vimlatex" script.
> 
> 
> To reconfigure Vim to use the vimlatex pipe, you'll have to add a line 
> to your .vimrc. See the LaTeX suite manual:
> 
> :help latex-suite
> 
> In particular, try:
> 
> :help compiler-rules
> 
> for more information. You'll have to use a line like...
> 
> let g:Tex_CompileRule_dvi = 'vimlatex latex -interaction=nonstopmode $*'
> 
> or, if you need to prefix it with bash:
> 
> let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex 
> -interaction=nonstopmode $*'
> 
> 
> Does that get you on the right track?
> 
> --Ted
> 
> 
> 
> Felipe G. Nievinski wrote:
>> Hi.
>>
>> When I'm compiling a .tex file with wrong cross-references (\label{} 
>> followed by \ref{}), I get a warning message indicating the offending 
>> reference (which I find useful) but then my .tex file gets replaced in 
>> vim with the corresponding .lox file (which I find annoying).
>>
>> - Is that a bug or a feature? =)
>>
>> Thanks,
>> Felipe.
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft Defy all challenges. 
>> Microsoft(R) Visual Studio 2008. 
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
> 

Re: [Vim-latex-devel] compiling with wrong cross-references

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

Check out:

http://links.tedpavlic.com/shell_scripts/vimlatex

and/or

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


LaTeX error messages have an interesting format. They use parentheses to 
start a block of error messages. For example...

(file1.tex

(file2.tex included from file1.tex
information message posted from file2.tex)

error from file1.tex

)

When parsing these error messages, the parser has to keep track of which 
"block" it's in. Vim's error parsing engine can handle this up until the 
point where there are multiple closing parentheses on one line. That is, 
if three blocks are closed at once with ")))" on one line, Vim will only 
see the first parentheses. So, when an error message from file3 comes 
up, sometimes Vim THINKS it's an error message for file2.


The only good Vim fix to this problem is to pipe the LaTeX process 
through a filter that prevents parentheses from stacking up. The 
"vimlatex" script above will do that. Unfortunately, I've only had a 
chance to implement that script for UNIX-like systems. Your e-mail looks 
like it was generated with Thunderbird for Windows, so I'm guessing that 
you're a Windows user. If that's the case, then you'll have to find a 
Windows-compatible way to do the same thing. One solution would be to 
install a few UNIX utilities that have been compiled for Windows. Namely:

*) bash
*) sed

If those two are available, you'll be able to use bash to execute that 
"vimlatex" script.


To reconfigure Vim to use the vimlatex pipe, you'll have to add a line 
to your .vimrc. See the LaTeX suite manual:

:help latex-suite

In particular, try:

:help compiler-rules

for more information. You'll have to use a line like...

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

or, if you need to prefix it with bash:

let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex 
-interaction=nonstopmode $*'


Does that get you on the right track?

--Ted



Felipe G. Nievinski wrote:
> Hi.
> 
> When I'm compiling a .tex file with wrong cross-references (\label{} 
> followed by \ref{}), I get a warning message indicating the offending 
> reference (which I find useful) but then my .tex file gets replaced in 
> vim with the corresponding .lox file (which I find annoying).
> 
> - Is that a bug or a feature? =)
> 
> Thanks,
> Felipe.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

[Vim-latex-devel] compiling with wrong cross-references

[Felipe G. N. <fgn...@te...>]

Hi.

When I'm compiling a .tex file with wrong cross-references (\label{} 
followed by \ref{}), I get a warning message indicating the offending 
reference (which I find useful) but then my .tex file gets replaced in 
vim with the corresponding .lox file (which I find annoying).

- Is that a bug or a feature? =)

Thanks,
Felipe.

Re: [Vim-latex-devel] single latex run?

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

If you try:

	:set makecmd?

you'll see the make command that Vim-LaTeX sets. It includes a "$*" at 
the end, which is substituted the argument passed to make.

Now, try:

	:!echo %

You'll see that the name of the file you're editing will be substituted 
for the "%".

Most importantly, check out:

	:help makeprg

You'll see:

=====
This option may contain '%' and '#' characters, which are expanded to
	the current and alternate file name.
=====

Then check out:

	:help :_%

and

	:help expand


HTH --
Ted



Felipe G. Nievinski wrote:
> Ted Pavlic wrote:
>> Try issuing:
>>
>> :make %
>>
>> rather than :make
>>
> That did it. (The minimum-effort solution :) Thanks!
> 
> Felipe.
> 
> PPS: what's the magic behind that percent sign? (I tried googling for 
> it, but it's hard to search without a keyword summarizing the concept).
> 
> 

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

Re: [Vim-latex-devel] single latex run?

[Felipe G. N. <fgn...@te...>]

Ted Pavlic wrote:
> Try issuing:
> 
> :make %
> 
> rather than :make
> 
That did it. (The minimum-effort solution :) Thanks!

Felipe.

PPS: what's the magic behind that percent sign? (I tried googling for 
it, but it's hard to search without a keyword summarizing the concept).

Re: [Vim-latex-devel] single latex run?

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

Try issuing:

:make %

rather than :make

--Ted

Felipe G. Nievinski wrote:
> Hi.
> 
> What would be the easiest way to run latex only once, from within vim, 
> please?
> 
> My .tex file is getting large and its compilation is not instantaneous 
> anymore. Furthermore, most of the time I only need to get a feel for 
> what the document will look like -- I wouldn't really need all the 
> references and citations correct.
> 
> I tried using vim's :make command, which issues
> 	latex --src-specials -interaction=nonstopmode 
>  >C:/Users/felipe/AppData/Local/Temp/VIe5CD.tmp 2>&1
> but never completes.
> 
> And it seems overkill to modify the suite's \ll.
> 
> Any hints or corrections would be appreciated.
> 
> Thanks,
> Felipe.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

[Vim-latex-devel] single latex run?

[Felipe G. N. <fgn...@te...>]

Hi.

What would be the easiest way to run latex only once, from within vim, 
please?

My .tex file is getting large and its compilation is not instantaneous 
anymore. Furthermore, most of the time I only need to get a feel for 
what the document will look like -- I wouldn't really need all the 
references and citations correct.

I tried using vim's :make command, which issues
	latex --src-specials -interaction=nonstopmode 
 >C:/Users/felipe/AppData/Local/Temp/VIe5CD.tmp 2>&1
but never completes.

And it seems overkill to modify the suite's \ll.

Any hints or corrections would be appreciated.

Thanks,
Felipe.

[Vim-latex-devel] F9 \ref completion fails

[Stefan S. <soe...@gm...>]

Hi all,

I use the F9 \ref completion quite a lot and just found a possible bug:

My document is composed of a number of files which are included in a
main file with the \input command. latex-suite finds all of them
correctly (and finds the label).

_But_ if the \input command in the main file is not placed at the
beginning of a line (e.g. in my case indented with a tab), latex-suite
does not recognize it (and thus shows no labels for these files)

Regards,

  Stefan

Re: [Vim-latex-devel] Mac OS X Leopard and F9 completion

[Reimundo H. <he...@ma...>]

This is an issue with the keyboard and not Leopard. 
I'm running 10.4.10 with that keyboard and having
the same problem. Is there anyway of preventing the
 OS of assigning <F9> to "fast forward"?.  The thing 
that strikes me as odd is that I can't even map 
it to <F6> which is useless in this keyboard.

Thanks,

R.

Re: [Vim-latex-devel] calling makeindex during compilation

[Felipe G. N. <fgn...@te...>]

Thanks for the hints. I was able to adapt compiler.vim and texrc. I'm 
sending the diff, in case anyone else might need it.

cheers.
Felipe.

  Felipe G. Nievinski wrote:
> Re: [Vim-latex-devel] calling makeindex during compilation
> From: Ted Pavlic <ted@te...> - 2008-04-11 13:06
>  > I guess you could do something similar with latex-suites compiler
>  > dependency stuff (see :help compiler-dependency), setting the chain
>  > to nlo,nls,dvi and setting compilation rules for .nls and .nlo. That
>  > would be your homework.
> 
> A few things...
> 
> *) As with makeindex, bibtex, etc., you'll often have to run latex twice
> after the makeindex call:
> 
> latex
> makeindex
> latex
> latex
> 
> In fact, there are some (ALMOST pathological) times when latex will need
> to be run yet again (and possibly makeindex again). Writing a Makefile
> to do all of this isn't trivial (though it's been done -- it's easy to
> find lots of very complete latex Makefile solutions on-line).
> 
> 
> *) If you build all of this logic into your Makefile, you should
> probably turn it off within Vim-LaTeX, or it may try to run LaTeX more
> than it needs to.
> 
> 
> *) I've actually modified my ~/.vim/ftplugin/latex-suite/compiler.vim
> file so that it runs makeindex not only if it sees idx files, but also
> if it sees other files for makeindex (like glo for glossaries or acr for
> acronyms). I'm not comfortable with distributing my own compiler.vim
> (for fear that I'll forget to tell you to also change something in
> texrc), but it may be a good idea to try hacking your own compiler.vim
> so that it responds to new .nlo files. Open up compiler.vim and search
> for "makeindex". You'll find the section. The flow isn't hard to follow.
> 
> 
> Best --
> Ted
> 
> 
> 
> 
>  > Happy hacking (and vimming)
>  >
>  > Martin
>  >
>  >
>  > On Thu, Apr 10, 2008 at 05:28:26PM -0300, Felipe G. Nievinski wrote:
>  >> Hi.
>  >>
>  >> I'm using the "nomenclature" latex package [1].
>  >>
>  >> It requires the following command
>  >>
>  >> makeindex mydoc.nlo -s nomencl.ist -o mydoc.nls
>  >>
>  >> in between latex runs.
>  >>
>  >> Could you give me a hint on how I could use the Vim-Latex suite to
>  >> automatize that intermediary call to makeindex, please? I'd like to
>  >> keep doing simply \ll, then.
>  >>
>  >> I've tried searching at the mailing list archive, to no avail.
>  >>
>  >> Thanks, Felipe.
>  >>
>  >> [1]
>  >> <http://mirror.ctan.org/macros/latex/contrib/nomencl/nomencl.pdf> A
>  >> snippet: The creation of the nomenclature list is very similar to
>  >> the creation of an index [6, App. A]. You need to: o Put
>  >> \usepackage[hoptionsi]{nomencl} in the preamble of your document. o
>  >> Put \makenomenclature in the preamble of your document. o Issue
>  >> the \nomenclature command (see Section 2.2) for each symbol you
>  >> want to have included in the nomenclature list. o Put
>  >> \printnomenclature at the place you want to have your nomenclature
>  >> list.
>  >>
>  >> Now put your file through LATEX. The command \makenomenclature will
>  >> instruct LATEX to open the nomenclature file <filename>.nlo
>  >> corresponding to your LATEX file <filename>.tex and to write the
>  >> information from your \nomenclature commands to this file.
>  >>
>  >> The next step is to invoke MakeIndex. You should instruct MakeIndex
>  >> to use <filename>.nlo as your input file, use nomencl.ist as your
>  >> style file, and write output to the file <filename>.nls. How to do
>  >> this depends on your implementation of MakeIndex. For most UNIX
>  >> implementations you should write something like makeindex
>  >> <filename>.nlo -s nomencl.ist -o <filename>.nls
>  >>
>  >> Now you have the file <filename>.nls that contains your
>  >> nomenclature list properly ordered. The last step is to invoke
>  >> LATEX on your master file <filename>.tex once more. It will input
>  >> your .nls file and process it accordingly to the current options.
>  >> That’s all!
>  >>
>  >>
>  >> 

Re: [Vim-latex-devel] Extra double quote within align environments

[Stefan S. <soe...@gm...>]

Hi,

I get the same behaviour when choosing align, equation, eqnarray, ... after
pressing F5. Entering the keyword first, then pressing F5 works though.

EEQ and EEA do work also, but EAL does nothing?!

Has anyone an idea?

- Stefan

Re: [Vim-latex-devel] Question about automatic indent

[Rhys U. <rhy...@gm...>]

I've run into similar problems repeatedly, and I'd welcome any solution.
This plagues me when working within math environments.

Please let me know if you'd like me to try out your patch.

- Rhys

On Fri, Apr 11, 2008 at 3:57 PM, Jesse Jacobsen <jm...@gm...> wrote:

> First, thank you for writing such a comprehensive and functional
> framework for editing LaTeX in Vim.  It has replaced my various
> home-grown solutions for some time now.  I use it daily.
>
> I have found that having } included in the indentkeys option is
> problematic when these two conditions are met:
>
> - I want a line to have a different indent than GetTeXIndent() would
>  like me to have.
>
> - I have something \emph{like this} within that line.
>
> The line is automatically reindented whenever the } character is entered
> into the buffer, so I have to manually reset the indent.
>
> There are two solutions I can see.  One is for me to stop insisting on
> using indent levels other than those provided by GetTeXIndent(), but
> that solution doesn't work with the kind of documents I often write.
>
> The other is to remove } from the indentkeys option.  Of course, that
> causes other problems.  The main problem is that several automatic
> features of LaTeXsuite rely upon } in indentkeys to produce sensible
> indents.  So, my question is this:
>
> Is there a reason why LaTeXsuite could not use ^F in its automatic
> features and templates instead of relying upon having the } in
> indentkeys?  According to the Vim documentation, and my own experiments,
> ^F is a usual way to reindent the current line according to indentexpr.
> I also noticed that !^F is already included in the indentkeys option
> under LaTeXsuite.  I have even modified parts of LaTeXsuite to include a
> ^F -- usually after a } -- so that the line is reindented immediately
> after being inserted.  It seems to work well.  However, there may be a
> reason I'm not aware of that this would not be a good solution.
>
> I could try creating a diff, but it would take me a while.  Please let
> me know if you'd like me to.
>
> Jesse Jacobsen
>
>
> --
> For God did not send His Son into the world to condemn the world, but
> that the world through Him might be saved.
> www.concordiahoodriver.org  www.bethanythedalles.org
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] Question about automatic indent

[Jesse J. <jm...@gm...>]

First, thank you for writing such a comprehensive and functional
framework for editing LaTeX in Vim.  It has replaced my various
home-grown solutions for some time now.  I use it daily.

I have found that having } included in the indentkeys option is
problematic when these two conditions are met:

- I want a line to have a different indent than GetTeXIndent() would
  like me to have.

- I have something \emph{like this} within that line.

The line is automatically reindented whenever the } character is entered
into the buffer, so I have to manually reset the indent.

There are two solutions I can see.  One is for me to stop insisting on
using indent levels other than those provided by GetTeXIndent(), but
that solution doesn't work with the kind of documents I often write.

The other is to remove } from the indentkeys option.  Of course, that
causes other problems.  The main problem is that several automatic
features of LaTeXsuite rely upon } in indentkeys to produce sensible
indents.  So, my question is this:

Is there a reason why LaTeXsuite could not use ^F in its automatic
features and templates instead of relying upon having the } in
indentkeys?  According to the Vim documentation, and my own experiments,
^F is a usual way to reindent the current line according to indentexpr.
I also noticed that !^F is already included in the indentkeys option
under LaTeXsuite.  I have even modified parts of LaTeXsuite to include a
^F -- usually after a } -- so that the line is reindented immediately
after being inserted.  It seems to work well.  However, there may be a
reason I'm not aware of that this would not be a good solution.

I could try creating a diff, but it would take me a while.  Please let
me know if you'd like me to.

Jesse Jacobsen


--
For God did not send His Son into the world to condemn the world, but
that the world through Him might be saved.
www.concordiahoodriver.org  www.bethanythedalles.org

Re: [Vim-latex-devel] calling makeindex during compilation

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

> I guess you could do something similar with latex-suites compiler 
> dependency stuff (see :help compiler-dependency), setting the chain
> to nlo,nls,dvi and setting compilation rules for .nls and .nlo. That
> would be your homework.

A few things...

*) As with makeindex, bibtex, etc., you'll often have to run latex twice 
after the makeindex call:

latex
makeindex
latex
latex

In fact, there are some (ALMOST pathological) times when latex will need 
to be run yet again (and possibly makeindex again). Writing a Makefile 
to do all of this isn't trivial (though it's been done -- it's easy to 
find lots of very complete latex Makefile solutions on-line).


*) If you build all of this logic into your Makefile, you should 
probably turn it off within Vim-LaTeX, or it may try to run LaTeX more 
than it needs to.


*) I've actually modified my ~/.vim/ftplugin/latex-suite/compiler.vim 
file so that it runs makeindex not only if it sees idx files, but also 
if it sees other files for makeindex (like glo for glossaries or acr for 
acronyms). I'm not comfortable with distributing my own compiler.vim 
(for fear that I'll forget to tell you to also change something in 
texrc), but it may be a good idea to try hacking your own compiler.vim 
so that it responds to new .nlo files. Open up compiler.vim and search 
for "makeindex". You'll find the section. The flow isn't hard to follow.


Best --
Ted




> Happy hacking (and vimming)
> 
> Martin
> 
> 
> On Thu, Apr 10, 2008 at 05:28:26PM -0300, Felipe G. Nievinski wrote:
>> Hi.
>> 
>> I'm using the "nomenclature" latex package [1].
>> 
>> It requires the following command
>> 
>> makeindex mydoc.nlo -s nomencl.ist -o mydoc.nls
>> 
>> in between latex runs.
>> 
>> Could you give me a hint on how I could use the Vim-Latex suite to 
>> automatize that intermediary call to makeindex, please? I'd like to
>> keep doing simply \ll, then.
>> 
>> I've tried searching at the mailing list archive, to no avail.
>> 
>> Thanks, Felipe.
>> 
>> [1]
>> <http://mirror.ctan.org/macros/latex/contrib/nomencl/nomencl.pdf> A
>> snippet: The creation of the nomenclature list is very similar to
>> the creation of an index [6, App. A]. You need to: o  Put
>> \usepackage[hoptionsi]{nomencl} in the preamble of your document. o
>> Put \makenomenclature in the preamble of your document. o  Issue
>> the \nomenclature command (see Section 2.2) for each symbol you
>> want to have included in the nomenclature list. o  Put
>> \printnomenclature at the place you want to have your nomenclature
>> list.
>> 
>> Now put your file through LATEX. The command \makenomenclature will
>>  instruct LATEX to open the nomenclature file <filename>.nlo 
>> corresponding to your LATEX file <filename>.tex and to write the 
>> information from your \nomenclature commands to this file.
>> 
>> The next step is to invoke MakeIndex. You should instruct MakeIndex
>> to use <filename>.nlo as your input file, use nomencl.ist as your
>> style file, and write output to the file <filename>.nls. How to do
>> this depends on your implementation of MakeIndex. For most UNIX 
>> implementations you should write something like makeindex
>> <filename>.nlo -s nomencl.ist -o <filename>.nls
>> 
>> Now you have the file <filename>.nls that contains your
>> nomenclature list properly ordered. The last step is to invoke
>> LATEX on your master file <filename>.tex once more. It will input
>> your .nls file and process it accordingly to the current options.
>> That’s all!
>> 
>> 
>> -------------------------------------------------------------------------
>>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>>  Don't miss this year's exciting event. There's still time to save
>> $100. Use priority code J8TL2D2. 
>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>>  _______________________________________________ Vim-latex-devel
>> mailing list Vim...@li... 
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save
> $100. Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________ Vim-latex-devel
> mailing list Vim...@li... 
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

Re: [Vim-latex-devel] calling makeindex during compilation

[Martin S. <fo...@un...>]

If you are familiar with make(1) and Makefiles, I would recommend giving
them a try.  It should't be to big of a hassle to write one, and
latex-suite automatically uses the Makefile if it exists in your working
directory.

I think your Makefile would look like this (I did not test it, never
used nomenclature before):

all: mydoc.dvi

mydoc.dvi: mydoc.nls
		latex -interaction=nonstopmode mydoc.tex

mydoc.nls: mydoc.nlo nomencl.ist
		makeindex mydoc.nlo -s nomencl.ist -o mydoc.nls

mydoc.nlo: mydoc.tex
		latex -interaction=nonstopmode mydoc.tex

clean:
	-rm -rf mydoc.dvi

.PHONY: clean

(don't just copy and paste, there has to be a TAB in front of every
rule, not a number of SPACES (if you don't know what I am talking about,
read an introduction to Makefiles).
Of course you could write the Makefile much more generally, but that
wouldn't help readability. There are tons of documentation on Makefiles
on the internet..

I guess you could do something similar with latex-suites compiler
dependency stuff (see :help compiler-dependency), setting the chain to
nlo,nls,dvi and setting compilation rules for .nls and .nlo. That would
be your homework.

Happy hacking (and vimming)

Martin


On Thu, Apr 10, 2008 at 05:28:26PM -0300, Felipe G. Nievinski wrote:
> Hi.
> 
> I'm using the "nomenclature" latex package [1].
> 
> It requires the following command
> 
>      makeindex mydoc.nlo -s nomencl.ist -o mydoc.nls
> 
> in between latex runs.
> 
> Could you give me a hint on how I could use the Vim-Latex suite to
> automatize that intermediary call to makeindex, please? I'd like to keep 
> doing simply \ll, then.
> 
> I've tried searching at the mailing list archive, to no avail.
> 
> Thanks,
> Felipe.
> 
> [1] <http://mirror.ctan.org/macros/latex/contrib/nomencl/nomencl.pdf>
> A snippet:
> The creation of the nomenclature list is very similar to the creation of
> an index [6, App. A]. You need to:
>      o  Put \usepackage[hoptionsi]{nomencl} in the preamble of your
> document.
>      o  Put \makenomenclature in the preamble of your document.
>      o  Issue the \nomenclature command (see Section 2.2) for each
> symbol you want to have included in the nomenclature list.
>      o  Put \printnomenclature at the place you want to have your
> nomenclature list.
> 
> Now put your file through LATEX. The command \makenomenclature will
> instruct LATEX to open the nomenclature file <filename>.nlo
> corresponding to your LATEX file <filename>.tex and to write the
> information from your \nomenclature commands to this file.
> 
> The next step is to invoke MakeIndex. You should instruct MakeIndex to
> use <filename>.nlo as your input file, use nomencl.ist as your style
> file, and write output to the file <filename>.nls. How to do this
> depends on your implementation of MakeIndex. For most UNIX
> implementations you should write something like
>      makeindex <filename>.nlo -s nomencl.ist -o <filename>.nls
> 
> Now you have the file <filename>.nls that contains your nomenclature
> list properly ordered. The last step is to invoke LATEX on your master
> file <filename>.tex once more. It will input your .nls file and process
> it accordingly to the current options. That’s all!
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] calling makeindex during compilation

[Felipe G. N. <fgn...@te...>]

Hi.

I'm using the "nomenclature" latex package [1].

It requires the following command

     makeindex mydoc.nlo -s nomencl.ist -o mydoc.nls

in between latex runs.

Could you give me a hint on how I could use the Vim-Latex suite to
automatize that intermediary call to makeindex, please? I'd like to keep 
doing simply \ll, then.

I've tried searching at the mailing list archive, to no avail.

Thanks,
Felipe.

[1] <http://mirror.ctan.org/macros/latex/contrib/nomencl/nomencl.pdf>
A snippet:
The creation of the nomenclature list is very similar to the creation of
an index [6, App. A]. You need to:
     o  Put \usepackage[hoptionsi]{nomencl} in the preamble of your
document.
     o  Put \makenomenclature in the preamble of your document.
     o  Issue the \nomenclature command (see Section 2.2) for each
symbol you want to have included in the nomenclature list.
     o  Put \printnomenclature at the place you want to have your
nomenclature list.

Now put your file through LATEX. The command \makenomenclature will
instruct LATEX to open the nomenclature file <filename>.nlo
corresponding to your LATEX file <filename>.tex and to write the
information from your \nomenclature commands to this file.

The next step is to invoke MakeIndex. You should instruct MakeIndex to
use <filename>.nlo as your input file, use nomencl.ist as your style
file, and write output to the file <filename>.nls. How to do this
depends on your implementation of MakeIndex. For most UNIX
implementations you should write something like
     makeindex <filename>.nlo -s nomencl.ist -o <filename>.nls

Now you have the file <filename>.nls that contains your nomenclature
list properly ordered. The last step is to invoke LATEX on your master
file <filename>.tex once more. It will input your .nls file and process
it accordingly to the current options. That’s all!

Re: [Vim-latex-devel] Folding breaks "goto error"

[Dan M. H. <dan...@st...>]

Den 9. april. 2008 kl. 15.58 skrev Ted Pavlic:
> Dan --
>
> 	Two quick notes...
>
>> Thanks alot to both of you for the help. I tested some more and   
>> discovered that Vim 7.1 actually _is_ capable of autoexpanding the   
>> fold when using :cc. I misinterpreted the problem, which actually   
>> seems to be that the <Enter>-key doesn't work in the quickfix- 
>> window,  but that is certainly not a Vim-LaTex-problem :)
>
> 1. What was your fix? That is, when you did :cc, did it autoexpand  
> as you wanted?

Yes, when I use :cc in the main window (not the Quickfix), Vim  
autoexpands the folds as I wanted. But when using the <Enter>-key in  
the Quickfix-window it only takes me to the fold without expanding it.  
That is not a big issue though.

> 2. "Enter" works fine for me in the Quickfix window, because I use  
> "vimlatex" to pipe my latex through. Everyone who uses Vim and LaTeX  
> together should be doing something similar.
>
> See:
>
> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>
> for more details.

Thanks a lot, Ted. That solved the problem with my non-working <Enter>- 
key.

Dan Michael

Re: [Vim-latex-devel] Folding breaks "goto error"

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

Dan --

	Two quick notes...

> Thanks alot to both of you for the help. I tested some more and  
> discovered that Vim 7.1 actually _is_ capable of autoexpanding the  
> fold when using :cc. I misinterpreted the problem, which actually  
> seems to be that the <Enter>-key doesn't work in the quickfix-window,  
> but that is certainly not a Vim-LaTex-problem :)

1. What was your fix? That is, when you did :cc, did it autoexpand as 
you wanted?

2. "Enter" works fine for me in the Quickfix window, because I use 
"vimlatex" to pipe my latex through. Everyone who uses Vim and LaTeX 
together should be doing something similar.

See:

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

for more details.

--Ted



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

Re: [Vim-latex-devel] Folding breaks "goto error"

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

> When an error is selected in the quickfix-window, pressing <Enter>  
> takes you to the error in the latex-document. But when the given line  
> is inside a fold, nothing happens. Is it possible to get Vim-Latex to  
> autoexpand the fold and take you to the error?

IIRC, pressing a key that will open a fold (like pressing the right 
cursor) will bring you to the correct line. That is, the quickfix window 
will bring you to the right fold, and pressing the right arrow key 
should open the fold to the correct spot.

The problem isn't something specific to Vim-LaTeX. When you press 
"enter" in the quickfix window, Vim runs

:.cc

which brings you to the line corresponding to wherever your cursor is in 
the quickfix window. You would like to do something like

:.cc;foldo!

or something, but that doesn't work (Vim complains about "trailing 
characters").

Because this is a Vim problem and not a Vim-LaTeX problem, I highly 
recommend that you post in the "vim" list. I'm sure others have had this 
problem and have a solution (or at least can give an authoritative "no").

--Ted


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

[Vim-latex-devel] Folding breaks "goto error"

[Dan M. H. <dan...@st...>]

Hi,

I'm new to Vim-Latex and I'm sorry if this has already been discussed.

When an error is selected in the quickfix-window, pressing <Enter>  
takes you to the error in the latex-document. But when the given line  
is inside a fold, nothing happens. Is it possible to get Vim-Latex to  
autoexpand the fold and take you to the error?

Thanks
Dan Michael

Re: [Vim-latex-devel] Mac OS X Leopard and F9 completion

[Daniele A. <d.a...@gm...>]

Thanks for the quick response. In Leopard (and new aluminum keyboards) F9 is
associated with the iTunes "forward" button, and F3 with exposé. To have a
"real F9" I have to do fn+F9 which is still reserved for exposé (grrrr). I
have no choice, I believe.
imap buffer <F1> <Plug>Tex_Completion

doesn't work because F1 is mapped to the brightness of the display and if I
type fn+F1 (the "real F1") MacVim prompts the help (hence, I suppose, F1 is
for the help).

I have F13 free on my aluminum keyboard. Anyway if I try

imap buffer <F13> <Plug>Tex_Completion

then, when I try to complete a "\ref{fig:" field, I obtain the characters
<F13> on the screen.

Thanks

Daniele




On Tue, Apr 8, 2008 at 12:13 PM, Christian Ebert <bla...@gm...> wrote:

> * Daniele Avitabile on Tuesday, April 08, 2008 at 09:02:07 +0100
> > I'm using Vim-LaTeX and MacVim under Leopard. Unfortunately, F9 on this
> OS
> > has been reserved already for exposé. Any idea how to map another key,
> say
> > F1, to do the same?
>
> try:
>
> imap buffer <F1> <Plug>Tex_Completion
>
> in ~/.vim/ftplugin/tex.vim (untested).
>
> But first you might want think about your working practices:
>
> Can't you press fn-F9, "fn" being the "function" key probably on
> the very left of your keyboard?
>
> And, if Leopard is not completely different to Tiger, you can go
> to System Preferences->Keyboard & Mouse->Keyboard and tick the
> "Use all F1, F2, etc. keys [...]" to get the standared behaviour
> within Vim (and other non-Mac progs for that matter). This
> reverses the behaviour of the "fn" key, that is, for exposé you
> now have to press fn-F9. Depends on your use habits.
>
> c
> --
> _B A U S T E L L E N_ lesen! --->> <
> http://www.blacktrash.org/baustellen.html>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Register now and save $200. Hurry, offer ends at 11:59 p.m.,
> Monday, April 7! Use priority code J8TLD2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>