Re: [Vim-latex-devel] Review of vim-latex status

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

On Thu, 26 Dec 2002, Mikolaj Machowski wrote:

> Some new are awaiting in home for stabilization of new placeholders
> system.

The placeholder system has been stabilized.. If we do make any changes,
it will be internal changes, so the interace never changes... In all the
package files, just use the '<+' and '+>' characters instead of the old
=AB and =BB characters...

> diacritics are rarely used. If you need it for your national letters
> probably they are built-in in LaTeX and you don't need to play with =3Db
> things. Maybe disable it by default and add switch to turn it on/off?
>
Precisely what I was thinking... I will disable them by default.

> Why? pdflatex thing works good enough. Dvi format has advantage of
> possibility of forward/backward searching in dvi viewers but if you need
> it you will be making pdf files at the end of day.
>
Well, its just a nice thing to do... I gave pdf as an example... For ps
files, afaik, dvips is the only way... Morevoer, this will be
customizable. If the user wants to use pdflatex, he would be able to
tell latex-suite to use pdflatex which takes tex files not ps files...

> > 3. New developer: Becase Luc has implemented both 2 and 3 in lh-tex, I
> >    propose that we get Luc into the developer team if he wants. To star=
t
> >    with, he can implement his ideas on a seperate branch. Afterwards, w=
e
> >    can merge this into the main trunk.
>
> Fine :)

Luc, Please let us know if you think you like this idea...

Also, Carl Mueller has made invaluable contributions to latex-suite. If
he desires, he could join the team too

> > 4. Citation browser: I know that auctex from emacs has a feature where
> >    it sets up a browsable window of the citations found in the bibtex
> >    file. We could implement a system where if the user presses <Alt-c>,
> >    \cite{} is inserted and the browser comes up asking him to choose a
> >    citation.
>
> It could be done also for labels, refpages and so on. I did some time
> ago something like this. I have to find it...
>
Let's make this as general as possible, so the citation browser, the
reference browser etc only have to supply a list to some central handler
function...

> > 5. Removal of unwanted cruft: I am pretty sure latex-suite has features
> >    which it can afford to lose.
>
> Hmm. I would vote for "other miscellaneous stuff taken from imaps.vim in
> main.vim (lines 117-136 in my version). This is really redundant IMO.
>
Done! Feel free to suggest more deletions.

> 1. Move smartspace.vim and brackets.vim to ftplugin/latex-suite
> directory (and add proper lines in main.vim). Now they are in
> ftplugin/tex dir and they are automagically sourced. IMO this is a Bad
> Thing(tm). We do not have control in which order they are sourced and
> more important user doesn't have control.  Because this files have
> mappings user should have possibility to overwrite it. With latex-suite
> files in ftplugin/tex dir user have to give special names to be sure his
> files are sourced at the end.
>
Well, overwriting the maps is not a problem. See the latest version of
tex/brackets.vim. It does

if !hasmapto('Tex_MathBF', 'i') && mapcheck('<M-b>', 'i') =3D=3D ''
=09inoremap <buffer> <silent> <M-b> <C-r>=3DTex_MathBF()<CR>
endif

This enables a user to overwrite the plugin using something like

inoremap <buffer> <silent> mykey <C-r>=3DTex_MathBF()<cr>

his ftplugin/tex.vim file.

The reason I chose this way was this provides a nice (or at least easy)
way to extend latex-suite. The final aim is that each of these files is
kind of independent of the rest, so the user can pick up whatever pieces
he wants. Also note that tex_latexSuite.vim is still sourced before
files in the tex/ directory. Therefore latex-suite will still be able to
provide hooks to these plugins if wanted... I wonder what others think
of this issue...

> 2. Create vim-latex format with vim-latex menus integrated with normal
> Vim menus like this is in HTML editors. For example: disable Syntax
> menus, put TeX-Suite/Templates menu into File/New Latex File menu.
>
Hmmm... I am not really sure what you mean... What do you mean by
'vim-latex' format? Also, whats a natural place for the TeX-Environments
menu? That will have to be seperate, right?

Srinath