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

Re: [Vim-latex-devel] A bunch of Debian bugs

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

> support for latex-beamer
>
> I really do not know about this package.=20
Is a package to create presentations with LaTeX that is very, very powerful=
=20
for creating layouts, using themes and the like. It creates a pdf=20
presentation that is fully navigable.

Is really, really cool

=2D-=20
Javier Rojas

GPG key:
http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xA1C57061

Re: [Vim-latex-devel] A bunch of Debian bugs

[Franz P. <fp...@fr...>]

Hi,

thanks for the quick response.

On Fri, Apr 28, 2006 at 04:46:48PM -0700, Srinath Avadhanula wrote:
> > - 03_insertitem.patch, http://bugs.debian.org/350021
> >   When going into insert mode with a there are issues with the
> >   placement of \item. Please see the bug for details.
>=20
> I incorporated your patch in the latest SVN.

Thanks.

> > - 04_fname_outline.patch, http://bugs.debian.org/365152
> >   outline.py adds the .tex extension twice when it's already given in
> >   and input/include statement.
>=20
> I fixed this also, but in a slightly different manner. I think one more
> function would be confusing so I just made getFileContents in outline.py
> handle the file-reading, like your includeFile function.

Great, I'll keep my patch in Debian until you release a new version.

> > - http://bugs.debian.org/233682
>=20
> !commando ends in insert mode
>=20
> This looks more like a vim issue that a latex-suite issue, even
> though without latex-suite it doesn't seem to manifest itself. If this
> annoys an end-user, I would suggest using some other mapping for jumping
> to the next place-holder.

All right, I'll contact the vim maintainers and see what they think
about it.

> > - http://bugs.debian.org/310649
>=20
> makeprg not set to 'make target' when Makefile in pwd is present
>=20
> This was asked in the mailing list a while back. This is not really
> a bug in the program but in the documentation. Although 'makeprg' is set
> to something other than 'make <target>', when the user presses \ll to
> compile, latex-suite temporarily resets 'makeprg' to 'make <target>'. In
> other words, latex-suite uses the Makefile at the last step. Issuing the
> :make command from the command-line will not use the Makefile.
>=20
> I will update the documentation.

Thanks, I'll post your explanation and close the bug.

> > - http://bugs.debian.org/312816
>=20
> <F5> doesn't work properly when showcmd is set
>=20
> I'll fix this in the next release. It should be a matter of changing
> line 653 in plugin/imaps.vim to:
>=20
> let s:RemoveLastHistoryItem =3D ':silent! call histdel("/", -1)|let
> @/=3Dg:Tex_LastSearchPattern'
>=20
> Although I have not tested this. For me even with 'showcmd' I do not get
> the message, so I cannot reproduce this bug.

Ok, I'll do some testing and maybe cook up a patch to fix this in another
Debian revision.

> > - http://bugs.debian.org/282753
>=20
> support for latex-beamer
>=20
> I really do not know about this package. I remember some discussion
> about this on the list, but cannot remember what happened off the top of
> my head. I would gladly accept patches etc.

I am interested in latex-beamer support myself as I use it quite regulary.
Perhaps I dig some more into vim-latexsuite and add support for it. But I
can't guaranntee if time permits. ;-)

> > - http://bugs.debian.org/242974
> > - http://bugs.debian.org/280793
> > - http://bugs.debian.org/254619
> >
> I will comment on this at a later time.

Great. Thanks for your comments so far.

One more question: Is there a timeframe on when the next version of
vim-latexsuite will be released? And, if not in the near future, is SVN
trunk generally stable enough to ship it with Debian unstable? It would
undergo a testing phase of at least 5 days to 10 days there until being put
into testing (next stable, currently etch).

Cheers,
Franz

--=20
Franz Pletz                   \  The Internet treats censorship as
www: http://franz-pletz.org/   \  damage and routes around it.
email: fp...@fr...   \  -- John Gilmore

Re: [Vim-latex-devel] bug in \item command

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

Hi Javier,

On 4/19/06, Javier Rojas <jer...@gm...> wrote:
> Anyway, would it be possible that vimlatex, instead of deleting the text
> written, simply puts it "as is" if I'm not within any of the itemize,
> enumerate or description environments? For example, if my imap were \pota=
to,
> vimlatex should change it to \item when I'm inside of some of these
> environments, and leave \potato if I'm out.
>

This is actually quite a bit harder than it seems (partly because there
Tex_InsertItem() does not know what mapping was responsible for calling
it). The best way to get around this might be to define

    let g:Tex_ItemStyle_list =3D '\item '

and similar for any other environments you use \items for. One thing
which we _could_ do is to create yet another setting which makes
latex-suite insert a bare \item when no enclosing environment is
found...

Thanks,
Srinath

Re: [Vim-latex-devel] A bunch of Debian bugs

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

Hi,

On 4/28/06, Franz Pletz <fp...@fr...> wrote:
> Hello,
>
> I'm the new maintainer of vim-latexuite in Debian GNU/Linux. There are

Thanks for taking up the maintenance.

>  - 03_insertitem.patch, http://bugs.debian.org/350021
>    When going into insert mode with a there are issues with the
>    placement of \item. Please see the bug for details.

I incorporated your patch in the latest SVN.

>  - 04_fname_outline.patch, http://bugs.debian.org/365152
>    outline.py adds the .tex extension twice when it's already given in
>    and input/include statement.

I fixed this also, but in a slightly different manner. I think one more
function would be confusing so I just made getFileContents in outline.py
handle the file-reading, like your includeFile function.

>  - http://bugs.debian.org/233682

!commando ends in insert mode

This looks more like a vim issue that a latex-suite issue, even
though without latex-suite it doesn't seem to manifest itself. If this
annoys an end-user, I would suggest using some other mapping for jumping
to the next place-holder.

>  - http://bugs.debian.org/310649

makeprg not set to 'make target' when Makefile in pwd is present

This was asked in the mailing list a while back. This is not really
a bug in the program but in the documentation. Although 'makeprg' is set
to something other than 'make <target>', when the user presses \ll to
compile, latex-suite temporarily resets 'makeprg' to 'make <target>'. In
other words, latex-suite uses the Makefile at the last step. Issuing the
:make command from the command-line will not use the Makefile.

I will update the documentation.

>  - http://bugs.debian.org/312816

<F5> doesn't work properly when showcmd is set

I'll fix this in the next release. It should be a matter of changing
line 653 in plugin/imaps.vim to:

let s:RemoveLastHistoryItem =3D ':silent! call histdel("/", -1)|let
@/=3Dg:Tex_LastSearchPattern'

Although I have not tested this. For me even with 'showcmd' I do not get
the message, so I cannot reproduce this bug.

>  - http://bugs.debian.org/282753

support for latex-beamer

I really do not know about this package. I remember some discussion
about this on the list, but cannot remember what happened off the top of
my head. I would gladly accept patches etc.

>  - http://bugs.debian.org/242974
>  - http://bugs.debian.org/280793
>  - http://bugs.debian.org/254619
>
I will comment on this at a later time.

Thanks,
Srinath

[Vim-latex-devel] A bunch of Debian bugs

[Franz P. <fp...@fr...>]

Hello,

I'm the new maintainer of vim-latexuite in Debian GNU/Linux. There are
some open bugs in our BTS at http://bugs.debian.org/vim-latexsuite
which need your attendence. Some have already been forwarded to your BTS
or mailing list a few months/years ago but don't seem to be fixed in the
current release.

I created patches against 20060325 for 2 issues myself which are attached
and work:

 - 03_insertitem.patch, http://bugs.debian.org/350021
   When going into insert mode with a there are issues with the
   placement of \item. Please see the bug for details.

 - 04_fname_outline.patch, http://bugs.debian.org/365152
   outline.py adds the .tex extension twice when it's already given in
   and input/include statement.

These are the bugs I wasn't able to address myself and need your
assistence:

 - http://bugs.debian.org/233682
 - http://bugs.debian.org/310649
 - http://bugs.debian.org/312816
 - http://bugs.debian.org/282753

And these are bugs which were already forwarded to you:

 - http://bugs.debian.org/242974
 - http://bugs.debian.org/280793
 - http://bugs.debian.org/254619

Please take your time as all of these bugs are more than one year old
and mostly minor though should get fixed in the near future.

Thanks,
Franz

-- 
Franz Pletz                   \  The Internet treats censorship as
www: http://franz-pletz.org/   \  damage and routes around it.
email: fp...@fr...   \  -- John Gilmore

Re: [Vim-latex-devel] Changes for vim7

[Andreas W. <A.W...@st...>]

Hello Srinath, hello list,
it took me some time and I still cannot be as elaborate as I would have 
liked to be, but anyway, here goes:

* Srinath Avadhanula wrote on Apr/06/2006:
> There are potentially a number of things I can think of:

> 2. Adapt vim-latex to vim7. Vim7 introduces the concept of the autoload 
>   directory which has the potential for making vim-latex more modular and 
>   also load faster at the same time.

I don't think speeding up the loading of vim-LaTeX should be of great 
priority. After all, the main delay happens when you load a tex/bib 
file, and not when you actually work with it.
As for other advantages of vim7, I can't tell. I have dl'd it, but not 
yet checked it out.

> 3. Introduce some cool new features, or make some presently 
> implemented feature more usable. I really cannot think of too many at 
> this point.

One feature which could be imroved upon, IMHO, would be handling of 
packages. I have recently mailed about defining which options are 
possible for commands that new packages bring with them (like you can 
define which options they accept with \usepackage[x]{y}). Another thing 
would be auto-navigating to the correct place and handling necessary 
square brackets ('[', ']') correctly when the user selects among the 
package-loading options, so that one can select package options no 
matter where one is in the document. OTOH, selecting package is probably 
not something that needs to be done frequently during normal work, so it 
might not be needed.

> Any other thoughts/ideas? I'm also open to general usability complaints. 
> One more thing which would be invaluable for me is if I can get an idea of 
> what portions of vim-latex are actually being actively used. I know that I 
> personally only use maybe 40% of vim-latex's code.

Here is a bit about what I am using mostly, then. It's probably not even 
40%...
I am using (vim-)LaTeX for my studies in the humanities, and I don't 
have very much use for maths, figures, tables, pstricks and the like -- 
wich might be not very representative. What I am using mostly is this:
FEM, FIT (and the corresponding `em and `it), EQN, EQE. I have made 
mappings to insert a footnote and footcite (see below) on EFN and EFC, 
and I am using these extensively, too. Also, I am trying to get used to 
using F5, F7 (how many entries can one have there?) and most importantly 
F9 (both bib and reference completion) more regularly.

- I often need \frqq{} as opening and \flqq{} as closing quotes, so I 
    have mapped these to `CC and `CT respectively and additionally I have
    defined Tex_Env_citation accordingly and added it to 
    Tex_HotKeyMappings, so I could quickly insert them with Shift-F1. Only 
    recently I have found out that by now it's working fine when I just 
    define them as Tex_SmartQuoteOpen and -Close in my ngerman package 
    file, therefore I now have this in my ngerman package file and do 
    hardly need the other ways anymore (although typing `CC and `CT is 
    happening pretty automatically now):
      let b:Tex_SmartQuoteOpen = "\\frqq\{\}"
      let b:Tex_SmartQuoteClose = "\\flqq\{\}"

- I often need jurabib's (http://www.jurabib.org) \footcite and have 
    mapped it to EFC. (I have also defined a Tex_Env_Footcite.)
    (Unfortunately the mapping doesn't even work when I put it in 
    vimfiles/after/ftplugin/tex.vim, so I have to manually re-enter it 
    after opening my tex file. Luckily vim has a command history ;) When I 
    get to it, I will try to put up some jurabib (and hopefully other) 
    package support files.

- A similar issue to the problem Vaidotas has mentioned with double 
    brackets '((': I often use manual folding but freak out everytime I 
    have to enter '% {{{' (would it maybe be possible to disable the 
    expansion in a comment?)

- I've tried to add additional (optional) bibentry fields: crossref (x), 
    gender (g) and shorttitle (l), but I think I lost the code which 
    really integrated them into the bibtex-ftplugin routines, so that they 
    would be included upon entering BBib, BBL etc. Is there a way to 
    outsource some more of the relevant bibtex settings instead of messing 
    around in LaTeX-suite/bibtex.vim after each download of a new 
    release?

- what I'd /like/ to do would be a way to handle a couple of search and 
    replace runs more easily which I always have to do when finishing some 
    text. Like for example this one:
      :%s/\(\a\)\.\(\a\)\.\_s/\1.\\,\2.\~/gc
    (replacing e.g. or ie. with e.\,g.\~ and i.\,e.\~) Right now I have a 
    list of all those replacements but no cool way of performing them. Any 
    hints would be appreciated.

- pdfsync (http://itexmac.sourceforge.net/pdfsync.html) support would be 
    cool, I think -- pdf being a portable format and currently the only 
    one to benefit from pdfetex's microtypographic extensions. Only I 
    haven't got it working myself in a way that I really can tell much 
    about it. It's supposed to offer functionality comparable to 
    UseEditorSettingInDVIViewer, but I don't even know how I would get 
    back from xpdf to vim...


I think that might be enough food for thought for now. I hope it is of 
some use for you.

Cheers,
Andreas

-- 
All wiyht. Rho sritched mg kegtops awound?

-- 
My Public PGP Keys:
1024 Bit DH/DSS: 0x869F81BA
768 Bit RSA:     0x1AD97BA5

[Vim-latex-devel] bug in \item command

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

Hi,

I have a problem with the item command:=20
Since I use accented characters, I've remapped the command for inserting th=
e=20
\item to

imap <buffer> \it <Plug>Tex_InsertItemOnThisLine

in my tex.vim

When I'm within a itemize, enumerate, or description environment and I type=
=20
\it, it works fine; however, when I'm within a list environment it doesn't=
=20
write anything. Even more, it deletes my (so hardly typed :)) \it. I have=20
noticed that the same happens when I'm outside of all the three previous=20
environments.

Anyway, would it be possible that vimlatex, instead of deleting the text=20
written, simply puts it "as is" if I'm not within any of the itemize,=20
enumerate or description environments? For example, if my imap were \potato=
,=20
vimlatex should change it to \item when I'm inside of some of these=20
environments, and leave \potato if I'm out.

Thanks for your attention
=2D-=20
Javier Rojas

GPG key:
http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xA1C57061

Re: [Vim-latex-devel] listings packet

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

* Bernhard Walle on Monday, April 17, 2006 at 23:53:55 +0200:
> it would be nice if the lstlisting enviroment could be highlighted the
> same as verbatim. 

See Srinath's answer. -- As a workaround, and if you don't have
verbatim environments in your document, you could experiment
with:

\documentclass{article}
\usepackage{listings}
\let\verbatim\relax
\lstnewenvironment{verbatim}{}{}
\begin{document}
\begin{verbatim}[language=c,style=inline]
code
\end{verbatim}
\end{document}

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

Re: [Vim-latex-devel] Symbol visualization in vim-latex

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

On Mon, 17 Apr 2006, Srinath Avadhanula wrote:

> Hi Fabio,
>
> On 4/14/06, Fabio Stumbo <f.s...@un...> wrote:
>>
>> 1)Using gvim to edit a tex file, is it possible to have in some way
>> a previsualization of the output of a math symbol?  The menus under
>> Tex-math let you see only the name of a macro, not the actual symbol.
>> Or, for this, am I forced to use other editors like kile?
>
> Well, at one time I seriously thought of including the functionality of
> unilatex.vim:
>
> http://www.vim.org/scripts/script.php?script_id=284
>
> into latex-suite. However, I never found the time or inclination. The
> problem is that working with a non-compilable version of the file always
> and only writing out the actual compilable version during a :write
> seemed to be somewhat risky. What if Vim (or latex-suite or the terminal
> or the remote connection or any number of things) crashed in the middle
> of the edit session. In this case, the file is effectively tainted...


There are other things also which can go wrong. I had a file where I 
had defined a command \PM for something. I also had set ignorecase 
option. So, unilatex, changed all \PM to +- and then wrote back \pm to 
the file. Took me a while to get everything back. unilatex should 
specifically set noignorecase while doing its substitutions.

However, visualizing math is not so easy, especially, since vim only 
displays text. For complicated mathematics, the unilatex is not that 
helpful. I wish vim could incorporate something like preview-latex. 
But, that is not going to happen anytime soon.

However, if you just want to know what a symbol looks like, get a copy 
of 
http://www.ctan.org/tex-archive/info/symbols/comprehensive/symbols-a4.pdf 
and keep it with you. It is more useful than the limited menus for 
maths on other editors.


Aditya

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

[Vim-latex-devel] why F5 ?

[Olivier R. <vi...@ri...>]

Hi again,

Can I change F5 to F10 ? F1 to F8 are used by my window manager.

Thanks,

Olivier.

Re: [Vim-latex-devel] listings packet

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

Hi,

On 4/17/06, Bernhard Walle <ber...@gm...> wrote:
> Hello,
>
> it would be nice if the lstlisting enviroment could be highlighted the
> same as verbatim.
>
> \begin{lstlisting}[language=3Dc,style=3Dinline]
> code
> \end{lstlisting}
>
> Thanks.
>
> Regards,
>   Bernhard

This is not the realm of vim-latex. Syntax highlighting is completely
untouched by vim-latex. AFAIK, Dr. Chip is the present maintainer of
the tex syntax highlighting. He is very responsive on the vim and
vim-dev mailing lists where this message belongs.

I am forwarding this to the vim-dev group.

Thanks,
Srinath

[Vim-latex-devel] listings packet

[Bernhard W. <ber...@gm...>]

Hello,

it would be nice if the lstlisting enviroment could be highlighted the
same as verbatim. 

\begin{lstlisting}[language=c,style=inline]
code
\end{lstlisting}

Thanks.

Regards,
  Bernhard
-- 
Bei der Eroberung des Weltraums sind zwei Probleme zu lösen: die
Schwerkraft und der Papierkrieg. Mit der Schwerkraft wären wir fertig
geworden. -- Wernher von Braun

Re: [Vim-latex-devel] Symbol visualization in vim-latex

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

Hi Fabio,

On 4/14/06, Fabio Stumbo <f.s...@un...> wrote:
>
> 1)Using gvim to edit a tex file, is it possible to have in some way
> a previsualization of the output of a math symbol?  The menus under
> Tex-math let you see only the name of a macro, not the actual symbol.
> Or, for this, am I forced to use other editors like kile?

Well, at one time I seriously thought of including the functionality of
unilatex.vim:

http://www.vim.org/scripts/script.php?script_id=3D284

into latex-suite. However, I never found the time or inclination. The
problem is that working with a non-compilable version of the file always
and only writing out the actual compilable version during a :write
seemed to be somewhat risky. What if Vim (or latex-suite or the terminal
or the remote connection or any number of things) crashed in the middle
of the edit session. In this case, the file is effectively tainted...

Ofcourse, its probably not such a hard thing to repair it, but the whole
thing sounded a little risky. And after a while, since no-one else
expressed any interest, I sort of let it go.

> 2)Is there a way to have the window splitted into two buffer so that in t=
he
> other buffer you have tex-math symbols?
>

Well, this seems safer. Maybe a scratch buffer which is scroll-locked
with the current buffer which shows a symbolic version of the current
file. However, there is a problem with continuously updating it with
every keystroke. So the implementation of this will be much harder. Vim
does not provide onKeyPress() like functions, so the updating will have
to be done by mapping every key... In short quite hard.

> 3)Is there a similar package for editing plain tex files?
>

Well, what part of latex-suite is plaintex incompatible?

Thanks,
Srinath

[Vim-latex-devel] how to switch SSS and \SSS ?

[Olivier R. <vi...@ri...>]

Hi,

 As a newbie I found quite difficult to learn all the features of this
wanderful tool. I would have love to have a memento with the list of
all the shorcuts.

 After getting informations from different sources, I start to
understand it enought to use it. However I still have few questions.
Here is the first one (others in the next mails...).

The 3 lettres shortcup are quite painful for the user who doesn't know
them and doesn't expect to see his text be transformed. That was the
reason I gave up with vim-latex a year ago.

Now I know how to do :

let g:Tex_EnvironmentMaps=0
let g:Tex_EnvironmentMenus=0
let g:Tex_FontMaps=0
let g:Tex_FontMenus=0
let g:Tex_SectionMaps=0
let g:Tex_SectionMenus=0

but it is quite frustrating since I'd like to use the 3 letters macros
but with a special key before. I expected this key to be g:Tex_Leader2
but no. How can I have a special key before all the 3 letters macros
without to redo everything myself ?

call IMAP (g:Tex_Leader2."FEM", "\\emph{<++>}<++>", "tex")

                                       TIA,

                                          Olivier.

[Vim-latex-devel] Symbol visualization in vim-latex

[Fabio S. <f.s...@un...>]

Hi all,

I have some question about vim-latex.

1)Using gvim to edit a tex file, is it possible to have in some way a 
previsualization of the output of a math symbol?
The menus under Tex-math let you see only the name of a macro, not the actual 
symbol.
Or, for this, am I forced to use other editors like kile?

2)Is there a way to have the window splitted into two buffer so that in the 
other buffer you have tex-math symbols?

I mean: if  1 and 2 are possible, I would like that when opening a tex 
file with gvim, then the look of the window should be quite similar to 
what you get using kile.

Please don't reply: then use kile!  I _do_ prefer to use vim.


3)Is there a similar package for editing plain tex files?

Thank you very much

Fabio

Re: [Vim-latex-devel] customization prob

[Vaidotas Z. <ze...@gm...>]

Hi,

CC'ing the list

On 4/10/06, Rene wrote:
> Dear Vaidotas,
>
> you were right. Starting from terminal, everything works just fine. This
> is a very strange and irritating behaviour, though. My advice would be
> putting this into a FAQ item, but don't know how frequently it is asked,
> of course...
>

Ok, I probably found the culprit. On Fedora Core machine the open with
menu uses net-gvim.desktop file for information (this file resides in
/usr/share/applications). In this file there is a line

Exec=3Dgvim -f %f

That means that the gvim will be started with option -f, which in
manual is described as

-f          Foreground.  For the GUI version, Vim will  not  fork  and
                   detach  from  the  shell it was started in.  On the Amig=
a,
                   Vim is not restarted to open a new  window.   This  opti=
on
                   should be used when Vim is executed by a program that wi=
ll
                   wait for the edit session to finish (e.g. mail).   On  t=
he
                   Amiga the ":sh" and ":!" commands will not work.

As far as I understand, translated to human language, this option
means trouble for vim-latex users.

The solutions for this can be:
1. Change the net-gvim.desktop file, by removing -f option
2. In open with menu choose "open with other" and enter gvim for
command, then use it instead of other vim menu, or make it the
default, so that nautilus always uses correct way of starting vim
3. File the bugs, so the people who shipped this file can fix that.


Vaidotas Zemlys

Re: [Vim-latex-devel] customization prob

[Vaidotas Z. <ze...@gm...>]

Hi,

On 4/9/06, Ren=E9 Lange <bit...@ti...> wrote:
> Hi,
>
> compiling via \ll works fine. But at \lv, I get no reaction. This is weir=
d.
>
> Ok, I see now that the settings in ~/.vim/ftplugin/tex.vim and
> ~/.vim/ftplugin/
> tex/texrc are being ignored completely.
>

I noticed this behaviour on Fedora Core machine with  latex-suite
20060325. This happens when opening tex file using nautilus open with
menu. Strangely it did not happen when started from terminal, or when
I explicitly told nautilus to open tex files with gvlm. So my advice
will be to try opening tex files from command line.

Hope it helps.

Vaidotas

[Vim-latex-devel] customization prob

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

Hi,

compiling via \ll works fine. But at \lv, I get no reaction. This is weir=
d.

Ok, I see now that the settings in ~/.vim/ftplugin/tex.vim and =20
~/.vim/ftplugin/
tex/texrc are being ignored completely.

Why can that be?
Greetings,
Ren=C3=A9 Lange

Re: [Vim-latex-devel] Changes for vim7

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

El Jueves 06 Abril 2006 02:40, Srinath Avadhanula escribi=F3:
> Hi guys,

> 3. Introduce some cool new features, or make some presently implemented
>    feature more usable. I really cannot think of too many at this point.
=2DThe autoclean feature, to delete auxiliar files on leaving vim. If possi=
ble=20
it should let the user define its own set=20
of extensions to match the files to be deleted

=2DDoes actually folding has a maximum nesting level? can I configure it us=
ing=20
vim's mechanism? I haven't tried, but i'd like to be able to have, e.g., at=
=20
most 3 folding levels? I take the chance to ask: the folding gets updated a=
s=20
I write? as I save? if I add lines, do I have to do \rf every time?

=2Da mechanism to set options of each document, e.g., a commented line on t=
op of=20
the file which allows the user to set the default compiler type, the=20
dependency chain, perhaps even the command to be used

> Any other thoughts/ideas? I'm also open to general usability complaints.
> One more thing which would be invaluable for me is if I can get an idea of
> what portions of vim-latex are actually being actively used. I know that I
> personally only use maybe 40% of vim-latex's code.

Let's see, I use:
=2DF5 and F7 a lot, with personalized expansions for environments like fram=
e or=20
figure
=2DF9 (bib and reference completion)
=2Dselect visually, and then enclose in a command or environment
=2Dchange the environment/command I'm within
=2DFolding!!!
=2Dthe expansions as SSE, EFI, etc
=2Docasionally, the expansions as `8, `6


> Srinath
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live
> webcast and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

=2D-=20
Javier Rojas

GPG key:
http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xA1C57061

[Vim-latex-devel] Tip for a handy latex compile rule

[Sebastian M. <seb...@un...>]

Hi

Since I have a large screen, I have vim and xdvi open next to each
other. After compiling, i always had to tell xdvi to reload by hand.

Since xdvi reloads if you send the SIGUSR1 signal to it, i have updated
my compile-rule as follows:

TexLet g:Tex_CompileRule_dvi = 'latex -src-specials
-interaction=nonstopmode $*; kill -SIGUSR1 `pgrep xdvi.bin`'

Now i can see what i'm tex'ing immediatly after each \ll.

Just to let you know ...

Sebastian.

Re: [Vim-latex-devel] Changes for vim7

[Vaidotas Z. <ze...@gm...>]

Hi,

On 4/6/06, Srinath Avadhanula <sri...@gm...> wrote:
> Hi guys,
>
> I finally completed my thesis (yay!) and have a little more time than usu=
al
> to devote to vim-latex.
Congratulations!

>
> Any other thoughts/ideas? I'm also open to general usability complaints.
> One more thing which would be invaluable for me is if I can get an idea o=
f
> what portions of vim-latex are actually being actively used. I know that =
I
> personally only use maybe 40% of vim-latex's code.

I myself use extensively the code from brackets.vim, i.e. Alt+l to get
\label, Alt+b to enclose previous letter in \mathbf, with my additions
for \mathbb, and few more more used commands. Also I use shift+f1 to
get align environment, `+something to get greek letters or some other
stuff, and also some of the EEN type of bindings. Ocasionally I use
F9, not a lot, but this probably will change, when I'll start to write
my own thesis:) Also I use my custom shortcuts for compiling and
viewing Alt+1 for dvi+ps+pdf, Alt+2 for dvi, Alt+7 for viewing dvi,
Alt+8 for viewing postscript and Alt+9 for viewing pdf. I posted these
customisations to list some time ago.

In general I'm very happy with vim-latex, and I do not have any
show-stopper or annoying problems. What I would like to improve a bit
though is a following:

1. (( always gives \left( \right), since I frequently need parenthesis
within parenthesis, this sometimes is annoying.
2. \left( \right) parenthesis are too big, so it would be nice to have
some automatisation with \big, \bigg and other similar style
parenthesis. I'm thinking something like `(b expanding to \big( \big)
or something similar.
3. It would be good to have one place to safely put simple
customisations of vim-latex, like shortcuts, or some code which is
made using only functions of vim-latex.

First two I think is easy to do, and probably I can do them myself,
the 3 probably can not be done at all.

Vaidotas Zemlys

Re: [Vim-latex-devel] Changes for vim7

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

Hi Srinath,

* On 06 Apr 2006 * Srinath Avadhanula wrote:

> Hi guys,
> 
> I finally completed my thesis (yay!) and have a little more time than usual
> to devote to vim-latex. So I just wanted to ask people for their opinions
> on what might be a good thing to do...

Congratulations for your thesis! 

> 
> There are potentially a number of things I can think of:
> 
> 1. A complete re-arrangement of vim-latex. The code is somewhat messy right
>    now. I am afraid that it will be impossible for anyone else to take over
>    even if they wanted to if I have to stop working on vim-latex sometime.
>    If you remember, I had to stop working on vim-latex for almost 6-7
>    months because of various research deadlines. It would be nice to have
>    at least one more person who understands things enough and is
>    enthusiastic enough to contribute occasional bug-fixes.

Would be nice; not for me, because I do not understand
enough of it, but for the future developing...
> 
> 2. Adapt vim-latex to vim7. Vim7 introduces the concept of the autoload
>    directory which has the potential for making vim-latex more modular and
>    also load faster at the same time.
> 
> 3. Introduce some cool new features, or make some presently implemented
>    feature more usable. I really cannot think of too many at this point.

One nice feature would be to create automatically the label for
sections, figures and tables!?

Greetings!
Fabian

Re: [Vim-latex-devel] Changes for vim7

[Andreas W. <A.W...@st...>]

Hello Srinath, hello list,

* Srinath Avadhanula wrote on Apr/06/2006:
> I finally completed my thesis (yay!)

Congratulations!!

-- 
Why is the alphabet in that order? Is it because of that song?

-- 
My Public PGP Keys:
1024 Bit DH/DSS: 0x869F81BA
768 Bit RSA:     0x1AD97BA5

[Vim-latex-devel] Changes for vim7

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

Hi guys,

I finally completed my thesis (yay!) and have a little more time than usual
to devote to vim-latex. So I just wanted to ask people for their opinions
on what might be a good thing to do...

There are potentially a number of things I can think of:

1. A complete re-arrangement of vim-latex. The code is somewhat messy right
   now. I am afraid that it will be impossible for anyone else to take over
   even if they wanted to if I have to stop working on vim-latex sometime.
   If you remember, I had to stop working on vim-latex for almost 6-7
   months because of various research deadlines. It would be nice to have
   at least one more person who understands things enough and is
   enthusiastic enough to contribute occasional bug-fixes.

2. Adapt vim-latex to vim7. Vim7 introduces the concept of the autoload
   directory which has the potential for making vim-latex more modular and
   also load faster at the same time.

3. Introduce some cool new features, or make some presently implemented
   feature more usable. I really cannot think of too many at this point.

Any other thoughts/ideas? I'm also open to general usability complaints.
One more thing which would be invaluable for me is if I can get an idea of
what portions of vim-latex are actually being actively used. I know that I
personally only use maybe 40% of vim-latex's code.

Srinath

Re: [Vim-latex-devel] copying lines between buffers

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

Hi,

I could reproduce this and fixed this in SVN. It was a relatively
small fix due to my misunderstanding of the unnamed register.

Srinath

On 4/4/06, Javier Rojas <jer...@gm...> wrote:

> On 4/4/06, Andreas Lagemann < ae...@in...> wrote:
> > Hello,
> > I installed latex-suite recently. Since then I cannot yank a line in on=
e
> > latex-buffer open another one and paste it there.
>
>
>  I have the same problem. To be able to copy between buffers I'm using na=
med
> buffers, for example, to copy a line to buffer "a" I use the command:
>
>  "ayy
>
>  and to paste it on the other buffer
>
>  "ap
>
> Despite the available workaround, this is IMHO a bug in vimlatex
>
>  Greets,
>
>  Javier Rojas
>
>