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

Re: [Vim-latex-devel] taglist.vim integration

[Srinath A. <sr...@fa...>]

Hi Luc,

On Tue, 23 Sep 2003, Luc Hermitte wrote:

> Nothing has to be done to integrate a spellchecker with LaTeX-suite and
> vice-versa.
> [BTW, i definitively prefer lh-vimspell [1] ;-)
>  which works correctly which Aspell under MsWindows]
>
> --
> Luc Hermitte
> [1] http://hermitte.free.fr/vim/ressources/vimfiles/doc/VS_help.html

I wanted to give vhspell a quick try but unfortunately, there were a few
bugs. I followed the installation instructions best I could... I
downloaded vim-spell.tar.gz into my ~/vimfiles directory, tar xvzf'ed it
and then cp'ed the macros/lhVimSpell.vim file into my ~/vimfiles/plugin
directory. I then opened a new text file and pressed <F4> and got the
following errors:

----------------------------------%<----------------------------------
E492: Not an editor command: :SearchInRuntime :VSSearchSyn syntax/.vim
line   12:
E121: Undefined variable: s:SearchSynFile
E15: Invalid expression: '' != s:SearchSynFile
line   11:
E492: Not an editor command: :SearchInRuntime :VSSearchSyn syntax/.vim
line   12:
E121: Undefined variable: s:SearchSynFile
E15: Invalid expression: '' != s:SearchSynFile
line   11:
E492: Not an editor command: :SearchInRuntime :VSSearchSyn syntax/.vim
line   12:
E121: Undefined variable: s:SearchSynFile
E15: Invalid expression: '' != s:SearchSynFile
line   11:
E492: Not an editor command: :SearchInRuntime :VSSearchSyn syntax/.vim
line   12:
E121: Undefined variable: s:SearchSynFile
E15: Invalid expression: '' != s:SearchSynFile
----------------------------------%<----------------------------------

There are actually lots more such errors which keep repeating, but they
look like they are caused by the same basic thing. BTW, I got the
.tar.gz file from the location indicated in

http://hermitte.free.fr/vim/ressources/vimfiles/doc/VS_help.html

namely I got the archive

http://hermitte.free.fr/vim/ressources/vim-spell.tar.gz

BTW, the screenshot looks pretty cool.

Srinath

Re: [Vim-latex-devel] taglist.vim integration

[Luc H. <her...@fr...>]

* On Mon, Sep 22, 2003 at 11:45:28AM +0200, mi...@wp... <mi...@wp...> wrote:
> I'd like to add better support for ctags and taglist.vim
> (as the best interface for this feature).
> 
> Currently creating of tags file is made with ltags perl script.
> But this of course requires perl in situation when this is not
> necessary. Ctags can create tags file depending on options given as
> configuration file or command line options.

Why don't you use aux2tags.vim ? It works very well to generate the
tags. And it doesn't require ctags or any other external tool but
LaTeX.
However, it does not present any information ; and presenting the
structure of the document as a tree sounds a great idea!

> ps. Maybe we should create "insitution" like official LaTeX-Suite
> plugins? Provide better interfaces for them and so on?
> Current candidates:
> Spellchecing: engspchk, vimspell

Nothing has to be done to integrate a spellchecker with LaTeX-suite and
vice-versa.
[BTW, i definitively prefer lh-vimspell [1] ;-)
 which works correctly which Aspell under MsWindows]

-- 
Luc Hermitte
[1] http://hermitte.free.fr/vim/ressources/vimfiles/doc/VS_help.html

Re: [Vim-latex-devel] Delete Menus when done with editing tex file

[Luc H. <her...@fr...>]

hello,

* On Sun, Sep 21, 2003 at 11:47:43AM -0700, Srinath Avadhanula <sr...@fa...> wrote:
> >  au BufLeave FileType=tex call delteMenu() <CR>
> >
> This topic has come up in the past, and unfortunately, I have been
> putting a damper on things. We thought of something like
> 
> au BufEnter * :call Tex_CheckMenus()
> 
> Tex_CheckMenus() will check if the buffer being entered is a tex
> buffer and if so, leave the menus intact if they are already present
> and regerate the menus if they no longer exist.  Otherwise it will
> kill the menus. However, regenerating menus is a very time-consuming
> process and I beleive it will be more of an annoyance than a
> time-saver. 

In an ftplugin, I'm disabling the menus associated. It is not as slow as
deleting every thing, and it can be done on the root menu. Re-enabling
the menu is very simple as well.
=>
    if g:want_buffermenu_for_tex == 2 " {{{
      augroup LTXMenuEnableDisable
	au!
	au BufEnter		*.tex,*.sty amenu enable LaTeX
	au BufLeave,BufUnload	*.tex,*.sty amenu disable LaTeX
      augroup END
    endif " }}}

It won't disapear from the menu-bar, but at least it can't be used.

-- 
Luc Hermitte
http://hermitte.free.fr/vim/

[Vim-latex-devel] taglist.vim integration

[<mi...@wp...>]

Hello,

I'd like to add better support for ctags and taglist.vim
(as the best interface for this feature).

Currently creating of tags file is made with ltags perl script.
But this of course requires perl in situation when this is not
necessary. Ctags can create tags file depending on options given as
configuration file or command line options.

Inspired by Florent Manens Tip #453 I inserted this section to main.vim
and everything works without changing or adding anything to
non-latexSuite files!

" 
========================================================
======================
" Settings for taglist.vim plugin
" 
========================================================
====================== 
" Inspiration Florent Manens Tip #453

if !exists("g:tlist_tex_settings") 
	let g:tlist_tex_settings = 'tex;s:section;c:chapter;l:label;r:ref'
endif

if exists("Tlist_Ctags_Cmd")
	let s:tex_ctags = Tlist_Ctags_Cmd
else
	let s:tex_ctags = 'ctags' " Configurable in texrc?
endif

let Tlist_Ctags_Cmd = s:tex_ctags ." --langdef=tex --
langmap=tex:.tex.ltx.latex"
\.' --regex-tex="/\\\\subparagraph[ \t]*\*?\{[ \t]*([^}]*)\}/-   \1/p,subparagraph/"'
\.' --regex-tex="/\\\\paragraph[ \t]*\*?\{[ \t]*([^}]*)\}/+  \1/p,paragraph/"'
\.' --regex-tex="/\\\\subsubsection[ \t]*\*?\{[ \t]*([^}]*)\}/+ \1/s,subsubsection/"'
\.' --regex-tex="/\\\\subsection[ \t]*\*?\{[ \t]*([^}]*)\}/+\1/s,subsection/"'
\.' --regex-tex="/\\\\section[ \t]*\*?\{[ \t]*([^}]*)\}/\1/s,section/"'
\.' --regex-tex="/\\\\chapter[ \t]*\*?\{[ \t]*([^}]*)\}/\1/c,chapter/"'
\.' --regex-tex="/\\\\part[ \t]*\*?\{[ \t]*([^}]*)\}/\1/p,part/"'
\.' --regex-tex="/\\\\label[ \t]*\*?\{[ \t]*([^}]*)\}/\1/l,label/"'
\.' --regex-tex="/\\\\ref[ \t]*\*?\{[ \t]*([^}]*)\}/\1/r,ref/"'

" -------------------------------------------------------

It could be of course placed in texrc to be better accessible by
end-user.
But before final commitment here are few things to discuss:
1. 
This is calling external command - eternal problems with quoting.
Srinath - could you test it on Windows?
2.
Pluses and spaces are for creating "structure". We could go further and
make something more like in slrn or mutt with "real" trees for
sectioning structure. This chars are in extended ASCII - may cause
problems.
3.
Of course: what tags should be included?
ltags has:
cite, citeonline - are these really useful?
label
bibliography
bibitem, @....{

I'd like to make:
As far as possible full sectioning structure
abstract,part,chapter,section,subsection,subsubsection,paragraph,subparagra
ph
appendix,bibliography,thebibliography,bibitem
frontmatter,mainmatter,backmatter?
label,

I don't think things like cite, ref and so on are useful. Other
opinions?

Maybe \captions? This is not core LaTeX element as \label but more
readable for user when he wants to jump to specific element?

Tested with latest taglist.vim (2.8) and ctags 5.5.2 (should work >=5.0)

Unfortunately I am cutted off from CVS. Srinath, if you like it commit
it in this form or after changes.

m.

ps. Maybe we should create "insitution" like official LaTeX-Suite
plugins? Provide better interfaces for them and so on?
Current candidates:
Spellchecing: engspchk, vimspell
Tags: taglist

Any other ideas?

Re: [Vim-latex-devel] Delete Menus when done with editing tex file

[<mi...@wp...>]

On 21 Sep 2003 at 15:24, Aditya Mahajan wrote:

> >>  There is something that I find a little irritating with the latex-suite
> >> package. The menus are excellent but they occupy a lot of space on the
> >> gui. So whenever I am finished with the editing of the latex file, I do
> >> not want the menu anymore. There are other menus that I want to use, but
> >> there is no way in which the latex-suite menus can be turned off when I
> >> do not need them.

Other problem with menus: they are really heavy.

One idea: extract from current math menus those elements which are in basic latex (without ams packages). Load it by default. Add 
to this option "Load advanced math elements". If chosen unload current menu and load full math menus. Of course here should be: 
"Unload advanced math". Because math is responsible for ca. 60% of all menus it should reduce overall number of menus about 
30%. This is similar trick to this with syntax menus in "core Vim".
Srinath what do you think about that? I came across that some time ago but this is really boring to make :)
Other solution is to get rid of "exe" statements with menus but with it we lost possibility of moving menus.

m.

Re: [Vim-latex-devel] Delete Menus when done with editing tex file

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

Hi Srinath,

Today  Srinath Avadhanula wrote about Re: [Vim-latex-devel] Delete Menus...

>Aditya,
>
>> Hi,
>>  There is something that I find a little irritating with the latex-suite
>> package. The menus are excellent but they occupy a lot of space on the
>> gui. So whenever I am finished with the editing of the latex file, I do
>> not want the menu anymore. There are other menus that I want to use, but
>> there is no way in which the latex-suite menus can be turned off when I
>> do not need them.
>>  Is there some way in which the filetype menus can be associated with
>> the local buffer, so that when I delete the buffer containing the tex
>> file then the tex menu is automatically deleted.
>>  Another mehtod could be that there is something like
>>  au BufLeave FileType=tex call delteMenu() <CR>
>>
>This topic has come up in the past, and unfortunately, I have been
>putting a damper on things. We thought of something like
>
>au BufEnter * :call Tex_CheckMenus()
>
>(note BufEnter instead of BufLeave). Tex_CheckMenus() will check if the
>buffer being entered is a tex buffer and if so, leave the menus intact
>if they are already present and regerate the menus if they no longer
>exist.  Otherwise it will kill the menus. However, regenerating menus is
>a very time-consuming process and I beleive it will be more of an
>annoyance than a time-saver. Also, the menus which are created by
>Latex-suite are not created by a single function but by various
>sub-functions distributed in various scripts. For something like this to
>work, those things will have to pulled together... Better still, all
>those various places will create menus independently, but on a
>LatexSuiteCreateMenus event which could be fired from Tex_CheckMenus as
>needed.
>
>You know, I do not want to veto against this or anything. As of right
>now, I am running short on time, so this might have to wait for a while
>(3-4 weeks).
>
I understand, you guys are also under a lot of pressure and to have
developed such a great package does take a lot of time and effort.
>
>> where delteMenu is a function that deletes the menu.
>>
>> Otherwise it could be a entry (with a corresponding command) in the
>> tex-Suite menu. This will be a much better option as I am not sure how
>> the previous two will affect the speed of gvim. As it is gvim runs
>>
>The other method of listing all of latex-suite's menus under a single
>master menu is already possible. Unfortunately, this does not seem to be
>documented :( You have to set the value of g:Tex_MenuPrefix to something
>which includes a '.' in it. The default value is 'TeX'. This creates
>TeX-Suite, TeX-Packages etc. If you set it to 'Latex-Suite.' then all
>menus will be nested under the 'Latex-Suite' menu.
>

I did not know about this feature. This is close to what I want. I tried
with
 TexLet g:Tex_MenuPrefix="Late&x-Suite."

and then tearoff Tex-Suite

This works fine for my requirements. Infact what I find better is
 TexLet g:Tex_MenuPrefix="]Latex-Suite"
 and then tear-off. This way, it does not clutter my menu space at all,
and as I use the menu infrequently, this is just about perfect.

Thanks for your help

Cheers
Aditya

>HTH
>Srinath
>

Re: [Vim-latex-devel] Delete Menus when done with editing tex file

[Srinath A. <sr...@fa...>]

Aditya,

On Sat, 20 Sep 2003, Aditya Mahajan wrote:

> Hi,
>  There is something that I find a little irritating with the latex-suite
> package. The menus are excellent but they occupy a lot of space on the
> gui. So whenever I am finished with the editing of the latex file, I do
> not want the menu anymore. There are other menus that I want to use, but
> there is no way in which the latex-suite menus can be turned off when I
> do not need them.
>  Is there some way in which the filetype menus can be associated with
> the local buffer, so that when I delete the buffer containing the tex
> file then the tex menu is automatically deleted.
>  Another mehtod could be that there is something like
>  au BufLeave FileType=tex call delteMenu() <CR>
>
This topic has come up in the past, and unfortunately, I have been
putting a damper on things. We thought of something like

au BufEnter * :call Tex_CheckMenus()

(note BufEnter instead of BufLeave). Tex_CheckMenus() will check if the
buffer being entered is a tex buffer and if so, leave the menus intact
if they are already present and regerate the menus if they no longer
exist.  Otherwise it will kill the menus. However, regenerating menus is
a very time-consuming process and I beleive it will be more of an
annoyance than a time-saver. Also, the menus which are created by
Latex-suite are not created by a single function but by various
sub-functions distributed in various scripts. For something like this to
work, those things will have to pulled together... Better still, all
those various places will create menus independently, but on a
LatexSuiteCreateMenus event which could be fired from Tex_CheckMenus as
needed.

You know, I do not want to veto against this or anything. As of right
now, I am running short on time, so this might have to wait for a while
(3-4 weeks).


> where delteMenu is a function that deletes the menu.
>
> Otherwise it could be a entry (with a corresponding command) in the
> tex-Suite menu. This will be a much better option as I am not sure how
> the previous two will affect the speed of gvim. As it is gvim runs
>
The other method of listing all of latex-suite's menus under a single
master menu is already possible. Unfortunately, this does not seem to be
documented :( You have to set the value of g:Tex_MenuPrefix to something
which includes a '.' in it. The default value is 'TeX'. This creates
TeX-Suite, TeX-Packages etc. If you set it to 'Latex-Suite.' then all
menus will be nested under the 'Latex-Suite' menu.

HTH
Srinath

Re: [Vim-latex-devel] Features like preview-latex

[Srinath A. <sr...@fa...>]

Hi Aditya,

On Fri, 19 Sep 2003, Aditya Mahajan wrote:

> this package for preview-latex (http://preview-latex.sourceforge.net/) for
> xemacs, and by the look of it, it looks really impressive.
>  The main feature that I am concerned about is the ability to display
> math. I always liked that feature in lyx also. I am wondering, why it can
> not be done in (g)vim. I think that one could use a unicode encoding for
> the file and replace \sum by sigma from unicode and go about it. The only
>
I must admit preview-latex does sound extremeley impressive and might be
very useful. But IMHO you underestimate the complexity of rendering
equations using unicode fonts. Simple things like $x^2 + y^2 = z^2$
might be fine, because most probably we could just use the singe line
itself, but with more complex equations where the latex source occupies
much more space than the equation displayed, things will get very very
complex indeed.

You will notice that preview-latex actually runs latex and then
ghostscript to generate the bitmap and then displays that inline in the
document. I beleive that a project which aims to do something like this
in native vim script is going to be as complicated as LaTeX itself!

Infact, an easier solution would be to patch VIM itself to allow for
inline graphics and then use the same route which preview-latex does.
Ofcourse, having delved into the VIM source only very briefly, I do not
know if this is even feasible.

Quite frankly, I would not even attempt something this complicated
myself :(

Also, for simple things like displaying the actual greek character theta
instead of \theta, the greek Sigma character in place of \sum etc, I
beleive someone has already done something like that in VIM. I do not
have the URL handy though. And I wonder how they handle the case where
in some places, the user wants \sum but wants to display \sigma in other
places...

Srinath

[Vim-latex-devel] =?GB2312?B?1sLAz7/Nu6fQxaOh?=

[<xm...@to...>]

尊敬的老客户：
　　您好！
　　恒速达网络非常感谢您在这三年多来对我们的支持与厚爱！
    我司今年加强了对网站系统开发的研究，现公司有专职网页开发技术员十几名（工作经验均在三年以上），
同时还高薪聘请了不少网络上的高手做兼职。公司为扩大规模从9月1号开始做网站实行全面特惠价制作，相关
信息请上我们网站　http://www.88dns.cn 了解。
　　另外在加强网站开发的同时我们也不忘老本行，最近新上架了一批至强服务器，老客户如有需要换空间的
请及时与我们联系，您只要续费一年就可以更换高品质的服务器了，如另申请空间我们将给予　9折优惠（对于
老客户介绍的新客户也给予同样的优惠）。
　　    
　　我们本着诚信为本才有今日之成就，我们承诺　24小时为您服务，同时支持　QQ　24小时在线咨询！

注：为感谢广大老客户的支持,推出　9折优惠　的只限以下几类套餐，欲购从速!
  
 1、200M（纯HTML空间）+ 送一国际域名，仅售150元/年
 2、50M空间+50M企业邮局 + 支持ASP，CGI + 送一国际域名，仅售248元/年
 3、100MP空间+100M企业邮局 + 支持ASP，CGI，ACCESS + 送一国际域名，仅售280元/年 
 4、200MP空间+200M企业邮局 + 支持ASP，CGI，ACCESS + 送一国际域名，仅售330元/年


　　同时欢迎您加入我们代理行列来，我们将给您更加优惠的服务！

  详情请见：http://www.88dns.cn  欢迎咨询，选购!
  电话咨询：0592-6026652 / 8667174 / 8375020 / 8919334
   邮件： of...@88...
  QQ在线： 57729502　/　33925614　/　40327558 

  恒速达网络销售部：  宋先生/郑先生/宋小姐

*****此邮件为商业信函，如果给你造成不便请原谅，谢谢！ 
   This mail is a business letter .If you are uninterested in this ,please delete it ;If you do 
not hope to receive this mail again ,please go to xm...@to... ,fill ni your mail 
address ,and we will filter it out of our mail list! 
   Thank your!  
**********************************************
　
　　　　祝您中秋快乐、全家团圆， 好运天天有、幸运常伴随!!!
                         
　　　　　　　　　　　　　　　　　　　　　　　　　　　
　　　　　　　　　　　　　　　　　　　　　　　　　　　　恒速达网络

[Vim-latex-devel] Delete Menus when done with editing tex file

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

Hi,
 There is something that I find a little irritating with the latex-suite
package. The menus are excellent but they occupy a lot of space on the
gui. So whenever I am finished with the editing of the latex file, I do
not want the menu anymore. There are other menus that I want to use, but
there is no way in which the latex-suite menus can be turned off when I
do not need them.
 Is there some way in which the filetype menus can be associated with
the local buffer, so that when I delete the buffer containing the tex
file then the tex menu is automatically deleted.
 Another mehtod could be that there is something like
 au BufLeave FileType=tex call delteMenu() <CR>

where delteMenu is a function that deletes the menu.

Otherwise it could be a entry (with a corresponding command) in the
tex-Suite menu. This will be a much better option as I am not sure how
the previous two will affect the speed of gvim. As it is gvim runs
slightly slower than vim. If you guys want then maybe I could try to
write the deleteBuffer function and you can figure out where it should
go.

Cheers
aditya

[Vim-latex-devel] Features like preview-latex

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

Hi,
 I really find latex suite really useful. I work on latex a lot, started
with lyx, but once I got familiar with the code, shifted to gvim (which
happens to be my favourite editor). I was just browsing and came though
this package for preview-latex (http://preview-latex.sourceforge.net/) for
xemacs, and by the look of it, it looks really impressive.
 The main feature that I am concerned about is the ability to display
math. I always liked that feature in lyx also. I am wondering, why it can
not be done in (g)vim. I think that one could use a unicode encoding for
the file and replace \sum by sigma from unicode and go about it. The only
problem that I see is that vim does not allow one to use different fonts
and different font sizes for different lines (after all it is a humble
text editor). But how about something like this,
 detect when you are in math mode and keep three lines for display for
each math mode (or open the display in another preview window and keep
three line in that) with subscripts and superscripts going at respective
places. The main advantage is that if there is a sytax error, you will
know immediately and will not always have to compile to see how it looks
like.

Just musing...

Cheers
aditya

Re: [Vim-latex-devel] Latex Suite suggestions for folding

[Srinath A. <sr...@fa...>]

On Mon, 15 Sep 2003, Aditya Mahajan wrote:
>
> ... always expands to $\cdots$ This is annoying it I just want to put ...
> at some place in the comments. Is there some way in which you can check if
> we are in the math mode or not and then only make the substitution.
>
Unfortunately, detecting math mode is not very easy in vim because
certain things like \pi etc have a highlighting group which is called
texCommand or something similar. This syntax group can be contained both
in normal text as well as inside math. As of now, if latex-suite detects
that the amsmath package is included, then it will always put \dots
which amsmath adjusts correctly. Otherwise, it puts \cdots in math mode
(if detected), otherwise it puts \ldots. I would recommend using \dots
always instead of 3 dots anyway...

> Add folds for:
>  abstract
>  keywords "Both of these are useful while writing papers
>
>  " include folds for amsmath package
>  align/alignat
>  gather
>  intertext
>
Mikolaj added these items to folding.vim

>  "include fold for
>  sidewaysfigure
>
I am not sure where this environment occurs. Its not standard latex.
I am wondering therefore if its advisable to add these to the standard
latex-suite thingie?

> These environments need to be added in the TexFoldTextFunction() also.
> Also when I include a bibliography in the file, it gets folded with the
> last section. I find this very annoying and found out that this can be
> removed by
>  ^\s*\\begin{thebibliography}|^\s*\\bibliography
>  tags in the fold end pattern for section, subsection, subsubsection and
> chapter.
>
I'll fix this.

Thanks for the suggestions.
Srinath

Re: [Vim-latex-devel] Latex Suite suggestions for folding

[Srinath A. <sr...@fa...>]

On Wed, 17 Sep 2003, Mikolaj Machowski wrote:

> > These environments need to be added in the TexFoldTextFunction() also.
> > Also when I include a bibliography in the file, it gets folded with the
> > last section. I find this very annoying and found out that this can be
> > removed by
> >  ^\s*\\begin{thebibliography}|^\s*\\bibliography
> >  tags in the fold end pattern for section, subsection, subsubsection and
> > chapter.
>
> I don't touch this. Maybe someone better oriented in folding.
>
I will patch folding.vim with the above suggestions soon.


Thanks,
Srinath

Re: [Vim-latex-devel] Latex Suite suggestions for folding

[Mikolaj M. <mi...@wp...>]

Dnia Monday 15 of September 2003 23:13, Aditya Mahajan napisał:
> Hello,
>
> Add folds for:
>  abstract
>  keywords "Both of these are useful while writing papers
>
>  " include folds for amsmath package
>  align/alignat
>  gather
>  intertext

OK. I will include this. AMS names are almost part of standard LaTeX.

>
>  "include fold for
>  sidewaysfigure

What is this? Package specific environments should go to package files
but I am afraid this is impossible at the moment. Srinath?

> These environments need to be added in the TexFoldTextFunction() also.
> Also when I include a bibliography in the file, it gets folded with the
> last section. I find this very annoying and found out that this can be
> removed by
>  ^\s*\\begin{thebibliography}|^\s*\\bibliography
>  tags in the fold end pattern for section, subsection, subsubsection and
> chapter.

I don't touch this. Maybe someone better oriented in folding.

m.

-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/

[Vim-latex-devel] Latex Suite suggestions for folding

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

Hello,

 Latex-Suite is a really amazing bundle of packages. I have been using it
for quite some time and recently read on the c.t.t. newsgroup about the
release of its newer version. There are certain things that I had already
added to the file that I have and think that it will be good if they are
also included in the new release.

... always expands to $\cdots$ This is annoying it I just want to put ...
at some place in the comments. Is there some way in which you can check if
we are in the math mode or not and then only make the substitution.

Some suggested changes for File: folding.vim

Add folds for:
 abstract
 keywords "Both of these are useful while writing papers

 " include folds for amsmath package
 align/alignat
 gather
 intertext

 "include fold for
 sidewaysfigure

These environments need to be added in the TexFoldTextFunction() also.
Also when I include a bibliography in the file, it gets folded with the
last section. I find this very annoying and found out that this can be
removed by
 ^\s*\\begin{thebibliography}|^\s*\\bibliography
 tags in the fold end pattern for section, subsection, subsubsection and
chapter.

This is my folding.vim file

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
"=============================================================================
" 	     File: folding.vim
"      Author: Srinath Avadhanula
" 	  Version: 1.0
"     Created: Tue Apr 23 05:00 PM 2002 PST
"
"  Description: functions to interact with Syntaxfolds.vim
"=============================================================================

nnoremap <unique> <Plug>Tex_RefreshFolds :call MakeTexFolds(1)<cr>

augroup LatexSuite
	au LatexSuite User LatexSuiteFileType
		\ call Tex_Debug('folding.vim: catching LatexSuiteFileType') |
		\ call s:SetFoldOptions()
augroup END

" SetFoldOptions: sets maps for every buffer {{{
" Description:
function! <SID>SetFoldOptions()
	if exists('b:doneSetFoldOptions')
		return
	endif
	let b:doneSetFoldOptions = 1

	setlocal foldtext=TexFoldTextFunction()

	if g:Tex_Folding && g:Tex_AutoFolding
		call MakeTexFolds(0)
	endif

	if g:Tex_Folding && !hasmapto('<Plug>Tex_RefreshFolds')
		nmap <silent> <buffer> <Leader>rf  <Plug>Tex_RefreshFolds
	endif

endfunction " }}}
" MakeTexFolds: function to create fold items for latex. {{{
"
" used in conjunction with MakeSyntaxFolds().
" see ../plugin/syntaxFolds.vim for documentation
"
function! MakeTexFolds(force)
	if exists('g:Tex_Folding') && !g:Tex_Folding
		return
	endif
	if &ft != 'tex'
		return
	end

	" the order in which these calls are made decides the nestedness. in
	" latex, a table environment will always be embedded in either an item or
	" a section etc. not the other way around. so we first fold up all the
	" tables. and then proceed with the other regions.

	let b:numFoldItems = 0

	" ========================================================================
	" How to add new folding items {{{
	" ========================================================================
	"
	" Each of the following function calls defines a syntax fold region. Each
	" definition consists of a call to the AddSyntaxFoldItem() function.
	"
	" The order in which the folds are defined is important. Juggling the
	" order of the function calls will create havoc with folding. The
	" "deepest" folding item needs to be called first. For example, if
	" the \begin{table} environment is a subset (or lies within) the \section
	" environment, then add the definition for the \table first.
	"
	" The AddSyntaxFoldItem() function takes either 4 or 6 arguments. When it
	" is called with 4 arguments, it is equivalent to calling it with 6
	" arguments with the last two left blank (i.e as empty strings)
	"
	" The explanation for each argument is as follows:
	"    startpat: a line matching this pattern defines the beginning of a fold.
	"    endpat  : a line matching this pattern defines the end of a fold.
	"    startoff: this is the offset from the starting line at which folding will
	"              actually start
	"    endoff  : like startoff, but gives the offset of the actual fold end from
	"              the line satisfying endpat.
	"              startoff and endoff are necessary when the folding region does
	"              not have a specific end pattern corresponding to a start
	"              pattern. for example in latex,
	"              \begin{section}
	"              defines the beginning of a section, but its not necessary to
	"              have a corresponding
	"              \end{section}
	"              the section is assumed to end 1 line _before_ another section
	"              starts.
	"    startskip: a pattern which defines the beginning of a "skipped" region.
	"
	"               For example, suppose we define a \itemize fold as follows:
	"               startpat =  '^\s*\\item',
	"               endpat = '^\s*\\item\|^\s*\\end{\(enumerate\|itemize\|description\)}',
	"               startoff = 0,
	"               endoff = -1
	"
	"               This defines a fold which starts with a line beginning with an
	"               \item and ending one line before a line beginning with an
	"               \item or \end{enumerate} etc.
	"
	"               Then, as long as \item's are not nested things are fine.
	"               However, once items begin to nest, the fold started by one
	"               \item can end because of an \item in an \itemize
	"               environment within this \item. i.e, the following can happen:
	"
	"               \begin{itemize}
	"               \item Some text <------- fold will start here
	"                     This item will contain a nested item
	"                     \begin{itemize} <----- fold will end here because next line contains \item...
	"                     \item Hello
	"                     \end{itemize} <----- ... instead of here.
	"               \item Next item of the parent itemize
	"               \end{itemize}
	"
	"               Therefore, in order to completely define a folding item which
	"               allows nesting, we need to also define a "skip" pattern.
	"               startskip and end skip do that.
	"               Leave '' when there is no nesting.
	"    endskip: the pattern which defines the end of the "skip" pattern for
	"             nested folds.
	"
	"    Example:
	"    1. A syntax fold region for a latex section is
	"           startpat = "\\section{"
	"           endpat   = "\\section{"
	"           startoff = 0
	"           endoff   = -1
	"           startskip = ''
	"           endskip = ''
	"    Note that the start and end patterns are thus the same and endoff has a
	"    negative value to capture the effect of a section ending one line before
	"    the next starts.
	"    2. A syntax fold region for the \itemize environment is:
	"           startpat = '^\s*\\item',
	"           endpat = '^\s*\\item\|^\s*\\end{\(enumerate\|itemize\|description\)}',
	"           startoff = 0,
	"           endoff = -1,
	"           startskip = '^\s*\\begin{\(enumerate\|itemize\|description\)}',
	"           endskip = '^\s*\\end{\(enumerate\|itemize\|description\)}'
	"     Note the use of startskip and endskip to allow nesting.
	"
	"
	" }}}
	" ========================================================================
	" {{{ footnote
	"call AddSyntaxFoldItem (
	"	\ '^\s*\\footnote{',
	"	\ '^\s*}',
	"	\ 0,
	"	\ 0
	"	\ )
	" }}}
	" {{{ intertext
	call AddSyntaxFoldItem (
		\ '^\s*\\intertext{',
		\ '^\s*}',
		\ 0,
		\ 0
		\ )
	 }}}
	" {{{ abstract
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{abstract}',
		\ '^\s*\\end{abstract}',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ keywords
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{keywords}',
		\ '^\s*\\end{keywords}',
		\ 0,
		\ 0
		\ )
	" }}}
" {{{ thebibliography
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{thebibliography}',
		\ '^\s*\\end{thebibliography}',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ biography
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{biography}',
		\ '^\s*\\end{biography}',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ biographynophoto
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{biographynophoto}',
		\ '^\s*\\end{biographynophoto}',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ table
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{table}',
		\ '^\s*\\end{table}',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ figure
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{figure',
		\ '^\s*\\end{figure}',
		\ 0,
		\ 0
		\ )
	" }}}
  	" {{{ sidewaysfigure
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{sidewaysfigure',
		\ '^\s*\\end{sidewaysfigure}',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ align/alignat
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{align',
		\ '^\s*\\end{align',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ gather
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{gather',
		\ '^\s*\\end{gather',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ equation/eqnarray
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{eq',
		\ '^\s*\\end{eq',
		\ 0,
		\ 0
		\ )
	" }}}
	" {{{ items
	call AddSyntaxFoldItem (
		\ '^\s*\\item',
		\ '^\s*\\item\|^\s*\\end{\(enumerate\|itemize\|description\)}',
		\ 0,
		\ -1,
		\ '^\s*\\begin{\(enumerate\|itemize\|description\)}',
		\ '^\s*\\end{\(enumerate\|itemize\|description\)}'
		\ )
	" }}}
	" {{{ subsubsection
	call AddSyntaxFoldItem (
		\ '^\s*\\subsubsection\W',
		\ '^\s*\\appendix\W\|^\s*\\subsubsection\W\|^\s*\\subsection\W\|^\s*\\section\W\|^\s*\\bibliography\|^\s*%%fakesection\|^\s*\\chapter\W\|^\s*\\begin{thebibliography\|^\s*\\begin{slide\|^\s*\\end{document',
		\ 0,
		\ -1,
		\ )
	" }}}
	" {{{ subsection
	call AddSyntaxFoldItem (
		\ '^\s*\\subsection\W',
		\ '^\s*\\appendix\W\|^\s*\\subsection\W\|^\s*\\section\W\|^\s*%%fakesection\|^\s*\\bibliography\|^\s*\\chapter\W\|^\s*\\begin{slide\|^\s*\\begin{thebibliography\|^\s*\\end{document',
		\ 0,
		\ -1,
		\ )
	" }}}
	" {{{ section
	call AddSyntaxFoldItem (
		\ '^\s*\\section\W',
		\ '^\s*\\appendix\W\|^\s*\\section\W\|^\s*\\bibliography\|^\s*%%fakesection\|^\s*\\chapter\W\|^\s*\\begin{slide\|^\s*\\begin{thebibliography\|^\s*\\end{document',
		\ 1,
		\ -1,
		\ )
	" }}}
	" {{{ fakesection (for forcinga fold item manually)
	call AddSyntaxFoldItem (
		\ '^\s*%%fakesection',
		\ '^\s*\\appendix\W\|^\s\\section\W\|^\s*%%fakesection\|^\s*\\bibliography\|^\s*\\chapter\W\|^\s*\\begin{slide\|^\s*\\begin{thebibliography\|^\s*\\end{document',
		\ 0,
		\ -1,
		\ )
	" }}}
	" {{{ chapter
	call AddSyntaxFoldItem(
		\ '^\s*\\chapter\W',
		\ '^\s*\\appendix\W\|^\s*\\chapter\W\|^\s*\\bibliography\|^\s*\\begin{slide\|^\s*\\begin{thebibliography\|^\s*\\end{document',
		\ 0,
		\ -1
		\ )
	" }}}
	" {{{ slide
	call AddSyntaxFoldItem (
		\ '^\s*\\begin{slide',
		\ '^\s*\\appendix\W\|^\s*\\chapter\W\|^\s*\\end{slide\|^\s*\\end{document',
		\ 0,
		\ 0
		\ )
	" }}}

	call MakeSyntaxFolds(a:force)
	normal! zv
endfunction

" }}}
" TexFoldTextFunction: create fold text for folds {{{
function! TexFoldTextFunction()
	if getline(v:foldstart) =~ '^\s*\\begin{'
		let header = matchstr(getline(v:foldstart), '^\s*\\begin{\zs\(figure\|sidewaysfigure\|table\|equation\|eqnarray\|gather\|align\|abstract\|keywords\|thebibliography\)[^}]*\ze}')

		let caption = ''
		let label = ''
		let i = v:foldstart
		while i <= v:foldend
			if getline(i) =~ '\\caption'
				let caption = matchstr(getline(i), '\\caption{\zs.*')
				let caption = substitute(caption, '\zs}[^}]*$', '', '')
			elseif getline(i) =~ '\\label'
				let label = matchstr(getline(i), '\\label{\zs.*')
				let label = substitute(label, '\zs}[^}]*$', '', '')
			end

			let i = i + 1
		endwhile

		let ftxto = foldtext()
		" if no caption found, then use the second line.
		if caption == ''
			let caption = getline(v:foldstart + 1)
		end

		let retText = matchstr(ftxto, '^[^:]*').': '.header.' ('.label.') : '.caption
		return retText
	else
		return foldtext()
	end
endfunction
" }}}

" vim:fdm=marker:ff=unix:noet:ts=4:sw=4
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Re: [Vim-latex-devel] <F5>, theorem and NO label.

[Srinath A. <sr...@fa...>]

On Wed, 10 Sep 2003, Bart Kastermans wrote:

> Most of my theorems are not labelled.  So I want to disable
> the ``\label{}<++>'' from showing up.  Can you tell me how
> to achieve this?
>
Okay... I just added the ability to redefine the expansions produced by
latex-suite. Download the latest 1.5 RC 1 and then see:

http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-macros.html#Tex_Env_name

Srinath

[Vim-latex-devel] =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCF2IzIyLyEmIzMyLyEmIzUyLyM5QGlLfDFfPH1GfjxUQjM9UCE8O3Y8Qj5aNXIzTkcnN14bKEI=?=

[<no...@or...>]

＜事業者名＞身元保証受託協会・特定商取引法に基づく表示です＜
不要の場合は、 http://www12.ocn.ne.jp/~hosyou/deny.htmlでお願い
します。他の表示事項はhttp://www12.ocn.ne.jp/~hosyou/77/でご
参照願います＞
☆〜〜〜〜〜〜〜☆〜〜〜〜〜〜☆〜〜〜〜〜〜☆〜〜〜〜〜☆

 　【５億９千万円証拠有収入在宅保証証券ビジネス権利】
　　
　　　　特別優遇発売中！！サポート制度あります。
　　　　　　　　　　　☆★--◇--★-◆
　　　　　　【２億円・３億円・５億９千万円等の収入者続出】
　　　貴方様も【証拠有ビック収入ビジネスチャンス】のご検討を！！　　
　　　　　　　　
　　　　　　　　　　　
　あの時、１億円があったら・あのとき、２億円の保証があったら
　　　　今は、最高なのに！！今からでも遅くありません！！
　　

■保証証券発行元の全国身元保証受託協会が全責任を持ちます。

高裁判決書が物的証拠・判決書見せます・見る迄は信用しないで下さい。
　☆〜〜〜〜〜〜〜☆〜〜〜〜〜〜☆〜〜〜〜〜〜☆〜〜〜〜〜☆
資料請求は　http://www12.ocn.ne.jp/~hosyou/77/から３億円への一歩
　　　　　　　　　
　　　

Re: [Vim-latex-devel] <F5>, theorem and NO label.

[Srinath A. <sr...@fa...>]

On Wed, 10 Sep 2003, Bart Kastermans wrote:

>   I use vim+latexsuite, and am very happy with how things
> work.  There is just one thing that is starting to get to
> me, and it seems like something that should be easily
> configurable; but I can't find it in the user manual.
>
> When I have a line just containing ``theorem'' and
> press <F5>  I get
> \begin{theorem}
>   \label{}<++>
> \end{theorem}<++>
>
> Most of my theorems are not labelled.  So I want to disable
> the ``\label{}<++>'' from showing up.  Can you tell me how
> to achieve this?
>
Amazingly enough, as of now, there is no simple way to set anything to
change this without modifying latex-suite :(

There have been quite a few requests like this though, so we will
definitely try to find a way to do this better in the future. In the
meanwhile, you will have to patch ftplugin/latex-suite/envmacros.vim,
which ships with latex-suite.

(Basically, all environments in that pattern get a \label in them).

> BTW: I am using latex-suite RC 1 on VIM 6.1.
>
You mean RC 1.5 right?

HTH (for now),
Srinath

Index: envmacros.vim
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/envmacros.vim,v
retrieving revision 1.34
diff -c -r1.34 envmacros.vim
*** envmacros.vim	27 Jun 2003 22:20:16 -0000	1.34
--- envmacros.vim	11 Sep 2003 01:01:22 -0000
***************
*** 554,560 ****
  		endif
  		return VEnclose('\begin{'.a:env.'}', '\end{'.a:env.'}', '\begin{'.a:env.'}', '\end{'.a:env.'}')
  	else
! 		if a:env =~ 'equation*\|eqnarray*\|theorem\|lemma\|equation\|eqnarray\|align\*\|align\>\|multline'
  			let g:aa = a:env
  			return Tex_eqnarray(a:env)
  		elseif a:env =~ "enumerate\\|itemize\\|theindex\\|trivlist"
--- 554,560 ----
  		endif
  		return VEnclose('\begin{'.a:env.'}', '\end{'.a:env.'}', '\begin{'.a:env.'}', '\end{'.a:env.'}')
  	else
! 		if a:env =~ 'equation*\|eqnarray*\|lemma\|equation\|eqnarray\|align\*\|align\>\|multline'
  			let g:aa = a:env
  			return Tex_eqnarray(a:env)
  		elseif a:env =~ "enumerate\\|itemize\\|theindex\\|trivlist"

[Vim-latex-devel] <F5>, theorem and NO label.

[Bart K. <bka...@ya...>]

  I use vim+latexsuite, and am very happy with how things
work.  There is just one thing that is starting to get to
me, and it seems like something that should be easily
configurable; but I can't find it in the user manual.

When I have a line just containing ``theorem'' and
press <F5>  I get
\begin{theorem}
  \label{}<++>
\end{theorem}<++>

Most of my theorems are not labelled.  So I want to disable
the ``\label{}<++>'' from showing up.  Can you tell me how
to achieve this?

BTW: I am using latex-suite RC 1 on VIM 6.1.

Best,
Bart

=====
For contact information, current location and more see:
http://www.kastermans.nl/bart/

Re: [Vim-latex-devel] Tex_UseMakefile, broken logic

[Srinath A. <sr...@fa...>]

On Sun, 7 Sep 2003, Alan Schmitt wrote:

> In compiler.vim, the current logic:
>
> if !g:Tex_UseMakefile || glob('makefile') != '' || glob('Makefile') != ''
>
> is broken: the code is run as long as there is a Makefile. The correct
> code should be:

Oops! Sorry for the mistake. Thanks for the patch. The latest CVS has
it. I will make a release soon.

Srinath

[Vim-latex-devel] Tex_UseMakefile, broken logic

[Alan S. <ala...@po...>]

In compiler.vim, the current logic:

if !g:Tex_UseMakefile || glob('makefile') != '' || glob('Makefile') != ''

is broken: the code is run as long as there is a Makefile. The correct 
code should be:

if g:Tex_UseMakefile && (glob('makefile') != '' || glob('Makefile') != '')

which is run only if "UseMakefile" is 1.

I also added a comment to the variable definition. Attached is a patch.

Alan Schmitt

-- 
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] Error message, but works <- forward search.

[Srinath A. <sr...@fa...>]

On Fri, 5 Sep 2003, Bart Kastermans wrote:

> When I do a forward search \ls with the new version of
> latex suite (the file I installed from was called
> latex-suite-1.5-rc1.zip).  It goes to the right location
> in yap, but displays an error.
>
Thanks for the bug report. This was a small syntax error. Should have
been caught before the RC :(

Oh well! The bug is fixed. The same .zip file should have the corrected
version.

Thanks!
Srinath

[Vim-latex-devel] Error message, but works <- forward search.

[Bart K. <bka...@ya...>]

When I do a forward search \ls with the new version of
latex suite (the file I installed from was called
latex-suite-1.5-rc1.zip).  It goes to the right location
in yap, but displays an error.

As I don't know how to get the text of an error like this
(or the vim version information) into a text file.  I did
the most `straightforward' thing I could think of, and made
two screen captures.

The error:
http://www.kastermans.nl/bart/lsvimerr/latex-suite-error.bmp

My vim version information:
http://www.kastermans.nl/bart/lsvimerr/vimversioninfo.bmp

Best,
Bart

=====
For contact information, current location and more see:
http://www.kastermans.nl/bart/

[Vim-latex-devel] ANN: Latex-suite 1.5 released

[Srinath A. <sr...@fa...>]

Hello,

We are pleased to announce version 1.5 of Latex-suite. Latex-suite is
a comprehensive set of tools to view, edit and compile latex documents
from within vim. Since its release, Latex-suite has become very popular
and correspondingly has had a lot of feedback and bug reports/fixes from
users. Release 1.5 is a major release of Latex-suite containing lots of
enhancements.

The latest version Latex-suite is available at:

http://vim-latex.sourceforge.net/index.php?subject=download

Please download and test. Although its a release candidate, we
anticipate no real problems with it and the 'rc'-ness is only to really
make 100% sure.

The full 1.5 release announcement is quoted below

Thanks,
The Latex-suite team

Latex-suite 1.5 is a substantially improved version over version 1.0
containing many new features and lots and lots of bug-fixes.

Internationalization
--------------------
1. All of latex-suite now uses low end ASCII characters which means that
   there should no longer be any i18n problems due to encoding differences
   etc.

Package handling
----------------
1. Lots of new packages have been added.
2. Package handling is much more sophisticated. Latex-suite is now able to
   handle the inclusion of custom user packages via the g:Tex_TEXINPUTS
   setting, which behaves analogous to the $TEXINPUTS variable which latex
   uses.

Compiler
--------
1. The compiler has been improved to also show the context of the error in
   a preview window beneath the quickfix window. It is also able to take
   you to the correct column number.
2. Latex-suite also supports the kdvi viewer in the same manner as xdvi and
   yap.
3. Latex-suite is able to compile parts of a file. Simply press \ll while
   visually selecting a block of text.
4. Latex-suite has support for compiling a file multiple times in order to
   get all references, etc right.
5. Automatically able to handle dependencies between various formats. For
   example, easy to generate ps files via dvi files etc.

Completion
----------
1. A powerful new tool called "completion". If you wish to insert a
   reference to a \label defined previously, just press <F9> inside the
   \ref{} command and latex-suite will bring up a list of label's to choose
   from. You can also filter according to prefix.
2. Can also complete citations using the same key. It is possible to use
   the g:Tex_BIBINPUTS variable analogous to the $BIBINPUTS variable to
   search for possible \cite'ations.
3. Can also complete commands requiring filename arguments (using the same
   <F9> key). Used in places like \include,\input,\bibliography etc.
   Latex-suite will intelligently filter the list to make selection easier.
   For example, \bibliography will list only files ending in .bib.
4. Can also complete arguments to certain commands such as
   \bibliographystyle etc.

Bibtex support
--------------
Easily insert bibliographic keys via the BBB, BBL, BBH and BBX macros while
editing .bib files.

User-Manual
-----------
A much more comprehensive user manual has been prepared both for viewing
while inside vim and also online. There are no "hidden" features in
latex-suite any more. (well, not more than a couple anyway!) The user
manual is written in xml and automatically converted to vim-help, flat html
and chunked html, allowing the manual to be viewed online as well.

Bug-fixes
---------
There have been many, many bug-fixes since the last revision, thanks to
valuable feedback from the users. There are way too many to be listed here.
About 450 bug-fixes since the last release. Latex-suite is now pretty
stable only averaging about 1 minor bug report once every fortnight.

Re: [Vim-latex-devel] =?iso-8859-1?Q?List_?= =?iso-8859-1?Q?of_mappings_and_=E2?=

[Jean-Rene D. <jr...@ar...>]

* Srinath Avadhanula <sr...@fa...>:
> On Tue, 2 Sep 2003, Jean-Rene David wrote:
> 
> > I'm writing a text in French and a mapping is
> > interfering with the character â (a with a
> > circonflex accent).
> 
> I have a feeling that this has to do with the Alt key mappings. If so
> please refer to the (newly added) FAQ:
> 
> http://vim-latex.sourceforge.net/index.php?subject=faq#faq-5

Right on. Many thanks.