Re: [Vim-latex-devel] Vim LaTeX Suite Tutorial -WIP

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

On Mon, May 19, 2003 at 09:30:46AM +0200, Animesh Nerurkar wrote:
> 1) introduction (naturally)
> 2) download and install instructions for Vim LaTeX Suite (i'll shorten this
> to VLS hencforth).
> 3) instructions to setup and use VLS help in (g)vim 6.x
> 4) recommend gvim as a starter for newbies (they can switch to vim later as
> their skill levels increase).

Gvim also offers more - menus, I am currently working on utf-8 menus:
most symbols will be visible beside their names, tips for shortcuts, and
so on. Also some of shortcuts don't work properly in various terminals
(of course it is bug in terminals not in lS :).

Also gvim more cross-platform: I hear Vim in Mac's term can behave
strange, also for Windows there is no real terminal.

> 5) VLS menu items. HOWTO use VLS menu items.
> 6) VLS "insert mode" keymap stds. (E for environment etc.) and HOWTO use
> these.
> 7) VLS "visual mode" keymap stds. and HOWTO use these.
> 8) HOWTO use templates and add custom templates.
> 9) HOWTO use various packages bundled into VLS.
> 10) table the available keymaps for both modes and list what they do. (shud
> this be included as a tear-off cheat sheet?)

I would suggest make it in form of guide through writing of document.
After description of download and installation it would be:
1) Choose template. Nothing appropriate (eg non-standard documentclass).
Write my own. Use that template.
2) Make additions to preamble - it will be introduction of how to use
packages system, scanning preamble for \newcommand etc.
3) Write document - insert, change environments (you could shortly
explain Environment Wizard - disabled by default in favour of
placeholders):
<F5>, <S-F5> - maps
4) Here you could make copy&paste two or three paragraphs from word
processor or text/plain and edit them with Visual mappings.
5) Describe making of bibliography with bibtex.vim - unfortunately this
part has NULL documentation AFAIK and use <F9> for inserting bibkeys.

IMO this type of tutorial will be easier to understand (not necessarily
to write!). HOWTO style instructions should better be in main doc file.

BTW. In what form this tutorial will be originally? LaTeX, html, text?
If LaTeX you could just describe how you are writing it :) Only add some
math.

m.