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

Re: [Vim-latex-devel] I don't want to place the first error

[Till M. <ope...@ti...>]

On Fri October 31 2008, Zsolt Udvari wrote:

> As I wrote in the "subject", I don't want to place the first error
> after compilation.
> As in the docs ([1], [2]), I set the g:Tex_GotoError variable to 0
> ('let g:Tex_GotoError=0'), but it doesn't work. After press \ll, and
> return, the buffer changed (matek-11.tex to kombi.tex), and taken at
> the first warning.
> What can I do? Is it a bug?

If you post an link to example .tex files with the least required contents to 
reproduce this, I will take a look into this.

Regards,
Till

Re: [Vim-latex-devel] Wrong completion with 'section'

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

Because I don't use F5 regularly, I don't know much about it or how it's 
implemented.

However, I know that you can type

SSE

to get exactly what you want.

--Ted


Matthieu Louvel de Monceaux wrote:
> Hi,
> 
> I'm using Vim 7.2.025 and Vim-LaTeX 20060325 (the latest one AFAIK).
> It works properly but :
> when I type 'section' then press F5 to complete, it writes :
> 
> 0\section{<++>}<++>
> 
> with the cursor placed just after the 0, instead of :
> 
> \section{<++>}<++>
> 
> with the cursor placed after in the } spot, which would be good.
> 
> Any idea ?
> 
> 
> Cheers,
> M. Louvel de Monceaux
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

[Vim-latex-devel] Wrong completion with 'section'

[Matthieu L. de M. <gl...@gm...>]

Hi,

I'm using Vim 7.2.025 and Vim-LaTeX 20060325 (the latest one AFAIK).
It works properly but :
when I type 'section' then press F5 to complete, it writes :

0\section{<++>}<++>

with the cursor placed just after the 0, instead of :

\section{<++>}<++>

with the cursor placed after in the } spot, which would be good.

Any idea ?


Cheers,
M. Louvel de Monceaux

[Vim-latex-devel] insert package shortcut does not work as expected

[Fabio L. <fab...@we...>]

Hello everybody,

I have a problem regarding the insert \usepackage{} shortcut, defaulting
to the F5 key. Packages such as 'float' or 'array' are working as
expected. However, when the package offers optional arguments, e.g.
'amsmath' or 'babel', then latex-suite inserts this ugly string:
<++>]{amsmath}"`usepackage[X instead of the expected
\usepackage[]{amsmath}<++>
typing the command :TPackage works great (i.e.
\usepackage[]{amsmath}<++>). Info: This command, as opposed to the F5
key, prompts me for pressing return before inserting the correct string.

Is this a familiar bug? Did I miss some config? Can someone point me in
the right direction?

Thanks in advance!

--FL

[Vim-latex-devel] I don't want to place the first error

[Zsolt U. <udv...@gm...>]

Hi all!

As I wrote in the "subject", I don't want to place the first error
after compilation.
As in the docs ([1], [2]), I set the g:Tex_GotoError variable to 0
('let g:Tex_GotoError=0'), but it doesn't work. After press \ll, and
return, the buffer changed (matek-11.tex to kombi.tex), and taken at
the first warning.
What can I do? Is it a bug?
I'm using latexSuite20060325.

Thanks!
Zsolt


[1]: http://vim-latex.sourceforge.net/documentation/latex-suite/latex-compiling.html
[2]: http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-compiling.html#Tex_GotoError

Re: [Vim-latex-devel] New user installation problems

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

> Hello. I am trying to successfully install the plugin for GVim. I have 
> followed the sourceforge page installation instructions. I did not have a 
> ~/.vim folder so I had to create on in ~ 
> 
> I dropped the tar files in that folder but when I fire up GVim there are no 
> other menues for the is plugin. Plugins are new to me as is GVim. I'm used to 
> using the console for Vi/m. I did add the additions to the bottom of 
> my .vimrc too so I'm at a loss as to what is wrong.

First, check out:

http://phaseportrait.blogspot.com/2008/03/vim-latex-vim-70-and-filetype-plugin.html

You'll need to add

let g:tex_flavor='latex'

to your .vimrc (as well as the other changes described by the VIM-LaTeX 
documentation).

After that, you will only notice the Vim-LaTeX extensions firing up 
*AFTER* you edit TeX source (e.g., a file that ends in ".tex").

I hope that helps --
Ted


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

[Vim-latex-devel] New user installation problems -- SOLVED... duh i needed to save it as a .tex file and the menues started working!!!

[GK <gm...@gm...>]

Hello. I am trying to successfully install the plugin for GVim. I have 
followed the sourceforge page installation instructions. I did not have a 
~/.vim folder so I had to create on in ~ 

I dropped the tar files in that folder but when I fire up GVim there are no 
other menues for the is plugin. Plugins are new to me as is GVim. I'm used to 
using the console for Vi/m. I did add the additions to the bottom of 
my .vimrc too so I'm at a loss as to what is wrong.

Vi^3PirePengy

Sorry to bug you all. Don't I feel stupid now. 

Are there any resource people would have available to start volunteering or 
using in a entry level position for la/tex for additional work? I'm trying to 
get ideas to generate extra income.






-- 

------- GPG signed 
11FD 290A FAAE 07A7 9876 37AC D14F 11D6 0831 0392

Many individuals and organizations around the
globe have developed international cross platform
protocols to support your freedoms and ideas. 
Please support Open Standards for software and 
hardware with cross platform ISO standards and not 
proprietary formats from monopolies and the 
associated vendor lockin. If you are a Windows user
protect yourself from various known software 
vulnerabilities that allow virii, malware, adware,
trojans, etc., and use Firefox/Mozilla with 
NoScript for web browsing and not Internet Explorer. 
HTML emails, Microsoft DOC(X)/XLS(X) formats are 
not acceptable to send me. Please enclose inline or
by attachment with RTF, TXT, DJVU or PDF formats. 
Thank You.

This email generated by a Linux Operating System 
and accompanying software. Encryption of data and
emails is encouraged and welcomed with GnuPG.

[Vim-latex-devel] New user installation problems

[GK <gm...@gm...>]

Hello. I am trying to successfully install the plugin for GVim. I have 
followed the sourceforge page installation instructions. I did not have a 
~/.vim folder so I had to create on in ~ 

I dropped the tar files in that folder but when I fire up GVim there are no 
other menues for the is plugin. Plugins are new to me as is GVim. I'm used to 
using the console for Vi/m. I did add the additions to the bottom of 
my .vimrc too so I'm at a loss as to what is wrong.

Vi^3PirePengy


-- 

------- GPG signed 
11FD 290A FAAE 07A7 9876 37AC D14F 11D6 0831 0392

Many individuals and organizations around the
globe have developed international cross platform
protocols to support your freedoms and ideas. 
Please support Open Standards for software and 
hardware with cross platform ISO standards and not 
proprietary formats from monopolies and the 
associated vendor lockin. If you are a Windows user
protect yourself from various known software 
vulnerabilities that allow virii, malware, adware,
trojans, etc., and use Firefox/Mozilla with 
NoScript for web browsing and not Internet Explorer. 
HTML emails, Microsoft DOC(X)/XLS(X) formats are 
not acceptable to send me. Please enclose inline or
by attachment with RTF, TXT, DJVU or PDF formats. 
Thank You.

This email generated by a Linux Operating System 
and accompanying software. Encryption of data and
emails is encouraged and welcomed with GnuPG.

[Vim-latex-devel] vim-latex page on www.vim.org not up to date

[Emmanuel T. <etr...@gm...>]

www.vim.org is my main entry point to find vim plugins and your page on this
site is not up to date (last version is a 2003 version). I think it would be
a good idea to "refresh" it.

Emmanuel

[Vim-latex-devel] Minor change for vim-latex with taglist

[Robin <ro...@gm...>]

I have been using the most recent download version from the website
latexSuite20060325.

I think it is great - but had some problems with completion. I like to
use taglist, to navigate sections, labels etc. as in this tip:
http://vim.wikia.com/wiki/VimTip453

However, I found that F9 completions for citations and references were
failing, as vim-latex was trying to insert them into the taglist
window instead of the document window.

This was fixed by adding the line:
        exe s:winnum.' wincmd w'
as the first line of the function Tex_CompleteWord in texviewer.vim
(which was for me line 216).

I am not sure if vim-latex is actively developed any more (which is a
shame) but if it is perhaps this change can be added to the official
repository.

Robin

Re: [Vim-latex-devel] F9 completion problem patch

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

> Then, besides changing the subject, it might even be better to 
> actually not reply to the original (reply-to header) <-- insert big
> smiley here.

Huh... I clicked "Edit as New" in Thunderbird and assumed it would get 
rid of any references to the old message ID.... I guess I assumed wrong. 
  I figured "New" would mean "New," but I guess I can see how some 
people would be upset if "New" really meant "New," but then they could 
have used a different word.

--Ted

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

Re: [Vim-latex-devel] F9 completion problem patch

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

* Ted Pavlic on Tuesday, September 02, 2008 at 16:57:36 -0400
> This is my SECOND time posting this message. I realize that I may have  
> posted the first one as a response to the incorrect thread, and so I'm  
> going to go ahead and post it as a new thread . . .

Then, besides changing the subject, it might even be better to
actually not reply to the original (reply-to header) <-- insert
big smiley here.

> diff -ru old/outline.py new/outline.py
> --- old/outline.py      2008-08-27 17:55:51.000000000 +0200
> +++ new/outline.py      2008-08-27 18:00:55.000000000 +0200
> @@ -23,7 +23,7 @@
>      contents = '\n'.join(open(fname).read().splitlines())
> 
>      # TODO what are all the ways in which a tex file can include another?
> -    pat = re.compile(r'^\\(@?)(include|input){(.*?)}', re.M)
> +    pat = re.compile(r'^\s*\\(@?)(include|input){(.*?)(.tex)?}', re.M)

Perhaps make it non-greedy:

    pat = re.compile(r'^\s*?\\(@?)(include|input){(.*?)(.tex)?}', re.M)

>      contents = re.sub(pat, lambda input: getFileContents(input, ext), contents)
> 
>      return ('%%==== FILENAME: %s' % fname) + '\n' + contents

c
-- 
  Was heißt hier Dogma, ich bin Underdogma!
[ What the hell do you mean dogma, I am underdogma. ]

_F R E E_  _V I D E O S_  -->>  http://www.blacktrash.org/underdogma/

[Vim-latex-devel] F9 completion problem patch

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

This is my SECOND time posting this message. I realize that I may have 
posted the first one as a response to the incorrect thread, and so I'm 
going to go ahead and post it as a new thread . . .


It appears like an F9 completion problem has been patched. See the 
message below and the attached patch (from Florian Petran).

===== (from Florian Petran)
Sorry for mailing you directly, but no matter how I try to post to
vim-latex-devel, none of my mails seem to make it through. A while
ago, someone brought up an issue with F9 ref completion not working
when there was whitespace before the input directive. Turns out it is
just a small error in a regex in outline.py, I noticed that when I was
looking for an error where F9 completion wouldn't work when the
filename was stated with the tex extension. I wrote a patch for that
file that fixes both errors, could you please forward it to the list?
It requires deactivating python via let g:Tex_UsePython=0, though, for
the changed python code to take effect.
=====

So try applying the attached patch, and then adding a

let g:Tex_UsePython=0

in your .vimrc.

--Ted

P.S.

I have not tried this patch. This problem doesn't bother me, and so I
don't have an opinion. I was just asked to post this.


ahmet nurlu wrote:
> Hi,
> 
> I have been getting this recent error with a vim7.1.
> It is not happening with vim6.4. 
> 
> The problem is that \cite{} command doesn't search
> through \begin{thebibliography} environment.(It is
> strange that  when I type "\cite" , its color becomes
> blue.)
> 
> My tex file(try.tex) is something like:
> ------------------------------------->
> \documentclass{article}
> \usepackage{color}
> \usepackage{listings}
> \begin{document}
> try try try
> 
> \cite{}<++>
> 
> \begin{thebibliography}{99}
>        \bibitem{goossens93} Michel Goossens, The Latex
> Book
> \end{thebibliography}
> \end{document}
> ---------------------------------------------<
> 
> when the cursor positions itself into the \cite{},
> pressing F9 brings no action. 
> 
> This problem doesn't arise if I prepare a bib
> file(trybib.bib) and put my bibliography index into
> it. For example, 
> 
> my_Directory/
>        try.tex
>        trybib.bib
> ------------------------------------------------->
> \documentclass{article}
> \usepackage{color}
> \usepackage{listings}
> \begin{document}
> try try try
> 
> \cite{}<++>
> \bibliographystyle{plain}
> \bibliography{trybib}
> 
> \end{document}
> 
> I am using vim-latexsuite(debian/unstable). Any
> suggestions?
> 
> Regards,
> Ahmet
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

Re: [Vim-latex-devel] F9 completion problem in vim7

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

It appears like this problem has been patched. See the message below and 
the attached patch (from Florian Petran).

===== (from Florian Petran)
Sorry for mailing you directly, but no matter how I try to post to
vim-latex-devel, none of my mails seem to make it through. A while
ago, someone brought up an issue with F9 ref completion not working
when there was whitespace before the input directive. Turns out it is
just a small error in a regex in outline.py, I noticed that when I was
looking for an error where F9 completion wouldn't work when the
filename was stated with the tex extension. I wrote a patch for that
file that fixes both errors, could you please forward it to the list?
It requires deactivating python via let g:Tex_UsePython=0, though, for
the changed python code to take effect.
=====

So try applying the attached patch, and then adding a

let g:Tex_UsePython=0

in your .vimrc.

--Ted

P.S.

I have not tried this patch. This problem doesn't bother me, and so I 
don't have an opinion. I was just asked to post this.


ahmet nurlu wrote:
> Hi,
> 
> I have been getting this recent error with a vim7.1.
> It is not happening with vim6.4. 
> 
> The problem is that \cite{} command doesn't search
> through \begin{thebibliography} environment.(It is
> strange that  when I type "\cite" , its color becomes
> blue.)
> 
> My tex file(try.tex) is something like:
> ------------------------------------->
> \documentclass{article}
> \usepackage{color}
> \usepackage{listings}
> \begin{document}
> try try try
> 
> \cite{}<++>
> 
> \begin{thebibliography}{99}
>        \bibitem{goossens93} Michel Goossens, The Latex
> Book
> \end{thebibliography}
> \end{document}
> ---------------------------------------------<
> 
> when the cursor positions itself into the \cite{},
> pressing F9 brings no action. 
> 
> This problem doesn't arise if I prepare a bib
> file(trybib.bib) and put my bibliography index into
> it. For example, 
> 
> my_Directory/
>        try.tex
>        trybib.bib
> ------------------------------------------------->
> \documentclass{article}
> \usepackage{color}
> \usepackage{listings}
> \begin{document}
> try try try
> 
> \cite{}<++>
> \bibliographystyle{plain}
> \bibliography{trybib}
> 
> \end{document}
> 
> I am using vim-latexsuite(debian/unstable). Any
> suggestions?
> 
> Regards,
> Ahmet
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

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

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

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

> Btw. you can abbreviate filetype as ft.

Yep, but because I was taking the time to document it, I wanted the 
solution to be self-explanatory.

That being said, if people like the idea of manually setting their 
filetype over and over again... maybe it's better to list the abbreviation.

I've now noted both abbreviations.

--Ted


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

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Till M. <ope...@ti...>]

On Thu August 7 2008, Ted Pavlic wrote:
> I've tried to document all of these solutions in:
>
> http://phaseportrait.blogspot.com/2008/03/vim-latex-vim-70-and-filetype-plu
>gin.html

Btw. you can abbreviate filetype as ft.

Regards,
Till

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

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

I've tried to document all of these solutions in:

http://phaseportrait.blogspot.com/2008/03/vim-latex-vim-70-and-filetype-plugin.html

--Ted

Ted Pavlic wrote:
>>> Evidently, adding:
>>>
>>> %&latex
>>>
>>> to the top of any .tex file will set the proper filetype.
>> You can also add this to the top of the file (or at the end) to probably get 
>> the same (the filetype will be set to tex):
>>
>> % vim: filetype=tex
> 
> Very cool. That works well.
> 
> Thanks --
> Ted
> 
> 

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

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

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

>> Evidently, adding:
>>
>> %&latex
>>
>> to the top of any .tex file will set the proper filetype.
> 
> You can also add this to the top of the file (or at the end) to probably get 
> the same (the filetype will be set to tex):
> 
> % vim: filetype=tex

Very cool. That works well.

Thanks --
Ted


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

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Till M. <ope...@ti...>]

On Thu August 7 2008, Ted Pavlic wrote:
> Evidently, adding:
>
> %&latex
>
> to the top of any .tex file will set the proper filetype.
>
> So if you don't want to force the tex_flavor, add that comment to the
> top of your LaTeX sources.

You can also add this to the top of the file (or at the end) to probably get 
the same (the filetype will be set to tex):

% vim: filetype=tex

Regards,
Till

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

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

Evidently, adding:

%&latex

to the top of any .tex file will set the proper filetype.

So if you don't want to force the tex_flavor, add that comment to the 
top of your LaTeX sources.

--Ted

Ted Pavlic wrote:
> In the recent patches that were applied to Vim-LaTeX, was the line:
> 
> 	let g:tex_flavor='latex'
> 
> added somewhere? Without it, Vim7's filetype plugin fails to load 
> Vim-LaTeX. Something changed between Vim6 and Vim7 that made latex *not* 
> the default, which seems strange.
> 
> 

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

Re: [Vim-latex-devel] Adding latex suite hooks for .w file type

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

> Adding a file ~/.vim/ftdetect/vim-latex.vim containing:
> 
> au BufNewFile,BufRead *.w set ft=tex

I was thinking of something similar, but I was afraid that that would 
blow away any cweb-specific hooks from the cweb filetype.

So it seemed like a better idea to do the symlink option so that the 
filetype stayed cweb while also loading Vim-LaTeX.

--Ted


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

Re: [Vim-latex-devel] Adding latex suite hooks for .w file type

[Till M. <ope...@ti...>]

On Thu August 7 2008, Rhys Ulerich wrote:

> I'd like to enable latex suite within my CWEB source files (.w extension).
> Vim has a cweb syntax option (set syntax=cweb).  Any idea how to trigger
> loading latex suite for .w files?  I've tried copying my

> ~/.vim/ftplugin/tex.vim and tex_latexSuite.vim to parallel versions
> starting with 'w', but no luck yet.

A symlink from cweb_latexSuite.vim to tex_latexSuite.vim will probably oben 
vim latex for cweb.

Adding a file ~/.vim/ftdetect/vim-latex.vim containing:

au BufNewFile,BufRead *.w set ft=tex

worked here.

Regards,
Till

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

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

FYI, James Vega posted this in the vim-dev list:

=====
Before Vim7 was released, Benji Fisher (the tex ftplugin maintainer)
brought up these changes for discussion[0].  There was also a discussion
started by Stefano Zacchiroli[1] a few months later wondering whether
tex should be the default.

[0] - http://thread.gmane.org/gmane.editors.vim.devel/11826
[1] - 
http://thread.gmane.org/gmane.linux.debian.packages.vim.devel/2915/focus=14409
=====

That explains some things. It's nice to see that people debated... I 
guess...

--Ted


Till Maas wrote:
> On Thu August 7 2008, Ted Pavlic wrote:
> 
>> So I wonder if something special should be added to the Vim-LaTeX 
>> documentation to instruct users to change their tex_flavor if they
>> want empty .tex files to load Vim-LaTeX...
> 
> I added some documentation about it here: 
> http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ#faq-not-loaded-vim7
>  
> http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html
> 
> 
> Regards, Till
> 
> 
> ------------------------------------------------------------------------
> 
> 
> -------------------------------------------------------------------------
>  This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK
> & win great prizes Grand prize is a trip for two to an Open Source
> event anywhere in the world 
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> 
> 
> ------------------------------------------------------------------------
> 
> 
> _______________________________________________ Vim-latex-devel
> mailing list Vim...@li... 
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

Re: [Vim-latex-devel] Adding latex suite hooks for .w file type

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

> I'd like to enable latex suite within my CWEB source files (.w 
> extension).  Vim has a cweb syntax option (set syntax=cweb).  Any idea 
> how to trigger loading latex suite for .w files?  I've tried copying my 
> ~/.vim/ftplugin/tex.vim and tex_latexSuite.vim to parallel versions 
> starting with 'w', but no luck yet.

Try copying (or symlinking)

~/.vim/ftplugin/tex_latexSuite.vim

to

~/.vim/ftplugin/cweb_latexSuite.vim

That should trigger loading the suite for files of the "cweb" type.

(note: if you type ":set ft?" in command mode when you're editing such a 
file, you'll see it's filetype is "cweb" and not "w")

--Ted


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

[Vim-latex-devel] Adding latex suite hooks for .w file type

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

Hi all,

I'd like to enable latex suite within my CWEB source files (.w extension).
Vim has a cweb syntax option (set syntax=cweb).  Any idea how to trigger
loading latex suite for .w files?  I've tried copying my
~/.vim/ftplugin/tex.vim and tex_latexSuite.vim to parallel versions starting
with 'w', but no luck yet.

Any pointers appreciated,
Rhys