[Vim-latex-cvs] vimfiles/doc latex-suite.txt,1.27,1.28 latex-suite.xml,1.4,1.5
Brought to you by:
srinathava,
tmaas
Menu
▾
▴
[Vim-latex-cvs] vimfiles/doc latex-suite.txt,1.27,1.28 latex-suite.xml,1.4,1.5
|
From: <sri...@us...> - 2003-06-21 22:13:10
|
Update of /cvsroot/vim-latex/vimfiles/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv6663
Modified Files:
latex-suite.txt latex-suite.xml
Log Message:
More documentation. more fixed typos...
Still a lot more to go...
Index: latex-suite.txt
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.txt,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -d -r1.27 -r1.28
*** latex-suite.txt 20 Jun 2003 06:02:39 -0000 1.27
--- latex-suite.txt 21 Jun 2003 22:13:07 -0000 1.28
***************
*** 1,2 ****
--- 1,44 ----
+ bodyText = [[u'w', u'address'], [u'a', u'author'], [u'b', u'booktitle'], [u'c', u'chapter'], [u'd', u'edition'], [u'e', u'editor'], [u'h', u'howpublished'], [u'i', u'institution'], [u'k', u'isbn'], [u'j', u'journal'], [u'm', u'month'], [u'z', u'note'], [u'n', u'number'], [u'o', u'organization'], [u'p', u'pages'], [u'q', u'publisher'], [u'r', u'school'], [u's', u'series'], [u't', u'title'], [u'u', u'type'], [u'v', u'volume'], [u'y', u'year']]
+ bodyText = [[u'(', u'\\left( <++> \\right)'], [u'[', u'\\left[ <++> \\right]'], [u'|', u'\\left| <++> \\right|'], [u'{', u'\\left\\{ <++> \\right\\}'], [u'<', u'\\langle <++> \\rangle'], [u'q', u'\\lefteqn{<++>}<++>']]
+ bodyText = [[u'{New}', u'Creates a new (unnamed) buffer in the latex-suite/macros/ directory. Use the\ncommand :TexMacroNew in non-gui mode.'], [u'{Edit}', u'Opens up the corresponding macro file for editing. Use :TexMacroEdit in non-gui\nmode.'], [u'{Delete}', u'Deletes the corresponding macro. Use the prefixed numbers for fast navigation of\nmenus. Use :TexMacroDelete in non-gui mode.'], [u'{Redraw}', u'Rescans the macros/ directory and refreshes the macros list.']]
+ bodyText = [[u'startpat', u'a line matching this pattern defines the beginning of a fold.'], [u'endpat', u'a line matching this pattern defines the end of a fold.'], [u'startoff', u'this is the offset from the starting line at which folding will actually start'], [u'endoff', u'like startoff, but gives the offset of the actual fold end from the line satisfying endpat. startoff and\nendoff are necessary when the folding region does not have a specific end pattern corresponding to a start\npattern. for example in latex, \\begin{section} defines the beginning of a section, but its not necessary to\nhave a corresponding \\end{section} the section is assumed to end 1 line before another section starts.'], [u'startskip', u'A Pattern Which Defines The Beginning Of A "Skipped" Region.\n\nFor example, suppose we define a \\itemize fold as follows: >\n = \'^\\s*\\\\item\',\n = \'^\\s*\\\\item\\|^\\s*\\\\end{\\(enumerate\\|itemize\\|description\\)}\',\n = 0,\n = -1&codeend;\n\nThis defines a fold which starts with a line beginning with an \\item and ending one line before a line\nbeginning with an \\item or \\end{enumerate} etc.\n\nThen, as long as \\item\'s are not nested things are fine. However, once items begin to nest, the fold\nstarted by one \\item can end because of an \\item in an \\itemize environment within this \\item. i.e, the\nfollowing can happen: >\n \\begin{itemize}\n \\item Some text <------- fold will start here\n This item will contain a nested item\n \\begin{itemize} <----- fold will end here because next line contains \\item...\n \\item Hello \n \\end{itemize} <----- ... instead of here.\n \\item Next item of the parent itemize \n \\end{itemize}&codeend;\n\nTherefore, in order to completely define a folding item which allows nesting, we need to also define a\n"skip" pattern. startskip and end skip do that. Leave \'\' when there is no nesting.'], [u'endskip', u'the pattern which defines the end of the "skip" pattern for nested folds.']]
+ bodyText = [[u'<Plug>IMAP_JumpForward', u'<C-j>'], [u'<Plug>IMAP_JumpBack', u'(none)'], [u'<Plug>IMAP_DeleteAndJumpForward', u'(none)'], [u'<Plug>IMAP_DeleteAndJumpBack', u'(none)']]
+ bodyText = [[u'<Plug>Tex_MathBF', u'<Alt-B>'], [u'<Plug>Tex_MathCal', u'<Alt-C>'], [u'<Plug>Tex_LeftRight', u'<Alt-L>']]
+ bodyText = [[u'0', u'part'], [u'1', u'chapter'], [u'2', u'section'], [u'3', u'subsection'], [u'4', u'subsubsection'], [u'5', u'paragraph'], [u'6', u'subparagraph']]
+ bodyText = [[u'+<n>', u'inserts section name <n> logical levels above the last used comand'], [u'-<n>', u'inserts section name <n> logical levels below the last used comand'], [u'+', u'inserts section name one logical level below the last used command (equal to +1).'], [u'++', u'inserts section name two logical levels below the last used command (equal to +2).'], [u'-', u'inserts section name one logical level over the last used command (equal to -1).'], [u'--', u'inserts section name two logical levels over the last used command (equal to -2).']]
+ bodyText = [[u'g', u'General shortcuts'], [u'e', u'Environment shortcuts'], [u'f', u'Font shortcuts'], [u's', u'Section shortcuts'], [u'a', u'All shortcuts']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Imap_PlaceHolderStart', u'String', u"'<+'"], [u'Imap_PlaceHolderEnd', u'String', u"'+>'"]]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'g:Tex_EnvironmentMaps', u'Environment Mappings [|insert-mode-environment-mappings|]', u'1'], [u'g:Tex_EnvironmentMenus', '', u'1'], [u'g:Tex_FontMaps', u'Font Mappings [|font-maps|]', u'1'], [u'g:Tex_FontMenus', '', u'1'], [u'g:Tex_SectionMaps', u'Section Mappings [|section-mappings|]', u'1'], [u'g:Tex_SectionMenus', '', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']]
+ bodyText = [[u'Type', u'String'], [u'Default Value', u"'`'"]]
+ bodyText = [[u'Type', u'String'], [u'Default Value', u"','"]]
+ bodyText = [[u'Type', u'String'], [u'Default Value', u"'eqnarray*,eqnarray,equation,equation*,\\[,$$,align,align*'"]]
+ bodyText = [[u'Type', u'String'], [u'Default Value', u"'eqnarray*,eqnarray,bmatrix'"]]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'g:Tex_SmartQuoteOpen', u'"``"'], [u'g:Tex_SmartQuoteClose', u'"\'\'"']]
+ bodyText = [[u'g:Tex_ViewerCwindowHeight', u'The height of the cwindow which displays the list of \\labels etc.', u'5'], [u'g:Tex_ViewerPreviewHeight', u'The height of the preview window which shows the context of a \\label etc.', u'10'], [u'g:Tex_ExplorerHeight', u'The height of the explorer window which lists the files from which to choose an\nimage file.', u'10'], [u'g:Tex_ImageDir', u'The directory to scan for images', u"''"]]
+ bodyText = [[u'Type', u'string'], [u'Default Value', u"''"]]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']]
+ bodyText = [[u'Type', u'String'], [u'Default Value', u'dvi for windows/*nix and pdf for mac']]
+ bodyText = [[u'g:Tex_CompileRule_dvi', u"'latex -interaction=nonstopmode $*'"], [u'g:Tex_CompileRule_ps', u"'ps2pdf $*'"], [u'g:Tex_CompileRule_pdf', u"'pdflatex -interaction=nonstopmode $*'"]]
+ bodyText = [[u'Type', u'String'], [u'Default Value', u'a new-line seperated list of patterns as described below']]
+ bodyText = [[u'Type', u'Integer'], [u'Default Value', u'7']]
+ bodyText = [[u'g:Tex_ViewRule_dvi', u"'yap -1'", u"'xdvi'"], [u'g:Tex_ViewRule_ps', u"'gsview32'", u"'ghostview'"], [u'g:Tex_ViewRule_pdf', u"'AcroRd32'", u"'xpdf'"]]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'String'], [u'Default Value', u"'TeX-'"]]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']]
+ bodyText = [[u'Type', u'string'], [u'Default Value', u"''"]]
+ bodyText = [[u'Lubomir Host', u'provided the diacritics and also helped in development.\n\n'], [u'Alexander Wagner', u'valuable suggestions during development.\n\n'], [u'Luc Hermitte', u"his variation of Stephen Riehm's bracketing system is used in latex-suite.\n\n"], [u'Gergely Kontra', u'the clever little JumpFunc() in imaps.vim is due to him. The implementation of the\ntemplates also borrows from mu-template.vim by him.\n\n'], [u'Dimitri Antoniou', u'author of ltags and also provided the nice tip about forward / reverse search on\nDVI documents.\n\n'], [u'Stephen Riehm', u'the extremely helpful bracketing system is from him.\n\n'], [u'Alan Schmitt', u'provided some macros/folding elements.\n\n'], [u'Hari Krishna Dara', u'for ExecMap(), the clever little function which makes typing visual mode mappings\nso much easier and error-free.\n\n'], [u'Alan G Isac', u'for the comprehensive BibT() function for entering bibtex entries.\n\n'], [u'Gontran Baerts', u'for libList.vim\n\n'], [u'Peter Heslin', u'useful discussion and also a lot of bug fixes. the %%fakesection in folding.vim.\n\n']]
Latex-Suite Reference
*latex-suite.txt*
***************
*** 27,32 ****
|ls_2| Inserting Templates
|ls_3| Latex-Suite Macros
! |ls_3_1| Insert-mode Environment Mappings
! |ls_3_2| Visual-mode Environment Mappings
|ls_3_3| Font Mappings
|ls_3_4| Section Mappings
--- 69,74 ----
|ls_2| Inserting Templates
|ls_3| Latex-Suite Macros
! |ls_3_1| Environment Mappings
! |ls_3_2| LaTeX command maps
|ls_3_3| Font Mappings
|ls_3_4| Section Mappings
***************
*** 46,50 ****
|ls_5_1| Latex-Suite \cite completion
|ls_6| Compiling LaTeX files via Latex-Suite
! |ls_6_1| Setting Compilation rules.
|ls_6_2| Specifying which file to compile
|ls_6_3| Customizing the compiler output
--- 88,92 ----
|ls_5_1| Latex-Suite \cite completion
|ls_6| Compiling LaTeX files via Latex-Suite
! |ls_6_1| Setting Compilation rules
|ls_6_2| Specifying which file to compile
|ls_6_3| Customizing the compiler output
***************
*** 72,75 ****
--- 114,127 ----
================================================================================
+ Viewing this file
+
+ This file can be viewed with all the sections and subsections folded to ease
+ navigation. By default, vim does not fold help documents. To create the folds,
+ press za now.
+
+ See |usr_28.txt| for an introduction to folding and |fold-commands| for key
+ sequences and commands to work with folds.
+
+ ================================================================================
Recommended Settings *ls_1*
*recommended-settings*
***************
*** 77,86 ****
! Latex-Suite works best if you have the following settings in your ~/.vimrc: >
! " this line is responsible for loading latex-suite when a .tex file is
! " opened.
filetype plugin on
! " for automatic indentation specific to LaTeX.
filetype indent on
--- 129,149 ----
! Make sure that you create a few necessary settings in your ~/.vimrc. >
!
! " REQUIRED. This makes vim invoke latex-suite when you open a tex file.
filetype plugin on
!
! " IMPORTANT: win32 users will need to have 'shellslash' set so that latex
! " can be called correctly.
! set shellslash
!
! " IMPORTANT: grep will sometimes skip displaying the file name if you
! " search in a singe file. This will confuse latex-suite. Set your grep
! " program to alway generate a file-name.
! set grepprg=grep\ -nH\ $*
!
! " OPTIONAL: This enables automatic indentation as you type.
filetype indent on
+
***************
*** 94,100 ****
" all the figure labels. Very useful!
set iskeyword+=:
! " IMPORTANT: If you are a win32 user, then the following setting is
! " necessary in order to have latex called correctly from within Vim.
! set shellslash
--- 157,161 ----
" all the figure labels. Very useful!
set iskeyword+=:
!
***************
*** 135,140 ****
*latex-macros*
! |ls_3_1| Insert-mode Environment Mappings
! |ls_3_2| Visual-mode Environment Mappings
|ls_3_3| Font Mappings
|ls_3_4| Section Mappings
--- 196,201 ----
*latex-macros*
! |ls_3_1| Environment Mappings
! |ls_3_2| LaTeX command maps
|ls_3_3| Font Mappings
|ls_3_4| Section Mappings
***************
*** 185,194 ****
--------------------------------------------------------------------------------
! Insert-mode Environment Mappings *ls_3_1*
*insert-mode-environment-mappings*
- |ls_3_1_1| Method 1
- |ls_3_1_2| Method 2
- |ls_3_1_3| Method 3
- |ls_3_1_4| Method 4
These mappings insert LaTeX "environments" such as: >
--- 246,260 ----
--------------------------------------------------------------------------------
! Environment Mappings *ls_3_1*
! *environment-mappings*
! |ls_3_1_1| Insert-mode Mappings
! |ls_3_1_2| Visual-mode Mappings
! |ls_3_1_3| Normal Mode Mappings
!
! Latex-Suite provides a rich set of mappings to insert, enclose and modify LaTeX
! environments.
!
! Insert-mode Mappings *ls_3_1_1*
*insert-mode-environment-mappings*
These mappings insert LaTeX "environments" such as: >
***************
*** 203,207 ****
! Method 1 *ls_3_1_1*
*ls-imap-f5*
--- 269,273 ----
! Method 1 *ls_3_1_1_1*
*ls-imap-f5*
***************
*** 216,220 ****
! Method 2 *ls_3_1_2*
If you press <F5> while on a line containing a single word, then latex-suite
--- 282,286 ----
! Method 2 *ls_3_1_1_2*
If you press <F5> while on a line containing a single word, then latex-suite
***************
*** 222,234 ****
! Method 3 *ls_3_1_3*
! The shifted function keys, <S-F1> to <S-F4>can also be optionally mapped to some
! common environments which you insert most often. The environments mapped to each
! key can also be customized via the g:Tex_HotKeyMappings [|Tex_HotKeyMappings|]
! setting.
! Method 4 *ls_3_1_4*
Environments can also be inserted by pressing a 3 capital letter sequence
--- 288,300 ----
! Method 3 *ls_3_1_1_3*
! The shifted function keys, <S-F1> to <S-F4> can also be optionally mapped to
! some common environments which you insert most often. The environments mapped to
! each key can also be customized via the g:Tex_HotKeyMappings
! [|Tex_HotKeyMappings|] setting.
! Method 4 *ls_3_1_1_4*
Environments can also be inserted by pressing a 3 capital letter sequence
***************
*** 259,264 ****
item should give the hint for the map.
! --------------------------------------------------------------------------------
! Visual-mode Environment Mappings *ls_3_2*
*visual-mode-environment-mapings*
--- 325,330 ----
item should give the hint for the map.
!
! Visual-mode Mappings *ls_3_1_2*
*visual-mode-environment-mapings*
***************
*** 284,287 ****
--- 350,391 ----
+
+ Normal Mode Mappings *ls_3_1_3*
+ *normal-mode-environment-mappings*
+
+ Pressing <S-F5> in normal mode detects which environment the cursor is presently
+ located in and prompts you to replace it with a new one. The innermost
+ environment is detected. For example, in the following source: >
+ \begin{eqnarray}
+ \begin{array}{ccc}
+ 2 & 3 & 4
+ \end{array}
+ \end{eqnarray}
+ if you are located in the middle "2 & 3 & 4" line, then pressing <S-F5> will
+ prompt you to change the array environment, not the eqnarray environment. In
+ addition, Latex-Suite will also try to change lines within the environment to be
+ consistent with the new environment. For example, if the original environment
+ was an eqnarray environment with a \label command, then changing it to an
+ eqnarray* environment will delete the \label.
+
+ Pressing <F5> in normal mode has the same effect as pressing <F5> in
+ insert-mode, namely you will be prompted to choose an environment to insert.
+
+ --------------------------------------------------------------------------------
+ LaTeX command maps *ls_3_2*
+ *latex-command-maps*
+
+ *ls-imap-f7*
+ Latex-Suite provides two simple mappings <F7> and <S-F7> which work in both
+ insert and normal mode in an idential manner. Pressing <F7> prompts you with a
+ list of commands to choose from and then inserts it into the text of the
+ document. The list of commands is constructed from the g:Tex_PromptedCommands
+ [|Tex_PromptedCommands|] setting and also from commands which Latex-Suite finds
+ while scanning custom packages which Latex-Suite finds. See the Package actions
+ [|package-actions|] section for details on which files are scanned etc.
+
+ In both insert and normal mode <S-F7> will find out if you are presently within
+ an environment and then prompt you with a list of commands to change it to.
+
--------------------------------------------------------------------------------
Font Mappings *ls_3_3* *font-maps*
***************
*** 296,300 ****
2. next 2 letters are the 2 letters describing the font.
! Example: Typing FEM in insert-mode expands to \textem{<++>}<++>.
Just like environment mappings, you can visually select an area and press `sf to
--- 400,404 ----
2. next 2 letters are the 2 letters describing the font.
! Example: Typing FEM in insert-mode expands to \emph{<++>}<++>.
Just like environment mappings, you can visually select an area and press `sf to
***************
*** 565,571 ****
Latex-Suite utilizes a set of macros originally created by Carl Mueller in
! auctex.vim to make inserting all the \left ... \right stuff very easy. The
! following maps are provided:
--- 669,690 ----
Latex-Suite utilizes a set of macros originally created by Carl Mueller in
! auctex.vim to make inserting all the \left ... \right stuff very easy and to
! also make some use of the heavily under-utilized <Alt> key.
+ NOTE: By default, typing Alt-<key> in Vim takes focus to the menu bar if a menu
+ with the hotkey <key> exists. If in your case, there are conflicts due to
+ this behavior, you will need to set >
+ set winaltkeys=no
+ < in your $VIM/ftplugin/tex.vim in order to use these maps.
+
+
+ NOTE: Customizing the maps
+ --------------------
+ If for some reason, you wish to not map the <Alt> keys, (some European
+ users need to use the <Alt> key to enter diacritics), you can change these
+ maps to other keys as described in the section Customizing Alt-key maps
+ [|customize-alt-key-maps|].
+
+
***************
*** 602,619 ****
2. otherwise insert \cite{}.
In visual mode, it will simply enclose the selection in \mathcal{}
- NOTE: By default, typing Alt-<key> in Vim takes focus to the menu bar if a menu
- with the hotkey <key> exists. If in your case, there are conflicts due to
- this behavior, you will need to set >
- set winaltkeys=no
- < in your $VIM/ftplugin/tex.vim in order to use these maps.
-
-
- NOTE: Customizing the maps
- --------------------
- You can also customize the keys which trigger this functionality by
- remapping certain <Plug> mappings as described in Customizing Alt-key maps
- [|customize-alt-key-maps|].
-
-
--------------------------------------------------------------------------------
--- 721,724 ----
***************
*** 639,648 ****
! {New} Creates a new (unnamed) buffer in the latex-suite/macros/ directory.
! Use the command :TexMacroNew in non-gui mode.
! {Edit} Opens up the corresponding macro file for editing. Use :TexMacroEdit
! in non-gui mode.
! {Delete} Deletes the corresponding macro. Use the prefixed numbers for fast
! navigation of menus. Use :TexMacroDelete in non-gui mode.
{Redraw} Rescans the macros/ directory and refreshes the macros list.
--- 744,753 ----
! {New} Creates a new (unnamed) buffer in the latex-suite/macros/ directory. Use the
! command :TexMacroNew in non-gui mode.
! {Edit} Opens up the corresponding macro file for editing. Use :TexMacroEdit in non-gui
! mode.
! {Delete} Deletes the corresponding macro. Use the prefixed numbers for fast navigation of
! menus. Use :TexMacroDelete in non-gui mode.
{Redraw} Rescans the macros/ directory and refreshes the macros list.
***************
*** 715,718 ****
--- 820,824 ----
For example, the SIUnits package has a custom dictionary.
+ *latex-package-scanning*
If a package detected at startup is found by Latex-Suite in the current
directory or in a location specified by the g:Tex_TEXINPUTS [|Tex_TEXINPUTS|]
***************
*** 721,725 ****
commands and environments which you are prompted with when you press <F5>
[|ls-imap-f5|] or <F7> [|ls-imap-f7|] in insert mode.
- *latex-package-scanning*
In addition, the TeX-Suite > Packages menu also contains the following submenus
--- 827,830 ----
***************
*** 1058,1062 ****
*latex-compiling*
! |ls_6_1| Setting Compilation rules.
|ls_6_2| Specifying which file to compile
|ls_6_3| Customizing the compiler output
--- 1163,1167 ----
*latex-compiling*
! |ls_6_1| Setting Compilation rules
|ls_6_2| Specifying which file to compile
|ls_6_3| Customizing the compiler output
***************
*** 1089,1093 ****
--------------------------------------------------------------------------------
! Setting Compilation rules. *ls_6_1*
*compiler-rules*
--- 1194,1198 ----
--------------------------------------------------------------------------------
! Setting Compilation rules *ls_6_1*
*compiler-rules*
***************
*** 1315,1319 ****
table, figure etc. (an environment). In this case, if a \caption and/or a label
is found in the folded region, then those are used to make a more meaningful
! fold-tex, otherwise the second line of the environment is displayed along with
the name of the environment. In other words, the following
--- 1420,1424 ----
table, figure etc. (an environment). In this case, if a \caption and/or a label
is found in the folded region, then those are used to make a more meaningful
! fold-text, otherwise the second line of the environment is displayed along with
the name of the environment. In other words, the following
***************
*** 1375,1387 ****
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.
--- 1480,1488 ----
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.
***************
*** 1393,1404 ****
<
! 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
--- 1494,1503 ----
<
! 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
***************
*** 1411,1419 ****
<
! 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.
NOTE: Example 1
--- 1510,1516 ----
<
! 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.
NOTE: Example 1
***************
*** 1453,1458 ****
! LatexSuite defines set of commands for non-GUI and power users. They are taking
! care about Macros, Templates and Packages.
--- 1550,1555 ----
! This section describes the maps and commands used in Latex-Suite. It also
! describes a way to change the map sequences according to your preference.
***************
*** 1479,1487 ****
NOTE: To change the IMAP mappings which affect jumping between placeholders, the
map statement above has to be placed in your ~/.vimrc. For other mappings
! you can place the map statement in your $VIM/ftplugin/tex.vim file.
!
! The reason for this is that the <C-j> maps are created in
! plugin/imaps.vim, which is sourced as soon as Vim starts before sourcing
! any ftplugin files.
--- 1576,1582 ----
NOTE: To change the IMAP mappings which affect jumping between placeholders, the
map statement above has to be placed in your ~/.vimrc. For other mappings
! you can place the map statement in your $VIM/ftplugin/tex.vim file. The
! reason for this is that the <C-j> maps are created in plugin/imaps.vim,
! which is sourced as soon as Vim starts before sourcing any ftplugin files.
***************
*** 1645,1656 ****
+<n> inserts section name <n> logical levels above the last used comand
-<n> inserts section name <n> logical levels below the last used comand
! + inserts section name one logical level below the last used command (equal
! to +1).
! ++ inserts section name two logical levels below the last used command (equal
! to +2).
! - inserts section name one logical level over the last used command (equal
! to -1).
! -- inserts section name two logical levels over the last used command (equal
! to -2).
--- 1740,1747 ----
+<n> inserts section name <n> logical levels above the last used comand
-<n> inserts section name <n> logical levels below the last used comand
! + inserts section name one logical level below the last used command (equal to +1).
! ++ inserts section name two logical levels below the last used command (equal to +2).
! - inserts section name one logical level over the last used command (equal to -1).
! -- inserts section name two logical levels over the last used command (equal to -2).
***************
*** 1853,1864 ****
*Tex_SectionMaps*
*Tex_SectionMenus*
! Setting Link to relevant section Default Value~
! g:Tex_EnvironmentMaps Environment Mappings 1
! [|insert-mode-environment-mappings|]
! g:Tex_EnvironmentMenus 1
! g:Tex_FontMaps Font Mappings [|font-maps|] 1
! g:Tex_FontMenus 1
! g:Tex_SectionMaps Section Mappings [|section-mappings|] 1
! g:Tex_SectionMenus 1
--- 1944,1954 ----
*Tex_SectionMaps*
*Tex_SectionMenus*
! Setting Link to relevant section Default Value~
! g:Tex_EnvironmentMaps Environment Mappings [|insert-mode-environment-mappings|] 1
! g:Tex_EnvironmentMenus 1
! g:Tex_FontMaps Font Mappings [|font-maps|] 1
! g:Tex_FontMenus 1
! g:Tex_SectionMaps Section Mappings [|section-mappings|] 1
! g:Tex_SectionMenus 1
***************
*** 2024,2039 ****
*Tex_ExplorerHeight*
*Tex_ImageDir*
! Setting Explanation Default Value~
! g:Tex_ViewerCwindowHeight The height of the cwindow which 5
! displays the list of \labels
! etc.
! g:Tex_ViewerPreviewHeight The height of the preview window 10
! which shows the context of a
! \label etc.
! g:Tex_ExplorerHeight The height of the explorer 10
! window which lists the files
! from which to choose an image
! file.
! g:Tex_ImageDir The directory to scan for images ''
--- 2114,2123 ----
*Tex_ExplorerHeight*
*Tex_ImageDir*
! Setting Explanation Default Value~
! g:Tex_ViewerCwindowHeight The height of the cwindow which displays the list of \labels etc. 5
! g:Tex_ViewerPreviewHeight The height of the preview window which shows the context of a \label etc. 10
! g:Tex_ExplorerHeight The height of the explorer window which lists the files from which to choose an 10
! image file.
! g:Tex_ImageDir The directory to scan for images ''
***************
*** 2081,2091 ****
Type String
! Default Value dvi for windows/*nix and
! pdf for mac
! Use this setting to choose the default compilation target. For example, setting
! this to pdf makes Latex-Suite compile a pdf file when you press \l. Make sure
! that a rule has been defined for compiling to this target format as described
! here [|Tex_CompileRule_format|].
--- 2165,2175 ----
Type String
! Default Value dvi for windows/*nix and pdf for mac
! Use this setting to choose the default target format. For example, setting this
! to pdf makes Latex-Suite compile a pdf file when you press \ll and fire up the
! pdf viewer on pressing \lv. Make sure that a rules for compiling and viewing
! have been defined for this target format as described here
! [|Tex_CompileRule_format|] and here [|Tex_ViewRule_format|].
***************
*** 2098,2108 ****
! g:Tex_CompileRule_dvi 'latex
! -interaction=nonstopmode
! $*'
g:Tex_CompileRule_ps 'ps2pdf $*'
! g:Tex_CompileRule_pdf 'pdflatex
! -interaction=nonstopmode
! $*'
If you desire forward and inverse searching via Latex-Suite, you will need to
--- 2182,2188 ----
! g:Tex_CompileRule_dvi 'latex -interaction=nonstopmode $*'
g:Tex_CompileRule_ps 'ps2pdf $*'
! g:Tex_CompileRule_pdf 'pdflatex -interaction=nonstopmode $*'
If you desire forward and inverse searching via Latex-Suite, you will need to
***************
*** 2354,2368 ****
! Luc Hermitte his variation of Stephen Riehm's bracketing system is used in
! latex-suite.
! Gergely Kontra the clever little JumpFunc() in imaps.vim is due to him. The
! implementation of the templates also borrows from
! mu-template.vim by him.
! Dimitri Antoniou author of ltags and also provided the nice tip about forward
! / reverse search on DVI documents.
--- 2434,2446 ----
! Luc Hermitte his variation of Stephen Riehm's bracketing system is used in latex-suite.
! Gergely Kontra the clever little JumpFunc() in imaps.vim is due to him. The implementation of the
! templates also borrows from mu-template.vim by him.
! Dimitri Antoniou author of ltags and also provided the nice tip about forward / reverse search on
! DVI documents.
***************
*** 2373,2382 ****
! Hari Krishna Dara for ExecMap(), the clever little function which makes typing
! visual mode mappings so much easier and error-free.
! Alan G Isac for the comprehensive BibT() function for entering bibtex
! entries.
--- 2451,2459 ----
! Hari Krishna Dara for ExecMap(), the clever little function which makes typing visual mode mappings
! so much easier and error-free.
! Alan G Isac for the comprehensive BibT() function for entering bibtex entries.
***************
*** 2384,2389 ****
! Peter Heslin useful discussion and also a lot of bug fixes. the
! %%fakesection in folding.vim.
--- 2461,2465 ----
! Peter Heslin useful discussion and also a lot of bug fixes. the %%fakesection in folding.vim.
***************
*** 2410,2415 ****
vim:ft=help:fdm=expr
! vim:foldexpr=getline(v\:lnum-1)=~"=\\\\{80,}"?"a1"\:(getline(v\:lnum+1)=~"=\\\\{80,}"?"s1"\:"=")
vim:foldtext=v\:folddashes.substitute(getline(v\:foldstart),"\\\\s*\\\\*.*","","")
================================================================================
-
--- 2486,2490 ----
vim:ft=help:fdm=expr
! vim:foldexpr=getline(v\:lnum-1)=~'-\\{80}'?'>2'\:getline(v\:lnum-1)=~'=\\{80}'?'>1'\:getline(v\:lnum)=~'=\\{80}'?'0'\:getline(v\:lnum)=~'-\\{80}'?'1'\:'='
vim:foldtext=v\:folddashes.substitute(getline(v\:foldstart),"\\\\s*\\\\*.*","","")
================================================================================
Index: latex-suite.xml
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** latex-suite.xml 20 Jun 2003 06:02:39 -0000 1.4
--- latex-suite.xml 21 Jun 2003 22:13:07 -0000 1.5
***************
*** 56,65 ****
<title>Recommended Settings</title>
<para>
! Latex-Suite works best if you have the following settings in your ~/.vimrc:
! <programlisting>" this line is responsible for loading latex-suite when a .tex file is
! " opened.
filetype plugin on
! " for automatic indentation specific to LaTeX.
! filetype indent on</programlisting>
</para>
<para>
--- 56,77 ----
<title>Recommended Settings</title>
<para>
! Make sure that you create a few necessary settings in your
! <literal>~/.vimrc.</literal>
! <programlisting>
! " REQUIRED. This makes vim invoke latex-suite when you open a tex file.
filetype plugin on
!
! " IMPORTANT: win32 users will need to have 'shellslash' set so that latex
! " can be called correctly.
! set shellslash
!
! " IMPORTANT: grep will sometimes skip displaying the file name if you
! " search in a singe file. This will confuse latex-suite. Set your grep
! " program to alway generate a file-name.
! set grepprg=grep\ -nH\ $*
!
! " OPTIONAL: This enables automatic indentation as you type.
! filetype indent on
! </programlisting>
</para>
<para>
***************
*** 73,79 ****
" all the figure labels. Very useful!
set iskeyword+=:
! " IMPORTANT: If you are a win32 user, then the following setting is
! " necessary in order to have latex called correctly from within Vim.
! set shellslash</programlisting>
</para>
</section>
--- 85,89 ----
" all the figure labels. Very useful!
set iskeyword+=:
! </programlisting>
</para>
</section>
***************
*** 165,227 ****
by &ls;.
</para>
! <section id="insert-mode-environment-mappings">
! <title>Insert-mode Environment Mappings</title>
! <para> These mappings insert LaTeX "environments" such as:
! <programlisting>\begin{center}
&ph;
\end{center}&ph;</programlisting>
! with the cursor left at the first |placeholder|. There are
! various ways of inserting environments into the source file. If
! the environment is a standard latex environment, then latex suite
! might also include common fields associated with it.
! </para>
! <section id="ls-imap-f5">
! <title>Method 1</title>
! <para>
! If you press <literal><F5></literal> in the
! insert mode while on an empty line, latex-suite prompts you
! with a list of environments you might want to insert. You can
! either choose one from the list or type in a new environment
! name. This list can be customized via the <link
! linkend="Tex_PromptedEnvironments"><literal>g:Tex_PromptedEnvironments</literal></link>
! setting.
</para>
! <para>
! In addition to the <literal>Tex_PromptedEnvironments</literal>
! variable, &ls; also lists envionments found in custom packages as
! described in the section <link linkend="package-actions">Package
! actions.</link>
</para>
</section>
! <section>
! <title>Method 2</title>
! <para>
! If you press <literal><F5></literal> while on a line
! containing a single word, then latex-suite creates a
! environment of that name.
</para>
</section>
! <section>
! <title>Method 3</title>
! <para>
! The shifted function keys, <literal><S-F1></literal> to
! <literal><S-F4></literal>can also be optionally mapped
! to some common environments which you insert most often. The
! environments mapped to each key can also be customized via the <link
! linkend="Tex_HotKeyMappings">g:Tex_HotKeyMappings</link> setting.
</para>
</section>
! <section>
! <title>Method 4</title>
! <para>
! Environments can also be inserted by pressing a 3 capital
! letter sequence starting with an <literal>E</literal>. The following subsection
! describes this in detail. The sequence of 3 letters generally
! tries to follow the following rules:
</para>
<orderedlist>
<listitem>
All environment mappings begin with <literal>E</literal>
! </listitem>
<listitem>
If the environment can be broken up into 2 distinct words,
--- 175,242 ----
by &ls;.
</para>
! <section id="environment-mappings">
! <title>Environment Mappings</title>
! &ls; provides a rich set of mappings to insert, enclose and modify
! &latex; environments.
! <section id="insert-mode-environment-mappings">
! <title>Insert-mode Mappings</title>
! <para>
! These mappings insert LaTeX "environments" such as:
! <programlisting>\begin{center}
&ph;
\end{center}&ph;</programlisting>
! with the cursor left at the first |placeholder|. There are
! various ways of inserting environments into the source file. If
! the environment is a standard latex environment, then latex suite
! might also include common fields associated with it.
</para>
! <section id="ls-imap-f5">
! <title>Method 1</title>
! <para>
! If you press <literal><F5></literal> in the
! insert mode while on an empty line, latex-suite prompts you
! with a list of environments you might want to insert. You can
! either choose one from the list or type in a new environment
! name. This list can be customized via the <link
! linkend="Tex_PromptedEnvironments"><literal>g:Tex_PromptedEnvironments</literal></link>
! setting.
! </para>
! <para>
! In addition to the <literal>Tex_PromptedEnvironments</literal>
! variable, &ls; also lists envionments found in custom packages as
! described in the section <link linkend="package-actions">Package
! actions.</link>
</para>
</section>
! <section>
! <title>Method 2</title>
! <para>
! If you press <literal><F5></literal> while on a line
! containing a single word, then latex-suite creates a
! environment of that name.
</para>
</section>
! <section>
! <title>Method 3</title>
! <para>
! The shifted function keys, <literal><S-F1></literal> to
! <literal><S-F4></literal> can also be optionally mapped
! to some common environments which you insert most often. The
! environments mapped to each key can also be customized via the <link
! linkend="Tex_HotKeyMappings">g:Tex_HotKeyMappings</link> setting.
</para>
</section>
! <section>
! <title>Method 4</title>
! <para>
! Environments can also be inserted by pressing a 3 capital
! letter sequence starting with an <literal>E</literal>. The following subsection
! describes this in detail. The sequence of 3 letters generally
! tries to follow the following rules:
</para>
<orderedlist>
<listitem>
All environment mappings begin with <literal>E</literal>
! </listitem>
<listitem>
If the environment can be broken up into 2 distinct words,
***************
*** 236,284 ****
Example:
<programlisting>equation (_eq_uation) ---> EEQ</programlisting>
! </listitem>
</orderedlist>
! <para>
! Unfortunately there are some environments that cannot be
! split in two words and first two letters in name are
! identical. In this case shortcut is created from E, first and
! last letter. Example:
! <programlisting>quote (_q_uot_e_) ---> EQE
quotation (_q_uotatio_n_) ---> EQN</programlisting>
! Of course, not every last one of the environments can follow
! this rule because of ambiguities. In case of doubt, pull down
! the Tex-Environments menu. The menu item should give the hint
! for the map.
</para>
</section>
</section>
! <section id="visual-mode-environment-mapings">
! <title>Visual-mode Environment Mappings</title>
! <para>
! &ls; provides visual-mode mappings which enclose visually
! selected portions of text in environments. These mappings are
! derived from the corresponding insert-mode environment mappings
! according to the following simple rule:
! <programlisting>ECE --> ,ce</programlisting>
! The rule simply says that the leading <literal>E</literal> is
! converted to <literal>,</literal> and the next 2 letters are
! small case.
! Here <literal>ECE</literal> is the insert-mode map which inserts
! the <literal>\begin{center} ... \end{center}</literal>
! environment. Correspondingly, if you select a portion of text
! visually and press <literal>,ce</literal> while still in visual
! mode, then the selected portion will be enclosed in
! <literal>\begin{center} ... \end{center}</literal>.
! Some of the visual mode mappings are sensitive to whether you
! choose line-wise or character-wise. For example, if you choose a
! word and press <literal>,ce</literal>, then you get
! <literal>\centerline{word}</literal>, whereas if you press
! <literal>,ce</literal> on a line-wise selection, you get:
! <programlisting>\begin{center}
line
\end{center}</programlisting>
</para>
</section>
<section id="font-maps">
--- 251,350 ----
Example:
<programlisting>equation (_eq_uation) ---> EEQ</programlisting>
! </listitem>
</orderedlist>
! <para>
! Unfortunately there are some environments that cannot be
! split in two words and first two letters in name are
! identical. In this case shortcut is created from E, first and
! last letter. Example:
! <programlisting>quote (_q_uot_e_) ---> EQE
quotation (_q_uotatio_n_) ---> EQN</programlisting>
! Of course, not every last one of the environments can follow
! this rule because of ambiguities. In case of doubt, pull down
! the Tex-Environments menu. The menu item should give the hint
! for the map.
</para>
</section>
</section>
! <section id="visual-mode-environment-mapings">
! <title>Visual-mode Mappings</title>
! <para>
! &ls; provides visual-mode mappings which enclose visually
! selected portions of text in environments. These mappings are
! derived from the corresponding insert-mode environment mappings
! according to the following simple rule:
! <programlisting>ECE --> ,ce</programlisting>
! The rule simply says that the leading <literal>E</literal> is
! converted to <literal>,</literal> and the next 2 letters are
! small case.
! Here <literal>ECE</literal> is the insert-mode map which inserts
! the <literal>\begin{center} ... \end{center}</literal>
! environment. Correspondingly, if you select a portion of text
! visually and press <literal>,ce</literal> while still in visual
! mode, then the selected portion will be enclosed in
! <literal>\begin{center} ... \end{center}</literal>.
! Some of the visual mode mappings are sensitive to whether you
! choose line-wise or character-wise. For example, if you choose a
! word and press <literal>,ce</literal>, then you get
! <literal>\centerline{word}</literal>, whereas if you press
! <literal>,ce</literal> on a line-wise selection, you get:
! <programlisting>\begin{center}
line
\end{center}</programlisting>
</para>
+ </section>
+ <section id="normal-mode-environment-mappings">
+ <title>Normal Mode Mappings</title>
+ <para>
+ Pressing <literal><S-F5></literal> in normal mode detects which
+ environment the cursor is presently located in and prompts you to
+ replace it with a new one. The innermost environment is detected. For
+ example, in the following source:
+ <programlisting>\begin{eqnarray}
+ \begin{array}{ccc}
+ 2 & 3 & 4
+ \end{array}
+ \end{eqnarray}</programlisting>
+ if you are located in the middle "2 & 3 & 4" line, then pressing
+ <literal><S-F5></literal> will prompt you to change the array
+ environment, not the eqnarray environment. In addition, &ls; will also
+ try to change lines within the environment to be consistent with the
+ new environment. For example, if the original environment was an
+ <literal>eqnarray</literal> environment with a
+ <literal>\label</literal> command, then changing it to an
+ <literal>eqnarray*</literal> environment will delete the
+ <literal>\label</literal>.
+ </para>
+ <para>
+ Pressing <literal><F5></literal> in normal mode has the same
+ effect as pressing <literal><F5></literal> in insert-mode,
+ namely you will be prompted to choose an environment to insert.
+ </para>
+ </section>
+ </section>
+ <section id="latex-command-maps">
+ <title>&latex; command maps</title>
+ <anchor id="ls-imap-f7" />
+ <para>
+ &ls; provides two simple mappings <literal><F7></literal> and
+ <literal><S-F7></literal> which work in both insert and normal
+ mode in an idential manner. Pressing <literal><F7></literal>
+ prompts you with a list of commands to choose from and then inserts it
+ into the text of the document. The list of commands is constructed from
+ the <link
+ linkend="Tex_PromptedCommands"><literal>g:Tex_PromptedCommands</literal></link>
+ setting and also from commands which &ls; finds while scanning custom
+ packages which &ls; finds. See the <link
+ linkend="package-actions">Package actions</link> section for details
+ on which files are scanned etc.
+ </para>
+ <para>
+ In both insert and normal mode <literal><S-F7></literal> will
+ find out if you are presently within an environment and then prompt you
+ with a list of commands to change it to.
+ </para>
</section>
<section id="font-maps">
***************
*** 299,303 ****
<para>
Example: Typing <literal>FEM</literal> in insert-mode expands to
! <literal>\textem{&ph;}&ph;</literal>.
</para>
<para>
--- 365,369 ----
<para>
Example: Typing <literal>FEM</literal> in insert-mode expands to
! <literal>\emph{&ph;}&ph;</literal>.
</para>
<para>
***************
*** 598,603 ****
&ls; utilizes a set of macros originally created by Carl Mueller in
auctex.vim to make inserting all the <literal>\left ... \right</literal>
! stuff very easy. The following maps are provided:
</para>
<section id="Alt-L">
<title><literal><Alt-L></literal></title>
--- 664,691 ----
&ls; utilizes a set of macros originally created by Carl Mueller in
auctex.vim to make inserting all the <literal>\left ... \right</literal>
! stuff very easy and to also make some use of the heavily under-utilized
! <literal><Alt></literal> key.
</para>
+ <note>
+ <para>
+ By default, typing <literal>Alt-<key></literal> in &vim; takes
+ focus to the menu bar if a menu with the hotkey
+ <literal><key></literal> exists. If in your case, there are
+ conflicts due to this behavior, you will need to set
+ <programlisting>set winaltkeys=no</programlisting>
+ in your <literal>$VIM/ftplugin/tex.vim</literal> in order to use these
+ maps.
+ </para>
+ </note>
+ <note>
+ <title>Customizing the maps</title>
+ <para>
+ If for some reason, you wish to not map the
+ <literal><Alt></literal> keys, (some European users need to use
+ the <literal><Alt></literal> key to enter diacritics), you can
+ change these maps to other keys as described in the section <link
+ linkend="customize-alt-key-maps">Customizing Alt-key maps</link>.
+ </para>
+ </note>
<section id="Alt-L">
<title><literal><Alt-L></literal></title>
***************
*** 657,679 ****
</para>
</section>
- <note>
- <para>
- By default, typing <literal>Alt-<key></literal> in &vim; takes
- focus to the menu bar if a menu with the hotkey
- <literal><key></literal> exists. If in your case, there are
- conflicts due to this behavior, you will need to set
- <programlisting>set winaltkeys=no</programlisting>
- in your <literal>$VIM/ftplugin/tex.vim</literal> in order to use these
- maps.
- </para>
- </note>
- <note>
- <title>Customizing the maps</title>
- <para>You can also customize the keys which trigger this functionality
- by remapping certain <literal><Plug></literal> mappings as
- described in <link linkend="customize-alt-key-maps">Customizing
- Alt-key maps</link>.
- </para>
- </note>
</section>
<section id="custom-macros-menu">
--- 745,748 ----
***************
*** 816,819 ****
--- 885,889 ----
dictionary.
</para>
+ <anchor id="latex-package-scanning" />
<para>
If a package detected at startup is found by &ls; in the current
***************
*** 829,833 ****
</para>
</section>
- <anchor id="latex-package-scanning" />
<para>
In addition, the <literal>TeX-Suite > Packages</literal> menu also
--- 899,902 ----
***************
*** 1258,1262 ****
</para>
<section id="compiler-rules">
! <title>Setting Compilation rules.</title>
<para>
In order to compile &latex; files into various formats, &ls; needs to know
--- 1327,1331 ----
</para>
<section id="compiler-rules">
! <title>Setting Compilation rules</title>
<para>
In order to compile &latex; files into various formats, &ls; needs to know
***************
*** 1524,1528 ****
table, figure etc. (an environment). In this case, if a \caption and/or a
label is found in the folded region, then those are used to make a more
! meaningful fold-tex, otherwise the second line of the environment is displayed
along with the name of the environment. In other words, the following
</para>
--- 1593,1597 ----
table, figure etc. (an environment). In this case, if a \caption and/or a
label is found in the folded region, then those are used to make a more
! meaningful fold-text, otherwise the second line of the environment is displayed
along with the name of the environment. In other words, the following
</para>
***************
*** 1715,1720 ****
<title>&ls; Commands and Maps</title>
<para>
! LatexSuite defines set of commands for non-GUI and power users. They are
! taking care about Macros, Templates and Packages.
</para>
<section id="latex-suite-maps">
--- 1784,1790 ----
<title>&ls; Commands and Maps</title>
<para>
! This section describes the maps and commands used in &ls;. It also
! describes a way to change the map sequences according to your
! preference.
</para>
<section id="latex-suite-maps">
***************
*** 1744,1753 ****
to be placed in your <literal>~/.vimrc</literal>. For other mappings
you can place the <literal>map</literal> statement in your
! <literal>$VIM/ftplugin/tex.vim</literal> file.
! </para>
! <para>
! The reason for this is that the <literal><C-j></literal> maps
! are created in <literal>plugin/imaps.vim</literal>, which is sourced
! as soon as &vim; starts before sourcing any ftplugin files.
</para>
</note>
--- 1814,1821 ----
to be placed in your <literal>~/.vimrc</literal>. For other mappings
you can place the <literal>map</literal> statement in your
! <literal>$VIM/ftplugin/tex.vim</literal> file. The reason for this is
! that the <literal><C-j></literal> maps are created in
! <literal>plugin/imaps.vim</literal>, which is sourced as soon as &vim;
! starts before sourcing any ftplugin files.
</para>
</note>
***************
*** 2594,2602 ****
</informaltable>
<para>
! Use this setting to choose the default compilation target. For example,
! setting this to <literal>pdf</literal> makes &ls; compile a pdf file when
! you press <literal>\l</literal>. Make sure that a rule has been defined
! for compiling to this target format as described <link
! linkend="Tex_CompileRule_format">here</link>.
</para>
</section>
--- 2662,2673 ----
</informaltable>
<para>
! Use this setting to choose the default target format. For example,
! setting this to <literal>pdf</literal> makes &ls; compile a pdf file
! when you press <literal>\ll</literal> and fire up the
! <literal>pdf</literal> viewer on pressing <literal>\lv</literal>. Make
! sure that a rules for compiling and viewing have been defined for this
! target format as described <li...
[truncated message content] |
