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

[Vim-latex-devel] Re: search for bibtex entry by regexp

[Fabian B. <f.b...@gm...>]

Hi Srinath,

* On 02 Mar 2006 * Srinath Avadhanula wrote:

> Hi,
> 
> On 3/2/06, Fabian Braennstroem <f.b...@gm...> wrote:
> > Hi Srinath,
> >
> > > something like this while accounting for the fact that there could be
> > > multiple bibtex files will be a little hard.
> >
> > little bit late, but as you see, I can wait ... but not too
> > long ;-)
> >
> 
> :) So I can give you what you want on one condition. There is almost no
> documentation for this feature written yet. This means that I am not
> ready to make a release yet. But I commited to CVS already, so if you
> wish, update to the latest CVS. (See the download section of
> vim-latex.sf.net for instructions). Then when you press <F9> after
> \cite, you will see a completely different screen. Something like:
> 
> -----------------------------------%<-----------------------------------
> Masters [avadhanula:ms:01]
> TI "The Design and fabrication of a dynamically tuned {MFI} thorax"
> AU S. Avadhanula
> IN In University of California, Berkeley, 2001
> 
> Conference [avadhanula:icra:02]
> TI "Dynamically tuned design of the {MFI} thorax"
> AU S. Avadhanula and R. J. Wood and D. Campolo and R. S. Fearing
> IN In Proc. IEEE Int. Conf. on Robotics and Automation, 2002
> 
> Conference [avadhanula:iros:03]
> TI "Lift Force improvements for the Micromechanical Flying Insect"
> AU S. Avadhanula and R. J. Wood and E. Steltz and J. Yan and R. S. Fearing
> IN In IEE Conf. on Intelligent Robots and Systems, 2003
> -----------------------------------%<-----------------------------------
> 
> Note that syntax highlighting will hide some of these. Once in this
> screen, you can use <n>, <p> to move back and forth. Press <enter> once
> you are on the required entry. To filter, press <f>. This allows you to
> specify a "filter". A filter is basically a string like "a ellington".
> This filters out all results where the author field matches the string
> ellington. (You can ofcourse use partial words). Press <a> to show all
> results. You can also sort by pressing <s>.

Nice!

> 
> Note that this whole functionality although algorithmically stable is
> still a little raw around the edges. Unfortunately, I cannot take a look
> at this for at least 20 days or so because I am _really_ busy with
> something else.

I can wait.

> 
> Oh! You will need Vim with python support builtin to use this. Doing
> this in Vim-script would have doubled my work.

Until now, I did not know, that you can use python for
scripting. Can you recommend any pages on the web with some
vim/python introductions?

> 
> Let me know how it goes.

As soon as I am able to get access, I will let you know. It
seems that the server is down!?

Greetings!
Fabian

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

[Srinath A. <sri...@gm...>]

Hi,

On 3/2/06, Fabian Braennstroem <f.b...@gm...> wrote:
> Hi Srinath,
>
> > something like this while accounting for the fact that there could be
> > multiple bibtex files will be a little hard.
>
> little bit late, but as you see, I can wait ... but not too
> long ;-)
>

:) So I can give you what you want on one condition. There is almost no
documentation for this feature written yet. This means that I am not
ready to make a release yet. But I commited to CVS already, so if you
wish, update to the latest CVS. (See the download section of
vim-latex.sf.net for instructions). Then when you press <F9> after
\cite, you will see a completely different screen. Something like:

-----------------------------------%<-----------------------------------
Masters [avadhanula:ms:01]
TI "The Design and fabrication of a dynamically tuned {MFI} thorax"
AU S. Avadhanula
IN In University of California, Berkeley, 2001

Conference [avadhanula:icra:02]
TI "Dynamically tuned design of the {MFI} thorax"
AU S. Avadhanula and R. J. Wood and D. Campolo and R. S. Fearing
IN In Proc. IEEE Int. Conf. on Robotics and Automation, 2002

Conference [avadhanula:iros:03]
TI "Lift Force improvements for the Micromechanical Flying Insect"
AU S. Avadhanula and R. J. Wood and E. Steltz and J. Yan and R. S. Fearing
IN In IEE Conf. on Intelligent Robots and Systems, 2003
-----------------------------------%<-----------------------------------

Note that syntax highlighting will hide some of these. Once in this
screen, you can use <n>, <p> to move back and forth. Press <enter> once
you are on the required entry. To filter, press <f>. This allows you to
specify a "filter". A filter is basically a string like "a ellington".
This filters out all results where the author field matches the string
ellington. (You can ofcourse use partial words). Press <a> to show all
results. You can also sort by pressing <s>.

Note that this whole functionality although algorithmically stable is
still a little raw around the edges. Unfortunately, I cannot take a look
at this for at least 20 days or so because I am _really_ busy with
something else.

Oh! You will need Vim with python support builtin to use this. Doing
this in Vim-script would have doubled my work.

Let me know how it goes.

HTH
Srinath

[Vim-latex-devel] Re: search for bibtex entry by regexp

[Fabian B. <f.b...@gm...>]

Hi Srinath,

* On 03 Feb 2006 * Srinath Avadhanula wrote:

> Hi,
> 
> On 1/25/06, Fabian Braennstroem <f.b...@gm...> wrote:
> >
> > I am a happy user of vim-latex, but I am missing a feature
> > like searching for bibtex-entry by an regular expression.
> > As far as I understand the manual, <F9> is looking just for
> > corresponding keys and e.g. not for any word in the title.
> >
> > I would like to know, if anybody has a work-around for
> > searching the keys by regexp in vim or maybe an external
> > script?
> >
> 
> I can see that this will definitely be very useful. It will take quite
> a bit of extra code to get right though, so it might be a little while
> before its implemented. I am working on it (slowly) in my spare time,
> but I do not know how long this might take. The thing is that
> vim-latex does not parse any of the bibtex files, but instead just
> :grep's the pattern '@\w+' in all the bibtex files found. To do
> something like this while accounting for the fact that there could be
> multiple bibtex files will be a little hard.

little bit late, but as you see, I can wait ... but not too
long ;-)

Greetings!
Fabian
-- 

[Vim-latex-devel] Fwd: RFC: filetypes for TeX, LaTeX, ConTeXT (others?)

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

The following is a post from  Benji Fisher to vim mailing list. 
Users in this list will be interetested in the discussion.

How about making latex-suite the 'default' ftplugin for latex. So that 
it ships with vim.

link:http://article.gmane.org/gmane.editors.vim/40018
--------- begin forwared message ---------------

  Vim Users and Developers:

       Up to vim 6.x, all TeX variants were given filetype tex .  The 
syntax file was aimed at LaTeX, and the ftplugin made some attempt to 
accommodate both plain TeX and LaTeX.  Under development, vim 7.0 
includes syntax and ftplugin files for ConTeXt, with file type 
context. I think it is time to have separate file types for plain TeX 
and LaTeX, and would like input from all interested users.

  1. Are there other TeX variants (a.k.a. formats or flavors) that 
should also be supported?

  2. What file types should we use for plain TeX and LaTeX:
  	(a) tex for plain TeX and latex for LaTeX
  	(b) plaintex for plain TeX and tex for LaTeX
  	(c) other suggestions?

       The argument for 2(a) is that it is more logical.  The argument 
for 2(b) is that it is more backwards compatible.  That is, I think 
there are a lot more users who use LaTeX and would have to make adjustments 
if we changed their file types to latex than there are users of plain 
TeX who would be bothered if they had to change to plaintex.  Correct me 
if  I am wrong:  I think there are not many scripts out there that

  					--Benji Fisher

  P.S.  I maintain $VIMRUNTIME/ftplugin/tex.vim .



-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

[Vim-latex-devel] Why do I have to run TTarget for every file?

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

Hello,

I finally decided to ask this, since it's been nagging me for a while.

I use the current (Jan. 24th) version of the latex suite on Vim 7 =20
(but I was seeing the same behavior on 6.3) on a Mac. When I open a =20
TeX file, if I do "\ll", it tells me that it's compiling, but it does =20=

not seem to be using pdflatex but plain latex (the dvi is updated, =20
not the pdf). If I do ":TTarget", then it suggests "pdf" correctly, =20
and I can now compile.

I tried telling it that I wanted to compile to pdf by default (even =20
though I thought it would on the Mac), so I added:

let g:Tex_DefaultTargetFormat =3D 'pdf'

to my .vim/ftplugin/tex.vim file

I checked that it was taken into account (when I look up the content =20
of the variable, it tells me it's pdf), but it still requires me to =20
do a TTarget once for each buffer.

Here is the full contents of my .vim/ftplugin/tex.vim file, in case =20
it matters:

" TIP: if you write your \label's as \label{fig:something}, then if you
" type in \ref{fig: and press <C-n> you will automatically cycle through
" all the figure labels. Very useful!
set iskeyword+=3D:

setlocal tw=3D78
setlocal fo+=3Daw

let g:Tex_ViewRule_dvi =3D 'advi'
let g:Tex_ViewRule_pdf =3D 'TeXShop'

let g:Tex_DefaultTargetFormat =3D 'pdf'

" To be able to input =E9
imap <buffer> <leader>it <Plug>Tex_InsertItemOnThisLine


If someone knows what is going on or can help me debug this, I'd be =20
grateful.

Thanks,

Alan

--=20
Alan Schmitt <http://alan.petitepomme.net/>

The hacker: someone who figured things out and made something cool =20
happen.
.O.
..O
OOO

Re: [Vim-latex-devel] versioning scheme

[Srinath A. <sri...@gm...>]

The versioning scheme of vim-latex leaves a little to be desired. Of
late, there are two distinct ways to define the "version" of
vim-latex. One is the output of the :TVersion command which will show
you a number like 1.8.02 or something similar. The other is the date
on the actual file you download. The reason the release is made with
the time-stamp is that it was simply easier to make quick releases
this way. In particular, the download.inc PHP code just checks for the
latest file names of the pattern latexSuite200*.tar.gz and proceeds to
dynamically generate a link to them. All I need to do to make a
release is to make a CVS commit and do

  :make release

I have been pretty careful nowadays to keep updating the internal
version number (maintained in ftplugin/latex-suite/version.vim) after
every release. So you should be able to use either of the two as the
official "version". Personally, the timestamp is a teensy bit more
robust because it  does not rely on me remembering to update
version.vim.

Thanks,
Srinath

On 2/10/06, jorges <jor...@ya...> wrote:
> Hi,
> I've been using vim-latex for more than a year now, although there's
> plenty of things I haven't used yet. Now, going to the purpose of this po=
st:
>
> - Have you changed the version naming scheme? It seems that all recent
> releases follow a different convention, i.e. latexSuite20060124, than
> the, now old, previous ones, i.e. 1.5. This might seem like a dumb
> question, but I ask because the linux distribution I use (Gentoo Linux)
> still has version 1.5 as the latest *released* version. Is there a
> conceptual distinction between the two naming schemes, i.e new features
> vs. bug fixes release types? I want to have this clear before I try to
> convince the maintainers to keep updating to the latests versions and
> probably switching to the new naming scheme.
>
> Regards,
>
> jorge
>
>
>
> ______________________________________________
> LLama Gratis a cualquier PC del Mundo.
> Llamadas a fijos y m=F3viles desde 1 c=E9ntimo por minuto.
> http://es.voice.yahoo.com
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] versioning scheme

[jorges <jor...@ya...>]

Hi,
I've been using vim-latex for more than a year now, although there's
plenty of things I haven't used yet. Now, going to the purpose of this post:

- Have you changed the version naming scheme? It seems that all recent
releases follow a different convention, i.e. latexSuite20060124, than
the, now old, previous ones, i.e. 1.5. This might seem like a dumb
question, but I ask because the linux distribution I use (Gentoo Linux)
still has version 1.5 as the latest *released* version. Is there a
conceptual distinction between the two naming schemes, i.e new features
vs. bug fixes release types? I want to have this clear before I try to
convince the maintainers to keep updating to the latests versions and
probably switching to the new naming scheme.

Regards,

jorge


		
______________________________________________ 
LLama Gratis a cualquier PC del Mundo. 
Llamadas a fijos y móviles desde 1 céntimo por minuto. 
http://es.voice.yahoo.com

Re: [Vim-latex-devel] Can't find file, acroread is not used

[Boris D. <bor...@cm...>]

Hi Ren=C3=A9

On Thursday 09 February 2006 17:52, Ren=C3=A9 Lange wrote:
> /usr/share/vim/vim63/ftplugin/tex.vim:
> let g:Tex_ViewRule_pdf =3D 'acroread'
>
> I think this should be enough to tell Latexsuite to use it, shouldn't it?

Yes, I have this in my .vimrc and it just works.

Cheers,
Boris Dusek

Re: [Vim-latex-devel] Can't find file, acroread is not used

[Srinath A. <sri...@gm...>]

Hi Rene,

On 2/9/06, Ren=E9 Lange <bit...@ti...> wrote:

> problem doesn't occur. It seems, the spaces really are the reason here.
> This is a problem I have always had when touching Latexsuite, and always
> was the reason not to keep on and get familiar with it. Now, I'm fed up, =
I
> absolutely want to use it! =3D)
>
I have been beating my head against the freaking spaces in filenames thing
for ever now, but apparently, things still do not work well. I suggest that
instead of waiting for a comprehensive fix in latex-suite, you set

let g:Tex_CompileRule_dvi =3D "latex --src-specials
--interaction=3Dnonstopmode '$*'"
let g:Tex_CompileRule_pdf =3D "pdflatex --interaction=3Dnonstopmode '$*'"

in your ~/.vim/ftplugin/tex.vim.

I think this will most probably fix your problem.

> Second: I would like to view my pdf output with acroread, which I have
> installed. Typing acroread in shell starts acroread. I set the following
> in /usr/share/vim/vim63/ftplugin/tex.vim:
> let g:Tex_ViewRule_pdf =3D 'acroread'

It might be due to spaces in the filename again. This time use

let g:Tex_ViewRule_pdf =3D "acroread '$*.pdf'"

Let us know if these fixes work.

Thanks,
Srinath

[Vim-latex-devel] Can't find file, acroread is not used

[<bit...@ti...>]

Hi,

I have 2 problems, at least. The first one: When I try to compile a file =
=20
with a name that contains spaces, I get a "Can't find file" error. I =20
checked Tex_CompileRule, as described in the FAQ. With simple names, this=
 =20
problem doesn't occur. It seems, the spaces really are the reason here. =20
This is a problem I have always had when touching Latexsuite, and always =
=20
was the reason not to keep on and get familiar with it. Now, I'm fed up, =
I =20
absolutely want to use it! =3D)

Second: I would like to view my pdf output with acroread, which I have =20
installed. Typing acroread in shell starts acroread. I set the following =
=20
in /usr/share/vim/vim63/ftplugin/tex.vim:
let g:Tex_ViewRule_pdf =3D 'acroread'

I think this should be enough to tell Latexsuite to use it, shouldn't it?

Thanx alot for your comments,
Ren=C3=A9 Lange

Re: [Vim-latex-devel] wish list

[Srinath A. <sri...@gm...>]

Hi,

On 2/2/06, Javier Rojas <jer...@gm...> wrote:
>
> The thing is an autoclean feature; when you close the tex file, vim shoul=
d
> delete the whole bunch of auxiliar files (.toc, .log, .out, etc) created
> during work. I've tried with autocommands with no success to achieve this=
.
>

This will not be too hard to do. I'd be willing to put it into
Vim-Latex if someone could write something up. It would involve
catching the VimLeave autocommand and using the Tex_GetMainFileName()
function. I am thinking that it will be annoying if it happens on the
BufLeave autocommand because that happens every time you open a new
file...

Srinath

Re: [Vim-latex-devel] search for bibtex entry by regexp

[Srinath A. <sri...@gm...>]

Hi,

On 1/25/06, Fabian Braennstroem <f.b...@gm...> wrote:
>
> I am a happy user of vim-latex, but I am missing a feature
> like searching for bibtex-entry by an regular expression.
> As far as I understand the manual, <F9> is looking just for
> corresponding keys and e.g. not for any word in the title.
>
> I would like to know, if anybody has a work-around for
> searching the keys by regexp in vim or maybe an external
> script?
>

I can see that this will definitely be very useful. It will take quite
a bit of extra code to get right though, so it might be a little while
before its implemented. I am working on it (slowly) in my spare time,
but I do not know how long this might take. The thing is that
vim-latex does not parse any of the bibtex files, but instead just
:grep's the pattern '@\w+' in all the bibtex files found. To do
something like this while accounting for the fact that there could be
multiple bibtex files will be a little hard.

Srinath

Re: [Vim-latex-devel] Nested manual folding

[Cristian R. <cr...@li...>]

On Thu, Feb 02, 2006 at 06:50:17PM -0800, Srinath Avadhanula wrote:
> I am still not quire sure why what you did is
> making latex-suite hang... Thats a bug for another day.

Thank you very much for your quick and valuable answer.

Well, I found out that substituting '<<<' patterns with '^%<<<' (see attached
patch) makes the "hang" problem disappear, and I got the nested manual
folds to work as I wanted, although with the following caveats:

- A) To avoid that a comment fold "eats up" any subsequent manual folds
  separated by empty lines, like in the following situation...

    % Comment block
    % ...
    % End comment block
    
    %<<< Manual fold
    ...
    %>>>

  ...you must include the empty line (i.e. the '^$' pattern) in the comment
  folds endpattern (as I've done in my patch).  Note that this problem affects
  also your proposed patch.

- B) If you want things to work nicely in the preamble too, you have to switch
  off the 'preamble' value from g:Tex_FoldedMisc (e.g. setting it to
  'item,<<<,comments'), otherwise folds inside the preamble won't work anymore
  (you can only choose between a completely folded preamble or a completely
  unfolded one).

  Although this is not a major limitation (since you can always enclose the
  whole preamble in a big manual fold and retain nested manual folds), I tried
  to fix it by adding startskip and endskip pattern for the "preamble" folds,
  but without success (it seems that whatever skip pattern I add, the preamble
  doesn't get folded anymore, but I admit that I didn't play too much with
  that).
  

> Can you try opening the following file and then opening it after
> applying the patch (also attached) to folding.vim? Is something like
> this what you want?

I tried your patch and it works nicely, it does not suffer from the "preamble"
bug as mine, although it suffers from the "empty line" bug I mentioned above.

I tried fiddling with it a bit in order to see if we can avoid to use two
different kinds of manual folding markers ("{{{" and "<<<"), but I couldn't
achieve any better results than those of my patch.

So, for now I'm quite satisfied with my patch, but I admit it could be
interesting to work on the B) problem, in order to restore "normal" preamble
folding working...

Thanks again for your reply!

Cri

-- 
  GPG/PGP Key-Id 0x943A5F0E      -     http://www.linux.it/~cri/cri.asc

[Vim-latex-devel] Blank screen after compile

[Hans C. <st...@st...>]

I'm new to this list, but I haven't been able to find a solution on the
net.

After compiling (\ll) a .tex document in a gnome console, the
text blanks out and I usually have to use CTRL-L to redraw the screen to
get it back.

But, the first time I run the compiler everything works fine and the
compiler displays: "Ran latex 2 time(s)". The next time I compile,
however, the compiler displays "Ran latex 1 time(s)" and nothing else.
After compiling (\ll) a .tex document in a gnome console, the
text blanks out and I have to use CTRL-L to redraw the screen to get it
back.

I have only been able to reproduce this when my document includes 

\bibliography{arkiv}
\bibliographystyle{plain}

regards hc

Re: [Vim-latex-devel] Very slow opening of LaTeX file after installing latex-suite

[Srinath A. <sri...@gm...>]

Hi,

On 2/2/06, Jeremy Conlin <jer...@gm...> wrote:
> I just installed LaTeX suite and added the following to my .vimrc file
>
> filetype plugin indent on
>
> Now when I open a LaTeX/TeX file, it takes a very long time to open, a
> few seconds.  Even worse is that I have to press enter before I can
> see everything.  Is this normal or do I have a setting messed up?

On my machine, WinXP on Pentium4, 1.6GHz, 1GB RAM, it takes about 0.4
seconds to start  latex-suite. I measured this by starting gvim on an
empty file (so that vim-latex is not activated) and then doing:

:python import time
:exec 'python tic =3D time.time()' | set ft=3Dtex | exec 'python toc =3D ti=
me.time()'
:python print toc-tic

You will ofcourse need vim with python to do this.

You can try to set

let g:Tex_MathMenus =3D 0

in your ~/.vim/ftplugin/tex.vim to reduce the time somewhat, but it
might not really help much. I am not sure why this is slower for you,
but 2 seconds seems to be in the same ballpark as 0.5 seconds, so I am
not sure if things can be much faster.

Srinath

Re: [Vim-latex-devel] Nested manual folding

[Srinath A. <sri...@gm...>]

Hi,

upon reading the latter part of your email, I think there might be
better ways to accomplish what you wish... Unfortunately, what you
need is not really supported by latex-suite OOTB, but the modification
is not that hard... I am still not quire sure why what you did is
making latex-suite hang... Thats a bug for another day.

On 2/2/06, Cristian Rigamonti <cr...@li...> wrote:
[snip]
>
> For the curious, the reason why I'm looking for nested manual folds lies =
in the
> fact that I'd like to define "arbitrary" manual foldings in the preamble
> (possibly containing blocks of comments) but "comment" folds seem to inte=
ract
> badly with "manual" folds; again, I tried various settings of g:Tex_Folde=
dMisc
> (e.g. exchanging the order of "<<<" and "comments") but I didn't find the
> right one; so that's why I turned to nested manual folding: if I could ma=
ke
> them work, I would use only manual folding, dropping "comment" and "pream=
ble"
> (which don't seem to work the way I expect together with manual folds).
>
> (I can elaborate on that and provide some examples if you are interested)
>
> Well, thanks for reading (and of course, thanks for this great project)!
>

Can you try opening the following file and then opening it after
applying the patch (also attached) to folding.vim? Is something like
this what you want?

Srinath

\documentclass[a4paper]{report}
%{{{ Packages
%{{{ Math Packages
\usepackage[sumlimits]{amsmath}
\usepackage[sumlimits]{float}
%}}}
%{{{ Some other Packages
\usepackage[sumlimits]{amsmath}
\usepackage[sumlimits]{float}
%}}}
%}}}
%{{{ Commands
%{{{ Math commands
\renewcommand{trivial}{trivial}
\renewcommand{trivial}{trivial}
%}}}
%{{{ Some other commands
\renewcommand{trivial}{trivial}
\renewcommand{trivial}{trivial}
%}}}
%}}}
\begin{document}
%<<< A region of text
\section{A section}
This is a block
This is a block
\section{Another section}
This is a block
This is a block
%>>>
%<<< Another region of stuff
\section{A third section}
This is a block
This is a block
%>>>
\end{document}

Index: folding.vim
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/folding.vim,v
retrieving revision 1.26
diff -u -r1.26 folding.vim
--- folding.vim=093 Jan 2006 08:40:39 -0000=091.26
+++ folding.vim=093 Feb 2006 02:48:29 -0000
@@ -219,11 +219,24 @@
 =09"
 =09" }}}
 =09" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
+
+=09" Manually folded regions {{{
+=09if g:Tex_FoldedMisc =3D~ '\(^\|,\)<<<\(,\|$\)'
+=09=09call AddSyntaxFoldItem (
+=09=09=09\ '%{{'.'{',
+=09=09=09\ '%}}'.'}',
+=09=09=09\ 0,
+=09=09=09\ 0,
+=09=09=09\ '%{{'.'{',
+=09=09=09\ '%}}'.'}'
+=09=09=09\ )
+=09endif
+=09" }}}
 =09
 =09" {{{ comment lines
 =09if g:Tex_FoldedMisc =3D~ '\<comments\>'
 =09=09call AddSyntaxFoldItem (
-=09=09=09\ '^%\([^%]\|[^f]\|[^a]\|[^k]\|[^e]\)',
+=09=09=09\ '^% ',
 =09=09=09\ '^[^%]',
 =09=09=09\ 0,
 =09=09=09\ -1
@@ -326,8 +339,8 @@
 =09" Manually folded regions {{{
 =09if g:Tex_FoldedMisc =3D~ '\(^\|,\)<<<\(,\|$\)'
 =09=09call AddSyntaxFoldItem (
-=09=09=09\ '<<<',
-=09=09=09\ '>>>',
+=09=09=09\ '^%<<<',
+=09=09=09\ '^%>>>',
 =09=09=09\ 0,
 =09=09=09\ 0
 =09=09=09\ )

[Vim-latex-devel] Very slow opening of LaTeX file after installing latex-suite

[Jeremy C. <jer...@gm...>]

I just installed LaTeX suite and added the following to my .vimrc file

filetype plugin indent on

Now when I open a LaTeX/TeX file, it takes a very long time to open, a
few seconds.  Even worse is that I have to press enter before I can
see everything.  Is this normal or do I have a setting messed up?
Thanks,
Jeremy

[Vim-latex-devel] wish list

[Javier R. <jer...@gm...>]

Hi,

There is something that i'd like to see implemented in a future in vim 
latex, and I wanted to see if it gets enough interest from the user's 
community to go on and ask /more/ things to the dev team, or to see if 
somebody has a workaround for this

The thing is an autoclean feature; when you close the tex file, vim should 
delete the whole bunch of auxiliar files (.toc, .log, .out, etc) created 
during work. I've tried with autocommands with no success to achieve this.


-- 
Javier

Candy Is dandy But liquor Is quicker. -- Ogden Nash, "Reflections on 
Ice-Breaking" Fortune updates the great quotes: #53. Candy is dandy; but 
liquor is quicker, and sex won't rot your teeth.

[Vim-latex-devel] Nested manual folding

[Cristian R. <cr...@li...>]

Hi, I'm trying to allow nesting for manual folds in latex-suite; to do so I
tried modifying the function MakeTexFolds in folding.vim, adding the "start=
skip"
and "endskip" arguments to the call of AddSyntaxFoldItem, like that (line 3=
26):

  " Original code
  "call AddSyntaxFoldItem (=20
  "   \ '<<<',
  "   \ '>>>',
  "   \ 0,
  "   \ 0
  "   \ )
 =20
  " My re-writing:
  call AddSyntaxFoldItem (
      \ '<<<',
      \ '>>>',
      \ 0,
      \ -1,
      \ '<<<',
      \ '>>>'
      \ )

But unfortunately it doesn't seem to work; as I open a latex file in vim, it
freezes eating up all my CPU; if I break it with Ctrl-C I got a couple of e=
rrors
and a badly highlighted file.

  Error detected while processing /home/cri/.vim/ftplugin/tex_latexSuite.vi=
m:
  line   13:
  Interrupted
  Error detected while processing /usr/share/vim/vim64/ftplugin/tex.vim:
  line    1:
  Interrupted

(I'm using latest tgz package on Debian GNU/Linux unstable and vim 6.4)

This happens whatever value I set to g:Tex_FoldedMisc (except, of course, i=
f I
don't include '<<<').

Are my changes wrong or am I missing something?

For the curious, the reason why I'm looking for nested manual folds lies in=
 the
fact that I'd like to define "arbitrary" manual foldings in the preamble
(possibly containing blocks of comments) but "comment" folds seem to intera=
ct
badly with "manual" folds; again, I tried various settings of g:Tex_FoldedM=
isc
(e.g. exchanging the order of "<<<" and "comments") but I didn't find the
right one; so that's why I turned to nested manual folding: if I could make
them work, I would use only manual folding, dropping "comment" and "preambl=
e"
(which don't seem to work the way I expect together with manual folds).

(I can elaborate on that and provide some examples if you are interested)

Well, thanks for reading (and of course, thanks for this great project)!

Cri

--=20
  GPG/PGP Key-Id 0x943A5F0E      -     http://www.linux.it/~cri/cri.asc

Re: [Vim-latex-devel] Inverse and Forward Search : This is not what I expected

[Srinath A. <sri...@gm...>]

Hi

On 2/1/06, ahmet nurlu <ahm...@ya...> wrote:
> Hi,
>
[snip]

> When I make a forward search in WinEdt, YAP was
> displaying the position roughly corresponding to your
> current position in YAP. It  points the corresponding
> line and puts a circle on the line(one line below or
> above of it at the worst). Inverse searching in  YAP
> works almost the same: When you initiate  the inverse
> search from the YAP previewer, the editor displays the
> corresponding source line in a small margin of error.
>
> In my Debian/Sarge system, I use TeTeX(ver:3.0.13) and
> Xdvi(ver:22.84.9). When I initiate a forward search
> from gvim, Xdvi draws a rectangle around the paragraph
> in which the corresponding line in the source file
> belongs to. So it is a big margin of error. Inverse
> search works with the same big margin of error. It
> doesn't matter where you click in a paragraph in Xdvi,
> it always points the begining of a paragraph in the
> corresponding source file.
>

This a difference between MikTeX and teTeX as you suspect. There is
unfortunately nothing which I know of which makes the search in teTeX
perform as well/better than MiKTeX. I haven't looked too closely at it
though. If you find a solution to this, I'd be glad to know.

Thanks
Srinath

Re: [Vim-latex-devel] Documentation update: alt-key macros

[Srinath A. <sri...@gm...>]

Hi,

On 2/1/06, Cristian Rigamonti <cr...@li...> wrote:
> On Wed, Feb 01, 2006 at 08:20:05PM +0100, Cristian Rigamonti wrote:
> >
> > - patch: patch to latex-suite.xml
> > - patch_quickstart: patch to latex-suite-quickstart.xml
> > - patch_latexhelp: patch to latexhelp.txt
>
> I forgot a patch for imaps.txt, here you are.
>

Thanks a lot for your help! I'll include these patches in the next
release. I'll also fix the online FAQ to point to the correct place.

Thanks,
Srinath

[Vim-latex-devel] Re: Invalid arguments for function substitute, etc

[Srinath A. <sri...@gm...>]

Excellent!

On 2/1/06, Gregor Berginc <gre...@gm...> wrote:
> Problem solved.
>
> Since I did not have .vimrc in my home, Vi compatible mode was used
> during plugin sourcing (.gvimrc is consulted much later than plugins).
>
> A simple 'touch ~/.vimrc' did the job.
>

I had forgotten the mandatory

set cpo&vim

at the beginning of plugin/imaps.vim. This reminds me to check all the
files in the distribution fo this.

Srinath

Re: [Vim-latex-devel] Documentation update: alt-key macros

[Cristian R. <cr...@li...>]

On Wed, Feb 01, 2006 at 12:30:30PM +0100, Cristian Rigamonti wrote:
 
> (I'd be happy to contribute in bug-fixing the documentantion
> if you need any help)

Speaking of which, I just did a spell-check (aspell rules!) on the three files
of the documentation (current CVS revision) and I'm attaching the following
patches which correct some typos.

- patch: patch to latex-suite.xml
- patch_quickstart: patch to latex-suite-quickstart.xml
- patch_latexhelp: patch to latexhelp.txt

Cri

-- 
  GPG/PGP Key-Id 0x943A5F0E      -     http://www.linux.it/~cri/cri.asc

Re: [Vim-latex-devel] Documentation update: alt-key macros

[Cristian R. <cr...@li...>]

On Wed, Feb 01, 2006 at 08:20:05PM +0100, Cristian Rigamonti wrote:
> 
> - patch: patch to latex-suite.xml
> - patch_quickstart: patch to latex-suite-quickstart.xml
> - patch_latexhelp: patch to latexhelp.txt

I forgot a patch for imaps.txt, here you are.

Cri

-- 
  GPG/PGP Key-Id 0x943A5F0E      -     http://www.linux.it/~cri/cri.asc

[Vim-latex-devel] Re: Invalid arguments for function substitute, etc

[Gregor B. <gre...@gm...>]

Problem solved.

Since I did not have .vimrc in my home, Vi compatible mode was used
during plugin sourcing (.gvimrc is consulted much later than plugins).

A simple 'touch ~/.vimrc' did the job.

Once again, thanks for yor help.

Best,
Gregor

On 2/1/06, Gregor Berginc <gre...@gm...> wrote:
> > many other files contain such commands. Do you have any idea why
> > multi-line commands causes problems to my vim?
>
> The worst thing is that if I copy the IMAP function in my .gvimrc it
> WORKS?! No problem with back-slashes... But, as soon as I put the IMAP
> function in my ~/.vim/plugin/ directory I get the same errors. Any
> clues?
>
> Gregor
>


--
Gregor Berginc, Ph.D. Student
University of Ljubljana, Faculty of CIS
Trzaska 25, SI-1001 Ljubljana, Slovenia
tel: +386 1 4776630, fax: +386 1 4264647
www: http://vicos.fri.uni-lj.si/gregor