File: latex-suite.html

package info (click to toggle)
vim-latexsuite 20100129-2
links: PTS, VCS
area: main
in suites: squeeze
size: 3,132 kB
ctags: 810
sloc: xml: 5,096; python: 285; makefile: 92; perl: 59; sh: 14
file content (2673 lines) | stat: -rw-r--r-- 217,047 bytes
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Latex-Suite Reference</title><link rel="stylesheet" href="latex-suite.css" type="text/css"></link><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"></meta><meta name="description" content="Latex-Suite attempts to provide a comprehensive set of tools to view, edit and compile LaTeX documents in Vim. Together, they provide tools starting from macros to speed up editing LaTeX documents to functions for forward searching .dvi documents. Latex-Suite has been possible because of the contributions of many people. Please see latex-suite-credits for a list of people who have helped. Latex-Suite is released under the Vim charityware license. For license and conditions of use look at |copyright|. Replace all occurrences of ``Vim'' with ``Latex-Suite''. The current copyright holders of Latex-Suite are Srinath Avadhanula and Mikolaj Machowski. Homepage: http://vim-latex.sourceforge.net"></meta></head><body><div xml:lang="en" class="article" title="Latex-Suite Reference"><div class="titlepage"><div><div><h2 class="title"><a id="id488278"></a>Latex-Suite Reference</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Srinath</span> <span class="surname">Avadhanula</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:srinath AT fastmail DOT fm">srinathATfastmailDOTfm</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Mikolaj</span> <span class="surname">Machowski</span></h3><div class="affiliation"><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:mikmach AT wp DOT pl">mikmachATwpDOTpl</a>&gt;</code></p></div></div></div></div><div><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b></p><p>
    Latex-Suite attempts to provide a comprehensive set of tools to
    view, edit and compile LaTeX documents in Vim. Together, they
    provide tools starting from macros to speed up editing LaTeX
    documents to functions for forward searching .dvi documents.
    Latex-Suite has been possible because of the contributions of many
    people. Please see <a class="link" href="#latex-suite-credits" title="12 Credits">latex-suite-credits</a> for a list of
    people who have helped.
   </p><p>
    Latex-Suite is released under the Vim charityware license. For
    license and conditions of use look at |copyright|. Replace all
    occurrences of ``Vim'' with ``Latex-Suite''. The current copyright
    holders of Latex-Suite are Srinath Avadhanula and Mikolaj Machowski.
   </p><p>
    Homepage: <a class="ulink" href="http://vim-latex.sourceforge.net" target="_top">http://vim-latex.sourceforge.net</a>
   </p></div></div></div><hr></hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#recommended-settings">1 Installation and recommended Settings</a></span></dt><dt><span class="section"><a href="#latex-suite-templates">2 Inserting Templates</a></span></dt><dt><span class="section"><a href="#latex-macros">3 Latex-Suite Macros</a></span></dt><dd><dl><dt><span class="section"><a href="#environment-mappings">3.1 Environment Mappings</a></span></dt><dt><span class="section"><a href="#latex-command-maps">3.2 Command Mappings</a></span></dt><dt><span class="section"><a href="#font-maps">3.3 Font Mappings</a></span></dt><dt><span class="section"><a href="#section-mappings">3.4 Section Mappings</a></span></dt><dt><span class="section"><a href="#greek-letter-mappings">3.5 Greek Letter Mappings</a></span></dt><dt><span class="section"><a href="#auc-tex-mappings">3.6 Auc-Tex Key Bindings</a></span></dt><dt><span class="section"><a href="#diacritic-mappings">3.7 Diacritics</a></span></dt><dt><span class="section"><a href="#bibtex-bindings">3.8 BibTeX Shortcuts</a></span></dt><dt><span class="section"><a href="#smart-keys">3.9 Smart Key Mappings</a></span></dt><dt><span class="section"><a href="#altkey-mappings">3.10 Alt Key Macros</a></span></dt><dt><span class="section"><a href="#custom-macros-menu">3.11 Custom Macros</a></span></dt><dt><span class="section"><a href="#ls-new-macros">3.12 Making your own Macros via <code class="literal">IMAP()</code></a></span></dt></dl></dd><dt><span class="section"><a href="#latex-packages">4 Package Handling</a></span></dt><dd><dl><dt><span class="section"><a href="#inserting-packages">4.1 Inserting package commands</a></span></dt><dt><span class="section"><a href="#package-actions">4.2 Actions taken for supported packages</a></span></dt><dt><span class="section"><a href="#automatic-package-detection">4.3 Automatic Package detection</a></span></dt><dt><span class="section"><a href="#supporting-packages">4.4 Writing supporting for a package</a></span></dt></dl></dd><dt><span class="section"><a href="#latex-completion">5 Latex Completion</a></span></dt><dd><dl><dt><span class="section"><a href="#ls-completion-usage">5.1 Latex-Suite completion example</a></span></dt><dt><span class="section"><a href="#ls-completion-ref">5.2 Latex-Suite \ref completion</a></span></dt><dt><span class="section"><a href="#latex-completion-cite">5.3 Latex-Suite <code class="literal">\cite</code> completion</a></span></dt><dt><span class="section"><a href="#ls-filename-completion">5.4 Latex-Suite filename completion</a></span></dt><dt><span class="section"><a href="#ls-completion-custom">5.5 Custom command completion</a></span></dt></dl></dd><dt><span class="section"><a href="#latex-compiling">6 LaTeX Compiling</a></span></dt><dd><dl><dt><span class="section"><a href="#compiler-rules">6.1 Setting Compilation rules</a></span></dt><dt><span class="section"><a href="#compiler-dependency">6.2 Handling dependencies in compilation</a></span></dt><dt><span class="section"><a href="#compiling-multiple">6.3 Compiling multiple times</a></span></dt><dt><span class="section"><a href="#compiler-output-customization">6.4 Customizing the compiler output</a></span></dt><dt><span class="section"><a href="#part-compiling">6.5 Compiling parts of a file</a></span></dt></dl></dd><dt><span class="section"><a href="#latex-viewing">7 Latex Viewing and Searching</a></span></dt><dd><dl><dt><span class="section"><a href="#latex-viewing-rules">7.1 Setting Viewing rules</a></span></dt><dt><span class="section"><a href="#forward-searching">7.2 Forward Searching documents</a></span></dt><dt><span class="section"><a href="#inverse-searching">7.3 Inverse Searching</a></span></dt></dl></dd><dt><span class="section"><a href="#latex-folding">8 Latex Folding</a></span></dt><dd><dl><dt><span class="section"><a href="#default-folding">8.1 Default Folding Scheme in Latex-Suite</a></span></dt><dt><span class="section"><a href="#customizing-what-to-fold">8.2 Customizing what to fold</a></span></dt><dt><span class="section"><a href="#editing-folding">8.3 Editing the folding.vim file directly</a></span></dt></dl></dd><dt><span class="section"><a href="#latex-project">9 Multiple file LaTeX projects</a></span></dt><dd><dl><dt><span class="section"><a href="#latex-project-settings">9.1 Latex-Suite project settings</a></span></dt><dt><span class="section"><a href="#latex-master-file">9.2 Specifying which file to compile</a></span></dt></dl></dd><dt><span class="section"><a href="#latex-suite-commands-maps">10 Latex-Suite Commands and Maps</a></span></dt><dd><dl><dt><span class="section"><a href="#latex-suite-maps">10.1 Latex-Suite Maps</a></span></dt><dt><span class="section"><a href="#latex-suite-commands">10.2 Latex Suite Commands</a></span></dt></dl></dd><dt><span class="section"><a href="#customizing-latex-suite">11 Customizing Latex-Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#ls-general-purpose-settings">11.1 General Settings</a></span></dt><dt><span class="section"><a href="#customizing-place-holders">11.2 Place-Holder Customization</a></span></dt><dt><span class="section"><a href="#customizing-macros">11.3 Macro Customization</a></span></dt><dt><span class="section"><a href="#customizing-smart-keys">11.4 Smart Key Customization</a></span></dt><dt><span class="section"><a href="#customizing-latex-completion">11.5 Latex Completion Customization</a></span></dt><dt><span class="section"><a href="#customizing-compiling">11.6 Compiler Customization</a></span></dt><dt><span class="section"><a href="#customizing-viewing">11.7 Viewer Customization</a></span></dt><dt><span class="section"><a href="#customizing-menus">11.8 Menu Customization</a></span></dt><dt><span class="section"><a href="#customizing-folding">11.9 Folding Customization</a></span></dt><dt><span class="section"><a href="#customizing-packages">11.10 Package Handling Customization</a></span></dt></dl></dd><dt><span class="section"><a href="#latex-suite-credits">12 Credits</a></span></dt></dl></div><div class="section" title="1 Installation and recommended Settings"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="recommended-settings"></a>1 Installation and recommended Settings</h2></div></div></div><p>
   If you are reading this, it most probably means that you have already
   installed Latex-Suite and the help files. If this is not the case, follow the
   detailed instructions on <a class="ulink" href="http://vim-latex.sourceforge.net/index.php?subject=download" target="_top">Latex-Suite's
    download page</a>.
  </p><p>
   Make sure that you create a few necessary settings in your
   <code class="literal">~/.vimrc.</code>
   </p><pre class="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 always generate a file-name.
set grepprg=grep\ -nH\ $*

" OPTIONAL: This enables automatic indentation as you type.
filetype indent on

" OPTIONAL: Starting with Vim 7, the filetype of empty .tex files defaults to
" 'plaintex' instead of 'tex', which results in vim-latex not being loaded.
" The following changes the default filetype back to 'tex':
let g:tex_flavor='latex'
</pre><p>
  </p><p>
   In addition, the following settings could go in your ~/.vim/ftplugin/tex.vim
   file:
   </p><pre class="programlisting">" this is mostly a matter of taste. but LaTeX looks good with just a bit
" of indentation.
set sw=2
" TIP: if you write your \label's as \label{fig:something}, then if you
" type in \ref{fig: and press &lt;C-n&gt; you will automatically cycle through
" all the figure labels. Very useful!
set iskeyword+=:
</pre><p>
  </p></div><div class="section" title="2 Inserting Templates"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-suite-templates"></a>2 Inserting Templates</h2></div></div></div><p>
   This functionality is available via the <code class="literal">TeX-Suite &gt;
    Templates</code> menu.
   This module provides a way to insert custom templates at the beginning of the
   current file.
  </p><p>
   When Latex-Suite first starts up, it scans the
   <code class="literal">$VIM/ftplugin/latex-suite/templates/</code>
   directory and creates menu items based on the files found there. When
   you select a template from this menu, the file will be read in above
   the first line of the current file.
  </p><p>
   A template file can utilize placeholders for initializing the cursor
   position when the template is read in and subsequent movement. In
   addition, template files can contain dynamic elements such as the
   time of creation of a file etc, by using vim expressions.
  </p><p>
   You can place your own templates in the
   <code class="literal">$VIM/ftplugin/latex-suite/templates/</code> directory in
   order for them to be available via the menu. Unless Latex-Suite releases a
   template with the same name, these files should not get over-written
   when you install a new release over an existing one.
  </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    Templates are also accessible for non-gui users with the command
    |<code class="literal">:TTemplate</code>|. The argument should be name of
    the corresponding template file.  If the command is called
    without arguments (preferred usage), then a list of available
    templates is displayed and the user is asked to choose one of
    them.
   </p></div></div><div class="section" title="3 Latex-Suite Macros"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-macros"></a>3 Latex-Suite Macros</h2></div></div></div><p>
   Latex-Suite ships with a very comprehensive set of insert mode and
   |visual-mode| mappings and menu items to typeset most of the LaTeX
   elements.
  </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    These mappings are are not standard mappings in the sense that
    only the last character is mapped. See plugin/imaps.vim for
    further documentation. For example, in the case of the mapping
    <code class="literal">EFI</code> provided by Latex-Suite you can press the characters
    '<code class="literal">E</code>', '<code class="literal">F</code>' and '<code class="literal">I</code>'
    as slowly as you wish (unlike the normal <code class="literal">imap</code> command
    where <code class="literal">timeout</code> issues are involved). The characters are
    visible as you type them (unlike normal <code class="literal">imap</code>s) and you
    can use the movement or backspace key to correct yourself unlike normal
    mappings.
   </p></div><a id="place-holder"></a><div class="note" title="Place Holders" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title"><a id="place-holders"></a>Place Holders</h3><p>
    Almost all macros provided in Latex-Suite implement Stephen Riem's bracketing
    system and Gergely Kontra's <code class="literal">JumpFunc()</code> for handling
    place-holders. This consists of using "place-holders" to mark off
    locations where the next relevant editing has to be done. As an example,
    when you type <code class="literal">EFI</code> in |insert-mode|, you will get the
    following:
    </p><pre class="programlisting">\begin{figure}[h]
    \centerline{\psfig{figure=&lt;+eps file+&gt;}}
    \caption{&lt;+caption text+&gt;}
    \label{fig:&lt;+label+&gt;}
\end{figure}&lt;++&gt;</pre><p>
    The text <code class="literal">&lt;+eps file+&gt;</code> will be selected and
    you will be left in |select-mode| so that you can continue typing
    straight away. After having typed in the file name, you can press
    <code class="literal">&lt;Ctrl-J&gt;</code> (while still in insert-mode). This will
    take you directly to the next "place-holder". i.e, <code class="literal">&lt;+caption
     text+&gt;</code> will be visually selected with Vim in select mode
    again for typing in the caption. This saves on a lot of key presses.
   </p></div><div class="note" title="Over-riding Latex-Suite Macros" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title"><a id="overriding-macros"></a>Over-riding Latex-Suite Macros</h3><p>
    If you wish to change these macros from their default values, for
    example, if you wish to change <code class="literal">`w</code> to expand to
    <code class="literal">\omega</code> instead of its default expansion to
    <code class="literal">\wedge</code>, you should use the <code class="literal">IMAP</code>
    function as described in the <a class="link" href="#ls-new-macros" title="3.12 Making your own Macros via IMAP()">Using 
     IMAP()</a> section.
   </p><p>
    An important thing to note is that if you wish to over-ride macros
    created by Latex-Suite rather than merely create new macros, you should place
    the <code class="literal">IMAP()</code> calls in a script which gets sourced
    after the files in Latex-Suite. A good place typically is as a file-type
    plugin file in the
    <code class="literal">~/.vim/after/ftplugin/</code> directory. (Use
    <code class="literal">~/vimfiles</code> if you are using
    <code class="literal">WINDOWS</code>). For example to over-ride
    <code class="literal">`w</code> to <code class="literal">\omega</code> instead of
    <code class="literal">\wedge</code>, place the following line in (say)
    <code class="literal">~/.vim/after/ftplugin/tex_macros.vim</code>:
    </p><pre class="programlisting">call IMAP('`w', '\omega', 'tex')</pre><p>
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     It is important to use a file-name which will get sourced on a
     <code class="literal">FileType</code> event. Therefore you must use a file-name
     which conforms to the standards as described in
     <code class="literal">|ftplugin-name|</code>.
    </p></div></div><div class="note" title="Pausing Macro expansion" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title"><a id="pausing-imaps"></a>Pausing Macro expansion</h3><p>
    If you wish to temporarily suspend the imaps functionality, then you
    can set the <code class="literal">Imap_FreezeImap</code> to 1. If you set
    <code class="literal">g:Imap_FreezeImap</code> to 1, then it will be a
    system-wide setting. Setting <code class="literal">b:Imap_FreezeImap</code> will
    affect only the current buffer.
   </p></div><p>
   The following sections describe the various editing macros provided
   by Latex-Suite.
  </p><div class="section" title="3.1 Environment Mappings"><div class="titlepage"><div><div><h3 class="title"><a id="environment-mappings"></a>3.1 Environment Mappings</h3></div></div></div>
   Latex-Suite provides a rich set of mappings to insert, enclose and modify
   LaTeX environments, i.e, <code class="literal">\begin{...} ... \end{...}</code>
   pairs.
   <div class="section" title="3.1.1 Inserting Environments"><div class="titlepage"><div><div><h4 class="title"><a id="inserting-environments"></a>3.1.1 Inserting Environments</h4></div></div></div><p>
     Latex-Suite provides the following ways to insert environments
    </p><div class="section" title="3.1.1.1 Method 1: Pressing &lt;F5&gt;"><div class="titlepage"><div><div><h5 class="title"><a id="inserting-env-f5"></a>3.1.1.1 Method 1: Pressing <code class="literal">&lt;F5&gt;</code></h5></div></div></div><p>
      If you press <code class="literal">&lt;F5&gt;</code> in the insert or normal
      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.  If you press
      <code class="literal">&lt;F5&gt;</code> on a line which already has a word,
      then that word is used instead of prompting.
     </p><p>
      See <a class="link" href="#Tex_Env_name" title="11.3.1 Tex_Env_name">Tex_Env_name</a> for a
      description of how Latex-Suite uses the word to form the expansion and how
      to modify Latex-Suite's behavior.
     </p><p>
      The list of environments which Latex-Suite prompts you with (when
      <code class="literal">&lt;F5&gt;</code> is pressed on an empty line) is formed
      from the <a class="link" href="#Tex_PromptedEnvironments" title="11.3.10 g:Tex_PromptedEnvironments">Tex_PromptedEnvironments</a>
      setting.
     </p><p>
      In addition to this setting, Latex-Suite also lists environments found in
      custom packages as described in the section <a class="link" href="#package-actions" title="4.2 Actions taken for supported packages">Package actions.</a>
     </p></div><div class="section" title="3.1.1.2 Method 2: Using &lt;S-F1&gt;-&lt;S-F4&gt;"><div class="titlepage"><div><div><h5 class="title"><a id="inserting-env-shift-f1"></a>3.1.1.2 Method 2: Using <code class="literal">&lt;S-F1&gt;</code>-<code class="literal">&lt;S-F4&gt;</code></h5></div></div></div><p>
      The shifted function keys, <code class="literal">&lt;S-F1&gt;</code> to
      <code class="literal">&lt;S-F4&gt;</code> can be mapped to insert very commonly
      used environments. The environments mapped to each key can be
      customized via the <a class="link" href="#Tex_HotKeyMappings" title="11.3.11 g:Tex_HotKeyMappings">g:Tex_HotKeyMappings</a> setting.
     </p></div><div class="section" title="3.1.1.3 Method 3: Using three letter sequences"><div class="titlepage"><div><div><h5 class="title"><a id="inserting-env-threeletter"></a>3.1.1.3 Method 3: Using three letter sequences</h5></div></div></div><p>
      Environments can also be inserted by pressing a 3 capital letter
      sequence starting with an <code class="literal">E</code>. The sequence of 3
      letters generally tries to follow the following rules:
     </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
       All environment mappings begin with <code class="literal">E</code></li><li class="listitem">
       If the environment can be broken up into 2 distinct words,
       such as flushright (flush + right), then the next 2 letters
       are the first letters of the 2 words.  Example:
       <pre class="programlisting">flushleft  (_f_lush + _l_eft)  ---&gt; EFL
flushright (_f_lush + _r_ight) ---&gt; EFR
eqnarray   (_e_qn + _a_rray)   ---&gt; EEA</pre>
       If on the other hand, the environment name cannot be broken
       up into 2 distinct words, then the next 2 letters are the
       first 2 letters of the name of the environment.
       Example:
       <pre class="programlisting">equation (_eq_uation)          ---&gt; EEQ</pre></li></ol></div><p>
      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:
      </p><pre class="programlisting">quote     (_q_uot_e_)          ---&gt; EQE
quotation (_q_uotatio_n_)      ---&gt; EQN</pre><p>
      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.
     </p></div></div><div class="section" title="3.1.2 Enclosing in Environments"><div class="titlepage"><div><div><h4 class="title"><a id="enclosing-environments"></a>3.1.2 Enclosing in Environments</h4></div></div></div><p>
     Latex-Suite provides visual-mode mappings which enclose visually
     selected portions of text in environments. There are two ways provided
     to do this.
    </p><div class="section" title="3.1.2.1 Method 1: Pressing &lt;F5&gt;"><div class="titlepage"><div><div><h5 class="title"><a id="enclosing-env-f5"></a>3.1.2.1 Method 1: Pressing <code class="literal">&lt;F5&gt;</code></h5></div></div></div><p>
      You can also select a portion of text visually and press
      <code class="literal">&lt;F5&gt;</code> while still in visual mode. This will
      prompt you with a list of environments. (This list can be customized
      via the <a class="link" href="#Tex_PromptedEnvironments" title="11.3.10 g:Tex_PromptedEnvironments">g:Tex_PromptedEnvironments</a>
      setting). You can either choose from this list or type in a new
      environment name. Once the selection is done, Latex-Suite encloses the
      visually selected portion in the chosen environment.
     </p></div><div class="section" title="3.1.2.2 Method 2: Using three letter mappings"><div class="titlepage"><div><div><h5 class="title"><a id="enclosing-env-threeletter"></a>3.1.2.2 Method 2: Using three letter mappings</h5></div></div></div><p>
      You can also select text visually and press a sequence of three
      characters beginning with <code class="literal">,</code> (the single comma
      character) and the selected text will be enclosed in the chosen
      environment. The three letter sequence follows directly from the
      three letter sequence used to insert environments as described <a class="link" href="#inserting-env-threeletter" title="3.1.1.3 Method 3: Using three letter sequences">here</a>. The following
      example describes the rule used:
     </p><p>
      If <code class="literal">ECE</code> inserts a
      <code class="literal">\begin{center}...\end{center}</code> environment, then to
      enclose a block of selected text in
      <code class="literal">\begin{center}...\end{center}</code>, simply select the
      text and press <code class="literal">,ce</code>.  The rule simply says that the
      leading <code class="literal">E</code> is converted to <code class="literal">,</code> and
      the next 2 letters are small case.  
     </p></div><p>
     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 <code class="literal">,ce</code>, then you get
     <code class="literal">\centerline{word}</code>, whereas if you press
     <code class="literal">,ce</code> on a line-wise selection, you get:
     </p><pre class="programlisting">\begin{center}
    line
\end{center}</pre><p>
    </p></div><div class="section" title="3.1.3 Changing Environments"><div class="titlepage"><div><div><h4 class="title"><a id="changing-environments"></a>3.1.3 Changing Environments</h4></div></div></div><p>
     Pressing <code class="literal">&lt;S-F5&gt;</code> 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:
     </p><pre class="programlisting">\begin{eqnarray}
  \begin{array}{ccc}
    2 &amp; 3 &amp; 4
  \end{array}
\end{eqnarray}</pre><p>
     if you are located in the middle "2 &amp; 3 &amp; 4" line, then pressing
     <code class="literal">&lt;S-F5&gt;</code> 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
     <code class="literal">eqnarray</code> environment with a
     <code class="literal">\label</code> command, then changing it to an
     <code class="literal">eqnarray*</code> environment will delete the
     <code class="literal">\label</code>.
    </p><p>
     Pressing <code class="literal">&lt;F5&gt;</code> in normal mode has the same
     effect as pressing <code class="literal">&lt;F5&gt;</code> in insert-mode,
     namely you will be prompted to choose an environment to insert.
    </p></div></div><div class="section" title="3.2 Command Mappings"><div class="titlepage"><div><div><h3 class="title"><a id="latex-command-maps"></a>3.2 Command Mappings</h3></div></div></div>
   Latex-Suite provides a rich set of mappings to insert, enclose and modify
   LaTeX commands.
   <div class="section" title="3.2.1 Inserting LaTeX commands"><div class="titlepage"><div><div><h4 class="title"><a id="inserting-commands"></a>3.2.1 Inserting LaTeX commands</h4></div></div></div><a id="ls-imap-f7"></a><a id="ls-imap-s-f7"></a><p>
     Pressing <code class="literal">&lt;F7&gt;</code> in insert or normal mode while
     the cursor is touching a word will insert a command formed from the
     word touching the cursor. 
    </p><p>
     For certain common commands, Latex-Suite will expand them to include
     additional arguments as needed. For example, <code class="literal">frac</code>
     becomes <code class="literal">\frac{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt;</code>. Otherwise, it will
     simply change the word under the cursor as follows 
     </p><pre class="programlisting">word --&gt; \word{&lt;++&gt;}&lt;++&gt;</pre><p> 
     You can define custom expansions
     of commands using the <code class="literal">Tex_Com_{name}</code> setting as
     described in <a class="link" href="#Tex_Com_name" title="11.3.2 Tex_Com_name">here</a>.
    </p><p>
     If <code class="literal">&lt;F7&gt;</code> is pressed when the cursor is on
     white-space, then Latex-Suite will prompt you to choose a command and insert
     that instead.The list of commands is constructed from the <a class="link" href="#Tex_PromptedCommands" title="11.3.12 g:Tex_PromptedCommands"><code class="literal">g:Tex_PromptedCommands</code></a>
     setting and also from commands which Latex-Suite finds while scanning custom
     packages which Latex-Suite finds. See the <a class="link" href="#package-actions" title="4.2 Actions taken for supported packages">Package actions</a> section for details
     on which files are scanned etc.
    </p></div><div class="section" title="3.2.2 Enclosing in a command"><div class="titlepage"><div><div><h4 class="title"><a id="enclosing-commands"></a>3.2.2 Enclosing in a command</h4></div></div></div><p>
     You can select a portion of text visually and press
     <code class="literal">&lt;F7&gt;</code> while still in visual mode. This will
     prompt you with a list of commands. (This list can be customized
     via the <a class="link" href="#Tex_PromptedCommands" title="11.3.12 g:Tex_PromptedCommands">g:Tex_PromptedCommands</a>
     setting). You can either choose from this list or type in a new
     command name. Once the selection is done, Latex-Suite encloses the
     visually selected portion in the chosen command.
    </p></div><div class="section" title="3.2.3 Changing commands"><div class="titlepage"><div><div><h4 class="title"><a id="changing-commands"></a>3.2.3 Changing commands</h4></div></div></div><a id="ls-vmap-f7"></a><p>
     In both insert and normal mode <code class="literal">&lt;S-F7&gt;</code> will
     find out if you are presently within an environment and then prompt you
     with a list of commands to change it to.
    </p></div></div><div class="section" title="3.3 Font Mappings"><div class="titlepage"><div><div><h3 class="title"><a id="font-maps"></a>3.3 Font Mappings</h3></div></div></div><p>
    These mappings insert font descriptions such as:
    <code class="literal">\textsf{&lt;++&gt;}&lt;++&gt;</code>
    with the cursor left in place of the first <a class="link" href="#place-holders" title="Place Holders">placeholder</a> (the &lt;++&gt; characters).
   </p><p>
    Mnemonic:
    </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">first letter is always F (F for font)</li><li class="listitem">next 2 letters are the 2 letters describing the font.</li></ol></div><p>
   </p><p>
    Example: Typing <code class="literal">FEM</code> in insert-mode expands to
    <code class="literal">\emph{&lt;++&gt;}&lt;++&gt;</code>.
   </p><p>
    Just like environment mappings, you can visually select an area and press
    <code class="literal">`sf</code> to have it enclosed in:
    <code class="literal">\textsf{word}</code>
    or
    </p><pre class="programlisting">{\sffamily
line
}</pre><p>
    depending on character-wise or line-wise selection.
   </p></div><div class="section" title="3.4 Section Mappings"><div class="titlepage"><div><div><h3 class="title"><a id="section-mappings"></a>3.4 Section Mappings</h3></div></div></div><p>
    These maps insert LaTeX sections such as:
    </p><pre class="programlisting">\section{&lt;++&gt;}&lt;++&gt;</pre><p>
    etc. Just as in the case of environments and fonts, can be enclosed with a
    visual selection. The enclosing is not sensitive to character or line-wise
    selection.
   </p><p>
    Mnemonic: (make your own!)
    </p><pre class="programlisting">SPA for part
SCH for chapter
SSE for section
SSS for subsection
SS2 for subsubsection
SPG for paragraph
SSP for subparagraph</pre><p>
   </p><p>
    Example:
    SSE in insert mode inserts
    </p><pre class="programlisting">\section{&lt;++&gt;}&lt;++&gt;</pre><p>
    If you select a word or line and press <code class="literal">,se</code>, then you
    get
    </p><pre class="programlisting">\section{section name}</pre><p>
    The menu item in Tex-Environments.Sections have a sub-menu called
    'Advanced'. Choosing an item from this sub-menu asks a couple of questions
    (whether you want to include the section in the table of contents, whether
    there is a shorter name for the table of contents) and then creates a more
    intelligent template.
   </p></div><div class="section" title="3.5 Greek Letter Mappings"><div class="titlepage"><div><div><h3 class="title"><a id="greek-letter-mappings"></a>3.5 Greek Letter Mappings</h3></div></div></div><p>
    Lower case
   </p><code class="literal">`a</code>   through <code class="literal">`z</code> expand to
   <code class="literal">\alpha</code> through <code class="literal">\zeta</code>.
   <p>
    Upper case:
   </p><pre class="programlisting">`D = \Delta
`F = \Phi
`G = \Gamma
`Q = \Theta
`L = \Lambda
`X = \Xi
`Y = \Psi
`S = \Sigma
`U = \Upsilon
`W = \Omega</pre><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>LaTeX does not support upper case for all greek alphabets.</p></div><p>Just like other Latex-Suite mappings, these mappings are not created using
    the standard <code class="literal">imap</code> command. Thus you can type slowly,
    correct using <code class="literal">&lt;BS&gt;</code> etc.</p></div><div class="section" title="3.6 Auc-Tex Key Bindings"><div class="titlepage"><div><div><h3 class="title"><a id="auc-tex-mappings"></a>3.6 Auc-Tex Key Bindings</h3></div></div></div><p>
    These are simple 2 key expansions for some very commonly used LaTeX
    elements:
   </p><pre class="programlisting">`^   Expands To   \Hat{&lt;++&gt;}&lt;++&gt;
`_   expands to   \bar{&lt;++&gt;}&lt;++&gt;
`6   expands to   \partial
`8   expands to   \infty
`/   expands to   \frac{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt;
`%   expands to   \frac{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt;
`@   expands to   \circ
`0   expands to   ^\circ
`=   expands to   \equiv
`\   expands to   \setminus
`.   expands to   \cdot
`*   expands to   \times
`&amp;   expands to   \wedge
`-   expands to   \bigcap
`+   expands to   \bigcup
`(   expands to   \subset
`)   expands to   \supset
`&lt;   expands to   \le
`&gt;   expands to   \ge
`,   expands to   \nonumber
`~   expands to   \tilde{&lt;++&gt;}&lt;++&gt;
`;   expands to   \dot{&lt;++&gt;}&lt;++&gt;
`:   expands to   \ddot{&lt;++&gt;}&lt;++&gt;
`2   expands to   \sqrt{&lt;++&gt;}&lt;++&gt;
`|   expands to   \Big|
`I   expands to   \int_{&lt;++&gt;}^{&lt;++&gt;}&lt;++&gt;</pre><p>
    (again, notice the convenient place-holders)
   </p><p>
    In addition the visual mode macros are provided:
   </p><pre class="programlisting">`(  encloses selection in \left( and \right)
`[  encloses selection in \left[ and \right]
`{  encloses selection in \left\{ and \right\}
`$  encloses selection in $$ or \[ \] depending on characterwise or
                                      linewise selection</pre></div><div class="section" title="3.7 Diacritics"><div class="titlepage"><div><div><h3 class="title"><a id="diacritic-mappings"></a>3.7 Diacritics</h3></div></div></div><p>
    These mappings speed up typing European languages which contain diacritic
    characters such as a-umlaut etc. 
    </p><pre class="programlisting">+&lt;l&gt;     expands to \v{&lt;l&gt;}
=&lt;l&gt;     expands to \'{&lt;l&gt;}</pre><p>
    where <code class="literal">&lt;l&gt;</code> is an alphabet.
   </p><pre class="programlisting">+}       expands to \"{a}
+:       expands to \^{o}</pre><p>
    Latex-Suite also ships with <a class="link" href="#smart-backspace">smart
     backspacing</a> functionality which provides another convenience while
    editing languages with diacritics.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Diacritics are disabled by default in Latex-Suite because they can
     sometimes be a little too intrusive. Moreover, most European users can
     nowadays use font encodings which display diacritic characters directly
     instead of having to rely on Latex-Suite's method of displaying diacritics.</p><p>Set the <a class="link" href="#Tex_Diacritics" title="11.3.7 g:Tex_Diacritics">g:Tex_Diacritics</a>
     variable to enable diacritics.</p></div></div><div class="section" title="3.8 BibTeX Shortcuts"><div class="titlepage"><div><div><h3 class="title"><a id="bibtex-bindings"></a>3.8 BibTeX Shortcuts</h3></div></div></div><p>
    Latex-Suite provides an easy way of entering bibliographic entries. Four
    insert-mode mappings: <code class="literal">BBB</code>, <code class="literal">BBL</code>,
    <code class="literal">BBH</code> and <code class="literal">BBX</code> are provided, all of
    which essentially act in the same manner. When you type any of these in
    insert-mode, you will get a prompt asking you to choose a entry type
    for the bibliographic entry.
   </p><p>
    When you choose an entry type, a bibliographic entry template will be
    inserted. For example, if you choose the option
    <code class="literal">'book'</code> via the map <code class="literal">BBB</code>, then
    the following template will be inserted:
    </p><pre class="programlisting">@BOOK{&lt;+key+&gt;,
    author = {&lt;++&gt;},
    editor = {&lt;++&gt;},
    title = {&lt;++&gt;},
    publisher = {&lt;++&gt;},
    year = {&lt;++&gt;},
    otherinfo = {&lt;++&gt;}
}&lt;++&gt;</pre><p>
   </p><p>
    <code class="literal">&lt;+key+&gt;</code> will be highlighted in select-mode and
    you can type in the bib-key. After that you can use
    <code class="literal">&lt;Ctrl-J&gt;</code> to navigate to successive locations
    in the template and enter new values.
   </p><p>
    <code class="literal">BBB</code> inserts a template with only the fields
    mandatorily required for a given entry type. <code class="literal">BBL</code>
    inserts a template with commonly used extra options.
    <code class="literal">BBH</code> inserts a template with more options which are
    not as commonly used. <code class="literal">BBX</code> inserts a template with
    all the fields which the entry type supports.
   </p><div class="note" title="Mnemonic" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Mnemonic</h3><p>
     <code class="literal">B</code> for Bibliographic entry, <code class="literal">L</code>
     for Large entry, <code class="literal">H</code> for Huge entry, and
     <code class="literal">X</code> stands for all eXtras.
    </p></div><div class="section" title="3.8.1 Customizing Bib-TeX fields"><div class="titlepage"><div><div><h4 class="title"><a id="adding-bib-options"></a>3.8.1 Customizing Bib-TeX fields</h4></div></div></div><p>
     If you wish the <code class="literal">BBB</code> command to insert a few
     additional fields in addition to the fields it creates, then you will
     need to define global variables of the form
     </p><pre class="programlisting">g:Bib_{type}_options</pre><p>
     in you <code class="literal">$VIM/ftplugin/bib.vim</code> file, where
     <code class="literal">{type}</code> is a string like
     <code class="literal">'article'</code>, <code class="literal">'book'</code> etc. This
     variable should contain one of the letters defined in the following
     table
    </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Character</th><th>Field Type</th></tr></thead><tbody><tr><td>w</td><td>address</td></tr><tr><td>a</td><td>author</td></tr><tr><td>b</td><td>booktitle</td></tr><tr><td>c</td><td>chapter</td></tr><tr><td>d</td><td>edition</td></tr><tr><td>e</td><td>editor</td></tr><tr><td>h</td><td>howpublished</td></tr><tr><td>i</td><td>institution</td></tr><tr><td>k</td><td>isbn</td></tr><tr><td>j</td><td>journal</td></tr><tr><td>m</td><td>month</td></tr><tr><td>z</td><td>note</td></tr><tr><td>n</td><td>number</td></tr><tr><td>o</td><td>organization</td></tr><tr><td>p</td><td>pages</td></tr><tr><td>q</td><td>publisher</td></tr><tr><td>r</td><td>school</td></tr><tr><td>s</td><td>series</td></tr><tr><td>t</td><td>title</td></tr><tr><td>u</td><td>type</td></tr><tr><td>v</td><td>volume</td></tr><tr><td>y</td><td>year</td></tr></tbody></table></div><p>
     For example, by default, choosing <code class="literal">'article'</code> via
     <code class="literal">BBB</code> inserts the following template by default
     </p><pre class="programlisting">@ARTICLE{&lt;+key+&gt;,
    author = {&lt;++&gt;},
    title = {&lt;++&gt;},
    journal = {&lt;++&gt;},
    year = {&lt;++&gt;},
    otherinfo = {&lt;++&gt;}
}&lt;++&gt;</pre><p>
     However, if <code class="literal">g:Bib_article_options</code> is defined as
     <code class="literal">'mnp'</code>, then <code class="literal">'article'</code> will
     insert the following template
     </p><pre class="programlisting">@ARTICLE{&lt;+key+&gt;,
    author = {&lt;++&gt;},
    title = {&lt;++&gt;},
    journal = {&lt;++&gt;},
    year = {&lt;++&gt;},
    month = {&lt;++&gt;},
    number = {&lt;++&gt;},
    pages = {&lt;++&gt;},
    otherinfo = {&lt;++&gt;}
}&lt;++&gt;</pre><p>
    </p><p>
     If you have some other fields you wish to associate with an article
     which are not listed above, then you will have to use the
     <code class="literal">Bib_{type}_extrafields</code> option. This is a newline
     separated string of complete field names which will be included in the
     template. For example, if you define
     </p><pre class="programlisting">let g:Bib_article_extrafields = "crossref\nabstract"</pre><p>
     then the article template will include the lines
     </p><pre class="programlisting">crossref = {&lt;++&gt;},
abstract = {&lt;++&gt;},</pre><p>
    </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      You will need to define <code class="literal">Bib_*</code> settings in your
      <code class="literal">$VIMRUNTIME/ftplugin/bib.vim</code> file.
     </p></div></div></div><div class="section" title="3.9 Smart Key Mappings"><div class="titlepage"><div><div><h3 class="title"><a id="smart-keys"></a>3.9 Smart Key Mappings</h3></div></div></div><p>
    Latex-Suite ships with the following smart keys:
   </p><p title="Smart Backspace"><a id="smart-backspace"></a><b>Smart Backspace.</b>
    Pressing <code class="literal">&lt;BS&gt;</code> in insert mode checks to see
    whether we are just after something like <code class="literal">\'{a}</code> and
    if so, deletes all of it. i.e, diacritics are treated as single
    characters for backspacing.
   </p><p title="Smart Quotes"><b>Smart Quotes.</b>
    Pressing <code class="literal">"</code> (English double quote) will insert
    <code class="literal">``</code> or <code class="literal">''</code> by making an
    intelligent guess about whether we intended to open or close a quote.
   </p><p title="Smart Space"><b>Smart Space.</b>
    Latex-Suite maps the <code class="literal">&lt;space&gt;</code> key in such a
    way that $ characters are not broken across lines. It does this by
    first setting <code class="literal">tw=0</code> so that Vim will not
    automatically break lines and then maps the
    <code class="literal">&lt;space&gt;</code> key to insert newlines keeping
    <code class="literal">$$</code>'s on the same line.
   </p><p title="Smart Dots"><b>Smart Dots.</b>
    Pressing <code class="literal">...</code> (3 dots) results in
    <code class="literal">\ldots</code> outside math mode and
    <code class="literal">\cdots</code> in math mode.
   </p></div><div class="section" title="3.10 Alt Key Macros"><div class="titlepage"><div><div><h3 class="title"><a id="altkey-mappings"></a>3.10 Alt Key Macros</h3></div></div></div><p>
    Latex-Suite utilizes a set of macros originally created by Carl Mueller in
    auctex.vim to make inserting all the <code class="literal">\left ... \right</code>
    stuff very easy and to also make some use of the heavily under-utilized
    <code class="literal">&lt;Alt&gt;</code> key. 
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     By default, typing <code class="literal">Alt-&lt;key&gt;</code> in Vim takes
     focus to the menu bar if a menu with the hotkey
     <code class="literal">&lt;key&gt;</code> exists. If in your case, there are
     conflicts due to this behavior, you will need to set
     </p><pre class="programlisting">set winaltkeys=no</pre><p>
     in your <code class="literal">$VIM/ftplugin/tex.vim</code> in order to use these
     maps.
    </p></div><div class="note" title="Customizing the maps" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Customizing the maps</h3><p>
     If for some reason, you wish to not map the
     <code class="literal">&lt;Alt&gt;</code> keys, (some European users need to use
     the <code class="literal">&lt;Alt&gt;</code> key to enter diacritics), you can
     change these maps to other keys as described in the section <a class="link" href="#customize-alt-key-maps" title="10.1.2 Alt-Key mappings">Customizing Alt-key maps</a>.
    </p></div><div class="section" title="3.10.1 &lt;Alt-L&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="Alt-L"></a>3.10.1 <code class="literal">&lt;Alt-L&gt;</code></h4></div></div></div><p>
     This is a polymorphic insert-mode mapping which expands to one of the
     following depending on the character just before the cursor location.
    </p><div class="informaltable"><table border="1"><colgroup><col width="0.5in" align="cener"></col><col width="0.5in"></col></colgroup><thead><tr><th align="cener">Character before cursor</th><th>Expansion</th></tr></thead><tbody><tr><td align="cener">(</td><td><code class="literal">\left( &lt;++&gt; \right)</code></td></tr><tr><td align="cener">[</td><td><code class="literal">\left[ &lt;++&gt; \right]</code></td></tr><tr><td align="cener">|</td><td><code class="literal">\left| &lt;++&gt; \right|</code></td></tr><tr><td align="cener">{</td><td><code class="literal">\left\{ &lt;++&gt; \right\}</code></td></tr><tr><td align="cener">&lt;</td><td><code class="literal">\langle &lt;++&gt; \rangle</code></td></tr><tr><td align="cener">q</td><td><code class="literal">\lefteqn{&lt;++&gt;}&lt;++&gt;</code></td></tr></tbody></table></div><p>
     If the character before the cursor is none of the above, then it will
     simply insert a <code class="literal">\label{&lt;++&gt;}&lt;++&gt;</code>.
    </p></div><div class="section" title="3.10.2 &lt;Alt-B&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="Alt-B"></a>3.10.2 <code class="literal">&lt;Alt-B&gt;</code></h4></div></div></div><p>
     This insert-mode mapping encloses the previous character in
     <code class="literal">\mathbf{}</code>.
    </p></div><div class="section" title="3.10.3 &lt;Alt-C&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="Alt-C"></a>3.10.3 <code class="literal">&lt;Alt-C&gt;</code></h4></div></div></div><p>
     In insert mode, this key is polymorphic as follows:
    </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
      If the previous character is a letter or number, then capitalize it and
      enclose it in <code class="literal">\mathcal{}</code>.
     </li><li class="listitem">
      otherwise insert <code class="literal">\cite{}</code>.
     </li></ol></div><p>
     In visual mode, it will simply enclose the selection in
     <code class="literal">\mathcal{}</code>
    </p></div><div class="section" title="3.10.4 &lt;Alt-I&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="Alt-I"></a>3.10.4 <code class="literal">&lt;Alt-I&gt;</code></h4></div></div></div><p>
     This mapping inserts an <code class="literal">\item</code> command at the
     current cursor location depending on which environment the cursor is
     enclosed in. The style of the <code class="literal">\item</code> command is
     dependent on the enclosing environment. By default,
     <code class="literal">&lt;Alt-I&gt;</code> has styles defined forthe following
     environments:
    </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Environment</th><th>Style</th></tr></thead><tbody><tr><td>itemize</td><td>\item </td></tr><tr><td>enumerate</td><td>\item </td></tr><tr><td>theindex</td><td>\item </td></tr><tr><td>thebibliography</td><td>\item[&lt;+biblabel+&gt;]{&lt;+bibkey+&gt;} &lt;++&gt;</td></tr><tr><td>description</td><td>\item[&lt;+label+&gt;] &lt;++&gt;</td></tr></tbody></table></div><p>
     <code class="literal">&lt;Alt-I&gt;</code> is intelligent enough to
     account for nested environments. For example,
     </p><pre class="programlisting">\begin{itemize}
    \item first item
    \item second item
          \begin{description}
              \item[label1] first desc
              \item[label2] second
              % &lt;Alt-I&gt; will insert "\item[&lt;+label+&gt;] &lt;++&gt;" if
              % used here
          \end{description}
    \item third item
    % &lt;Alt-I&gt; will insert "\item " when if used here.
\end{itemize}
% &lt;Alt-I&gt; will insert nothing ("") if used here</pre><p>
     </p><p>
     The style used by <code class="literal">&lt;Alt-I&gt;</code> can be customized
     using the <a class="link" href="#Tex_ItemStyle_environment" title="11.3.13 Tex_ItemStyle_environment"><code class="literal">g:Tex_ItemStyle_environment</code></a>
     variable.
    </p></div></div><div class="section" title="3.11 Custom Macros"><div class="titlepage"><div><div><h3 class="title"><a id="custom-macros-menu"></a>3.11 Custom Macros</h3></div></div></div><p>
    This functionality available via the TeX-Suite.Macros menu, provides
    a way of inserting customized macros into the current file via the
    menu.
   </p><p>
    When Latex-Suite starts up, it scans the
    <code class="literal">$VIM/ftplugin/latex-suite/macros/</code> directory and
    creates a menu from the files found there. Each file is considered as
    a single macro. You can place your own macros in this directory,
    using <a class="link" href="#place-holders" title="Place Holders">placeholders</a> if wanted.
   </p><p>
    When you choose a macro from the menu, the corresponding file is read
    into the current buffer after the current cursor position. In non-gui
    mode, you can use the |TMacro| command instead of choosing from the
    menu. This command takes the macro file name as an argument. When
    called without arguments (preferred usage), then a list of available
    macro files is displayed and the user is prompted to choose one of
    them).
   </p><p>
    There are some other tools provided in this menu, namely:
   </p><div class="informaltable"><table border="0"><colgroup><col width="0.5in"></col><col width="0.5in"></col></colgroup><tbody><tr><td>{New}</td><td>
        Creates a new (unnamed) buffer in the
        latex-suite/macros/ directory.  Use the command
        :TexMacroNew in non-gui mode.
       </td></tr><tr><td>{Edit}</td><td>
        Opens up the corresponding macro file for editing. Use
        |:TexMacroEdit| in non-gui mode. When you try to edit {macro}
        not from local directory Latex-Suite will copy it to your local
        directory with suffix "-local". If local copy already exists
        Latex-Suite prompt for overwriting it.
       </td></tr><tr><td>{Delete}</td><td>
        Deletes the corresponding macro. Use the prefixed numbers for
        fast navigation of menus. Use |:TexMacroDelete| in non-gui mode.
        When you choose to delete {macro} which is not in your local
        directory Latex-Suite will refuse to delete it.
       </td></tr><tr><td>{Redraw}</td><td>
        Rescans the macros/ directories and refreshes the macros list.
       </td></tr></tbody></table></div></div><div class="section" title="3.12 Making your own Macros via IMAP()"><div class="titlepage"><div><div><h3 class="title"><a id="ls-new-macros"></a>3.12 Making your own Macros via <code class="literal">IMAP()</code></h3></div></div></div><p>
    If you find the need to create your own macros, then you can use the
    <code class="literal">IMAP()</code> function provided with Latex-Suite. See <a class="link" href="#why-IMAP" title="3.12.1 Why use IMAP()">Why use <code class="literal">IMAP()</code></a> for a short
    explanation of why you might prefer <code class="literal">IMAP()</code> over
    Vim's standard <code class="literal">:imap</code> command. An example best
    explains the usage:
    </p><pre class="programlisting">:call IMAP('NOM', '\nomenclature{&lt;++&gt;}&lt;++&gt;', 'tex')</pre><p>
    This will create a Latex-Suite-style mapping, where if you type
    <code class="literal">NOM</code> in insert mode, you will get
    <code class="literal">\nomenclature{&lt;++&gt;}&lt;++&gt;</code> with the cursor left in
    place of the first <code class="literal">&lt;++&gt;</code> characters. See <a class="link" href="#ls-imaps-syntax" title="3.12.2 IMAP() syntax">IMAP() syntax</a> for
    a detailed explanation of the <code class="literal">IMAP()</code> command.
   </p><p>
    For maps which are triggered for a given filetype, the
    <code class="literal">IMAP()</code> command above should be put in the filetype
    plugin script for that file. For example, for tex-specific mappings,
    the <code class="literal">IMAP()</code> calls should go in
    <code class="literal">$VIM/ftplugin/tex.vim</code>. For globally visible maps,
    you will need to use the following in either your
    <code class="literal">~/.vimrc</code> or a file in your
    <code class="literal">$VIM/plugin</code> directory.
    </p><pre class="programlisting">augroup MyIMAPs
    au!
    au VimEnter * call IMAP('Foo', 'foo', '')
augroup END</pre><p>
   </p><div class="section" title="3.12.1 Why use IMAP()"><div class="titlepage"><div><div><h4 class="title"><a id="why-IMAP"></a>3.12.1 Why use <code class="literal">IMAP()</code></h4></div></div></div><p>
     Using <code class="literal">IMAP</code> instead of Vim's built-in
     <code class="literal">:imap</code> command has a couple of advantages:
     </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
       The 'ttimeout' option will generally limit how easily you can type
       the left hand side for a normal <code class="literal">:imap</code>. if you type
       the left hand side too slowly, then the mapping will not be
       activated.
      </li><li class="listitem">
       If you mistype one of the letters of the lhs, then the mapping is
       deactivated as soon as you backspace to correct the mistake.
      </li><li class="listitem">
       The characters in lhs are shown on top of each other. This is fairly
       distracting. This becomes a real annoyance when a lot of characters
       initiate mappings.
      </li></ol></div><p>
    </p></div><div class="section" title="3.12.2 IMAP() syntax"><div class="titlepage"><div><div><h4 class="title"><a id="ls-imaps-syntax"></a>3.12.2 IMAP() syntax</h4></div></div></div><p>
     Formally, the syntax which is used for the <code class="literal">IMAP</code>
     function is:
     </p><pre class="programlisting">call IMAP (lhs, rhs, ft [, phs, phe])</pre><p>
    </p><p>
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Argument</th><th>Explanation</th></tr></thead><tbody><tr><td>lhs</td><td>
          <p>
           This is the "left-hand-side" of the mapping. When you use
           <code class="literal">IMAP</code>, only the last character of this word is
           actually mapped, although the effect is that the whole word is
           mapped.
          </p>
          <p>
           If you have two mappings which end in a common
           <code class="literal">lhs</code>, then the mapping with the longer
           <code class="literal">lhs</code> is used. For example, if you do
           </p><pre class="programlisting">call IMAP('BarFoo', 'something', 'tex')
call IMAP('Foo', 'something else', 'tex')</pre><p>
            Then typing <code class="literal">BarFoo</code> inserts
            <code class="literal">"something"</code>, whereas <code class="literal">Foo</code> by
            itself inserts <code class="literal">"something else"</code>.
          </p>
          <p>
           Also, the nature of <code class="literal">IMAP()</code> makes creating
           certain combination of mappings impossible. For example if you
           have
           </p><pre class="programlisting">call IMAP('foo', 'something', 'tex')
call IMAP('foobar', 'something else', 'tex')</pre><p>
           Then you will never be able to trigger <code class="literal">"foobar"</code>
           because typing <code class="literal">"foo"</code> will immediately insert
           <code class="literal">"something"</code>. This is the "cost" which you incur
           over the normal <code class="literal">:imap</code> command for the
           convenience of no 'timeout' problems, the ability to correct
           <code class="literal">lhs</code> etc.
          </p>
         </td></tr><tr><td>rhs</td><td>
          <p>
           The "right-hand-side" of the mapping. This is the expansion you
           will get when you type <code class="literal">lhs</code>.
          </p>
          <p>
           This string can also contain special characters such as
           <code class="literal">&lt;enter&gt;</code> etc. To do this, you will need
           to specify the second argument in double-quotes as follows:
           </p><pre class="programlisting">:call IMAP('EFE', "\\begin{figure}\&lt;CR&gt;&lt;++&gt;\\end{figure}&lt;++&gt;", 'tex')</pre><p>
           With this, typing <code class="literal">EFE</code> is equivalent to typing
           in the right-hand side with all the special characters in
           insert-mode. This has the advantage that if you have filetype
           indentation set up, then the right hand side will also be
           indented just as if you had typed it in normally.
          </p>
          <a id="IMAP_PutTextWithMovement"></a>
          <p>
           You can also set up a Latex-Suite style mapping which calls a custom function
           as follows:
           </p><pre class="programlisting">:call IMAP('FOO', "\&lt;C-r&gt;=MyFoonction()\&lt;CR&gt;", 'tex')</pre><p>
           where <code class="literal">MyFoonction</code> is a custom function you have
           written. If <code class="literal">MyFoonction</code> also has to return a string
           containing <code class="literal">&lt;++&gt;</code> characters, then you will need to
           use the function <code class="literal">IMAP_PutTextWithMovement()</code>. An
           example best explains the usage:
          </p>
          <pre class="programlisting">call IMAP('FOO', "\&lt;C-r&gt;=AskVimFunc()\&lt;CR&gt;", 'vim')
" Askvimfunc: Asks For Function Name And Sets Up Template 
" Description: 
function! AskVimFunc()
    let name = input('Name of the function : ')
    if name == ''
        let name = "&lt;+Function Name+&gt;"
    end
    let islocal = input('Is this function scriptlocal ? [y]/n : ', 'y')
    if islocal == 'y'
        let sidstr = '&lt;SID&gt;'
    else
        let sidstr = ''
    endif
    return IMAP_PutTextWithMovement( 
        \ "\" ".name.": &lt;+short description+&gt; \&lt;cr&gt;" .
        \ "Description: &lt;+long description+&gt;\&lt;cr&gt;" . 
        \ "\&lt;C-u&gt;function! ".name."(&lt;+arguments+&gt;)&lt;++&gt;\&lt;cr&gt;" . 
        \       "&lt;+function body+&gt;\&lt;cr&gt;" . 
        \ "endfunction \" "
        \ )
endfunction</pre>
          <p>
          </p>
         </td></tr><tr><td>ft</td><td>
          <p>
           The file type for which this mapping is active. When this string
           is left empty, the mapping applies for all file-types. A filetype
           specific mapping will always take precedence.
          </p>
         </td></tr><tr><td>phs, phe</td><td>
          <p>
           If you prefer to write the <code class="literal">rhs</code> with characters
           other than <code class="literal">&lt;+</code> and <code class="literal">+&gt;</code>
           to denote place-holders, you can use the last 2 arguments to
           specify which characters in the <code class="literal">rhs</code> specify
           place-holders. By default, these are <code class="literal">&lt;+</code> and
           <code class="literal">+&gt;</code> respectively.
          </p>
          <p>
           Note that the <code class="literal">phs</code> and <code class="literal">phe</code>
           arguments do not control what characters will be displayed for
           the placeholders when the mapping is actually triggered. What
           characters are used to display place-holders when you trigger an
           <code class="literal">IMAP</code> are controlled by the <a class="link" href="#Imap_PlaceHolderStart" title="11.2.2 g:Imap_PlaceHolderStart &amp; g:Imap_PlaceHolderEnd"><code class="literal">Imap_PlaceHolderStart</code></a>
           and <a class="link" href="#Imap_PlaceHolderEnd"><code class="literal">Imap_PlaceHolderEnd</code></a>
           settings.
          </p>
         </td></tr></tbody></table></div><p>
    </p></div></div></div><div class="section" title="4 Package Handling"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-packages"></a>4 Package Handling</h2></div></div></div><p>
   Latex-Suite has a lot of functionality written to ease working with packages.
   Packages here refers to files which you include into the LaTeX
   document using the <code class="literal">\usepackage</code> command.
  </p><div class="section" title="4.1 Inserting package commands"><div class="titlepage"><div><div><h3 class="title"><a id="inserting-packages"></a>4.1 Inserting package commands</h3></div></div></div><p>
    When you first invoke Latex-Suite, it scans the
    <code class="literal">$VIM/ftplugin/latex-suite/packages</code> directory for
    package script files and creates a menu from all the files found there.
    This menu is created under <code class="literal">TeX-Suite &gt; Packages &gt;
     Supported</code>. This menu contains a list of packages "supported"
    by Latex-Suite. When you choose one of the packages from this menu (for example
    the <code class="literal">amsmath</code> package), then a line of
    the form
    </p><pre class="programlisting">\usepackage[&lt;++&gt;]{amsmath}&lt;++&gt;</pre><p>
    will be inserted into the current file.
   </p><p>
    The <code class="literal">\usepackage</code> line can also be inserted in an easy
    manner in the current file by pressing <code class="literal">&lt;F5&gt;</code>
    while in the preamble of the current document. This will set up a prompt
    from the supported packages and ask you to choose from one of them. If
    you do not find the package you want to insert in the list, you can type
    in a package-name and it will use that. Pressing
    <code class="literal">&lt;F5&gt;</code> in the preamble on a line containing a
    single word will construct a <code class="literal">\usepackage</code> line from
    that word.
   </p><p>
    You can also use the <a class="link" href="#TPackage" title="10.2.5 :TPackage [{package, ...}]"><code class="literal">TPackage</code></a> to insert the
    <code class="literal">\usepackage</code> line.
   </p><p>
    Once you have inserted a <code class="literal">\usepackage</code> line, for
    supported packages, you can use the Options and Commands menus
    described in the <a class="link" href="#package-actions" title="4.2 Actions taken for supported packages">next section</a>.
   </p></div><div class="section" title="4.2 Actions taken for supported packages"><div class="titlepage"><div><div><h3 class="title"><a id="package-actions"></a>4.2 Actions taken for supported packages</h3></div></div></div><p>
    Latex-Suite takes the following actions for packages detected when a file is
    loaded, or a new <code class="literal">\usepackage</code> line is inserted using
    one of the methods described in the <a class="link" href="#inserting-packages" title="4.1 Inserting package commands">previous section</a>.
   </p><p>
    If you are using the GUI and you have <a class="link" href="#Tex_Menus" title="11.8.1 g:Tex_Menus">g:Tex_Menus</a> set to 1, Latex-Suite will create the
    following sub-menus
   </p><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="literal">TeX-Suite &gt; Packages &gt; &lt;package&gt; Options</code></td></tr><tr><td><code class="literal">TeX-Suite &gt; Packages &gt; &lt;package&gt; Commands</code></td></tr></table><p>
   </p><p>
    where <code class="literal">&lt;package&gt;</code> is the package you just
    inserted (or was detected). You can use these menus to insert commands,
    environments and options which Latex-Suite recognizes as belonging to this
    package.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     While inserting an option, you need to position yourself in the
     appropriate place in the document, most commonly inside the square
     braces in the <code class="literal">\usepackage[]{packname}</code> command. Latex-Suite
     will not navigate to that location.
    </p></div><p>
    In addition to creating these sub-menus, Latex-Suite will also scan the
    <code class="literal">$VIM/ftplugin/latex-suite/dictionaries</code> directory and
    if a dictionary file corresponding to the package file is found, then
    it will add the file to the <code class="literal">'dict'</code> setting in Vim
    so you can use the <code class="literal">&lt;C-X&gt;&lt;C-K&gt;</code> command to
    complete words from that file.
   </p><p>
    For example, the <code class="literal">SIUnits</code> package has a custom
    dictionary.
   </p><a id="latex-package-scanning"></a><p>
    If a package detected at startup is found by Latex-Suite in the current
    directory or in a location specified by the <a class="link" href="#Tex_TEXINPUTS" title="11.10.1 g:Tex_TEXINPUTS">g:Tex_TEXINPUTS</a> variable, Latex-Suite will
    scan the package for <code class="literal">\newenvironment</code> and
    <code class="literal">newcommand</code> lines and also append any commands and
    environments found to the list of commands and environments which you
    are prompted with when you press <a class="link" href="#inserting-env-f5" title="3.1.1.1 Method 1: Pressing &lt;F5&gt;"><code class="literal">&lt;F5&gt;</code></a> or <a class="link" href="#ls-imap-f7"><code class="literal">&lt;F7&gt;</code></a> in insert
    mode.
   </p></div><p>
   In addition, the <code class="literal">TeX-Suite &gt; Packages</code> menu also
   contains the following submenus
  </p><p title="Update"><b>Update.</b>
   This command is to be invoked with the cursor placed on the package
   name. If the corresponding package is found, then a sub-menu with the
   supported commands and options is created.
  </p><p title="Update All"><b>Update All.</b>
   This function reads the preamble of the document for
   <code class="literal">\usepackage</code> lines and if Latex-Suite supports the detected
   packages, then sub-menus containing the package options and commands
   are created.
  </p><div class="section" title="4.3 Automatic Package detection"><div class="titlepage"><div><div><h3 class="title"><a id="automatic-package-detection"></a>4.3 Automatic Package detection</h3></div></div></div><p>
    Whenever Latex-Suite begins editing a new LaTeX file, it scans it for
    <code class="literal">\usepackage{name}</code> lines, and if a supported package
    is found, then it will create sub-menus and add to the
    <code class="literal">'dict'</code> setting as described above.
   </p><p>
    If a <a class="link" href="#latex-master-file" title="9.2 Specifying which file to compile">master-file</a> has been specified,
    then it will scan that file instead of the current file. See the section
    <a class="link" href="#custom-packages" title="4.3.1 Custom Packages">Custom Packages</a>
    to see which files Latex-Suite will scan in more detail.
   </p><p>
    For all the packages detected in this manner, Latex-Suite will take certain
    actions as described in the section <a class="link" href="#package-actions" title="4.2 Actions taken for supported packages">package support.</a>.
   </p><div class="section" title="4.3.1 Custom Packages"><div class="titlepage"><div><div><h4 class="title"><a id="custom-packages"></a>4.3.1 Custom Packages</h4></div></div></div><p>
     Often times, the preamble can become too long, and some people prefer
     to put most of their personalization in a custom package and include
     that using a <code class="literal">\usepackage</code> line. Latex-Suite tries to search
     such customs package for other <code class="literal">\usepackage</code> lines, so
     that supported packages included in this indirect manner can also be
     used to create sub-menus, extend the <code class="literal">'dict'</code> setting
     etc. The most obvious place to place such custom packages is in the
     same directory as the edited file. In addition, LaTeX also supports
     placing custom packages in places pointed to by the
     <code class="literal">$TEXINPUTS</code> environment variable.
    </p><p>
     If you use the <code class="literal">$TEXINPUTS</code> variable in LaTeX, and
     you wish Latex-Suite to search these custom packages for
     <code class="literal">\usepackage</code> lines, then you need to initialize the
     <a class="link" href="#Tex_TEXINPUTS" title="11.10.1 g:Tex_TEXINPUTS"><code class="literal">g:Tex_TEXINPUTS</code></a>
     variable.
    </p><p>
     The <code class="literal">g:Tex_TEXINPUTS</code> variable needs to be set in the
     same format which Vim uses for the <code class="literal">'path'</code> setting.
     This format is explained in detail if you do 
     </p><pre class="programlisting">:help file-searching</pre><p>
     from within Vim.
    </p><p>
     Therefore the value of <code class="literal">g:Tex_TEXINPUTS</code> will most
     probably be different from <code class="literal">$TEXINPUTS</code> which your
     native LaTeX distribution uses.
    </p><p>
     Example:
     </p><pre class="programlisting">let g:Tex_TEXINPUTS = '~/texmf/mypackages/**,./**'</pre><p>
     The <code class="literal">**</code> indicates that all directories below the
     directory <code class="literal">~/texmf/mypackages</code> and
     <code class="literal">./</code> are to be scanned for custom packages.
    </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      The present directory <code class="literal">'.'</code> is always searched. You
      need not include that in <code class="literal">g:Tex_TEXINPUTS</code>.
     </p></div></div></div><div class="section" title="4.4 Writing supporting for a package"><div class="titlepage"><div><div><h3 class="title"><a id="supporting-packages"></a>4.4 Writing supporting for a package</h3></div></div></div><p>
    Supporting a package is easy and consists of writing a vim script with
    the same name as the package and placing it in the
    <code class="literal">$VIM/ftplugin/latex-suite/packages</code> directory. A
    package script should define two variables as described in the next two
    sections. In addition to these two variables, you can also define any
    functions, environment definitions etc. in this file.
   </p><div class="section" title="4.4.1 g:Tex_package_option_&lt;package&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="id580293"></a>4.4.1 <code class="literal">g:Tex_package_option_&lt;package&gt;</code></h4></div></div></div><p>
     This setting is a string containing a comma separated list of options
     supported by this package.
    </p><p>
     Example:
     </p><pre class="programlisting">g:Tex_package_option_mypack = 'opt1,opt2=,sbr:group1,opt3,opt4'</pre><p>
     The <code class="literal">=</code> suffix means that the option takes a value.
     Use <code class="literal">sbr:group name</code> to separate options into
     sub-menus. All successive options will be clubbed into the
     <code class="literal">group1</code> sub-menu till the next
     <code class="literal">sbr:</code> option is encountered.
    </p></div><div class="section" title="4.4.2 g:Tex_package_&lt;package&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="id580338"></a>4.4.2 <code class="literal">g:Tex_package_&lt;package&gt;</code></h4></div></div></div><pre class="programlisting">
    g:TeX_package_&lt;package&gt; = "pre:Command,pre:Command1"
More detailed example is in latex-suite/packages/exmpl file (slightly
outdated).
Here is short summary of prefixes which can be used in package files:
(x - place with cursor, &lt;++&gt; - |placeholder|)

{env:command}  Environment: creates simple environment template
            \begin{command}
                x
            \end{command}&lt;++&gt;
{eno:command}  Environment with option:
            \begin[x]{command}
                &lt;++&gt;
            \end{command}&lt;++&gt;
{ens:command[&lt;&lt;option&gt;&gt;]...}  Environment special:
            \begin[&lt;&lt;option&gt;&gt;]...{command}
                &lt;++&gt;
            \end{command}&lt;++&gt;
{bra:command} Brackets:
            \command{x}&lt;++&gt;
{brd:command} Brackets double:
            \command{x}{&lt;++&gt;}&lt;++&gt;
{brs:command[&lt;&lt;option&gt;&gt;]...} Brackets special (as environment special:
            \command[&lt;+x+&gt;]{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt;
{nor:command} Normal:
            \command&lt;Space
{noo:command} Normal with option:
            \command[x]&lt;++&gt;
{nob:command} Normal with option and brackets:
            \command[x]{&lt;++&gt;}&lt;++&gt;
{pla:command} Plain:
            command&lt;Space
{spe:command} Special:
            command   &lt;-literal insertion of command
{sep:command} creates separator. Good for aesthetics and usability :)
{sbr:command} Breaks menu into submenus. &lt;command&gt; will be title of submenu.
            Can be used also in package variable.

Command can be also given without prefix:. The result is
           \command
          </pre></div></div></div><div class="section" title="5 Latex Completion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-completion"></a>5 Latex Completion</h2></div></div></div><p>
   Latex-Suite provides an easy way to insert references to labels and
   bibliographic entries and also provide filename arguments to commands
   such as <code class="literal">\includegraphics</code>. Although the completion
   capabilities are very diverse, Latex-Suite only uses a single key
   (<code class="literal">&lt;F9&gt;</code> by default) to do all of it. Pressing the
   <code class="literal">&lt;F9&gt;</code> key does different things based on where
   you are located. Latex-Suite tries to guess what you might be trying to
   complete at the location where you pressed
   <code class="literal">&lt;F9&gt;</code>. For example, pressing
   <code class="literal">&lt;F9&gt;</code> when you are within a
   <code class="literal">\ref</code> command will try to list the
   <code class="literal">\label</code>'s in the present directory. Pressing it when
   you are in a <code class="literal">\cite</code> command will list bibliography
   keys. Latex-Suite also recognizes commands which need a file name argument and
   will put up an explorer window for you to choose a filename.
  </p><div class="note" title="Before you start with Latex-Suite's completion function..." style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title"><a id="ls-set-grepprg"></a>Before you start with Latex-Suite's completion function...</h3><p>
    All of Latex-Suite's completion capabilities depend on a external program
    being available on your system which can search through a number of
    files for a reg-exp pattern. On *nix systems, the pre-installed
    <code class="literal">grep</code> utility is more than adequate.  Most windows
    systems come with a utility <code class="literal">findstr</code>, but that has
    proven to be very inadequate (for one, it does not have an option to
    force the file name to be displayed when searching through a single
    file). Your best bet is to install <a class="ulink" href="http://www.cygwin.com" target="_top">cygwin</a>, but if you think that's
    overkill, you can <a class="ulink" href="http://www.google.com/search?q=windows%20gnu%20grep" target="_top">search
     for</a> a windows implementation of GNU grep. (Latex-Suite testing on
    windows has been done with cygwin's port of GNU grep).
   </p><p>
    Once you have a <code class="literal">grep</code> program installed, you need to
    set the <code class="literal">'grepprg'</code> option for vim. Make sure you use a
    setting which forces the program to display file names even when you are
    searching through a single file. For GNU grep, the syntax is
    </p><pre class="programlisting">set grepprg=grep\ -nH\ $*</pre><p>
   </p></div><div class="section" title="5.1 Latex-Suite completion example"><div class="titlepage"><div><div><h3 class="title"><a id="ls-completion-usage"></a>5.1 Latex-Suite completion example</h3></div></div></div><p>
    Consider the situation where you are editing a file with two equations
    labelled <code class="literal">eqn:euler</code> and <code class="literal">eqn:einstein</code>.
    Now you want to insert a reference to one of these equations. To do this,
    you type the <code class="literal">\ref{eqn:}</code> command and with the cursor
    placed after <code class="literal">eqn:</code>, press <code class="literal">&lt;F9&gt;</code>.
    This will bring up two new windows beneath the main window you were working
    in as shown in the figure below. 
    </p><pre class="programlisting">
      8 These are a couple of equations:
      9 +--  4 lines: eqnarray (eqn:euler) :   e^{j\pi} + 1 &amp;=&amp; 0---------------
     13 +--  4 lines: equation (eqn:einstein) :   E = m c^2---------------------
     17
     18 These are a couple of figures:
     19 +--  7 lines: figure (fig:monkeys) : Monkeys can Type-------------------
     26 +--  7 lines: figure (fig:shakespeare) : Shakespeare could not type-----
     33
     34 This is a reference to \ref{eqn:}&lt;++&gt;
     35
     36
     37 \end{document}
     38
~
~
~
newfile.tex                                                   34,32          Bot
newfile.tex|11| \label{eqn:euler}
newfile.tex|15| \label{eqn:einstein}
~
[Error List]                                                  1,1            All
      7
      8 These are a couple of equations:
      9 \begin{eqnarray}
     10   e^{j\pi} + 1 &amp;=&amp; 0
     11   \label{eqn:euler}
     12 \end{eqnarray}
     13 \begin{equation}
     14   E = m c^2
     15   \label{eqn:einstein}
     16 \end{equation}
newfile.tex [Preview]                                         11,3           21%
  </pre><p>
   </p><p>
    The first window (shown as <code class="literal">[ErrorList]</code> above) is a
    <code class="literal">|cwindow|</code> containing a list of possible matches for the
    reference. The cursor will be located in the first line of this window. The
    bottom window is a <code class="literal">preview-window</code> showing the context of
    the <code class="literal">\label</code>. Moving around in the
    <code class="literal">[ErrorList]</code> window automatically scrolls the
    preview window so as to always keep showing the context of the
    <code class="literal">\label</code> being viewed in the
    <code class="literal">[ErrorList]</code> window. You can also press
    <code class="literal">J</code> and <code class="literal">K</code> in the
    <code class="literal">[ErrorList]</code> window to scroll the preview window up and
    down.
   </p><p>
    To insert one of the labels, simply position the cursor in the correct line
    in the <code class="literal">[ErrorList]</code> window and press
    <code class="literal">&lt;enter&gt;</code>. This will immediately close the two newly
    opened windows, get back to the correct location in the original file being
    edited and insert the label into the <code class="literal">\ref</code> command. 
   </p><p>
    If you notice carefully in the example above, the
    <code class="literal">[ErrorList]</code> window only showed the matches for the
    equations and did not list any of the figure labels. This is because we
    pressed <code class="literal">&lt;F9&gt;</code> after <code class="literal">\ref{eqn:</code>
    instead of simply after <code class="literal">\ref{</code>. This caused Latex-Suite to
    search only for those labels which started with the string
    <code class="literal">eqn:</code>. If you had pressed
    <code class="literal">&lt;F9&gt;</code> after a <code class="literal">\ref{</code>, you would
    have been shown matches from <span class="emphasis"><em>all</em></span> labels, not just
    those starting with <code class="literal">eqn:</code>.
   </p><p>
    Thus prefixing all your labels with <code class="literal">eqn:</code>,
    <code class="literal">fig:</code>, <code class="literal">tab:</code> etc. depending on what you
    are labelling will lead to an easier time completing references.
   </p></div><div class="section" title="5.2 Latex-Suite \ref completion"><div class="titlepage"><div><div><h3 class="title"><a id="ls-completion-ref"></a>5.2 Latex-Suite \ref completion</h3></div></div></div><p>
    Pressing <code class="literal">&lt;F9&gt;</code> when you are within a partially
    completed <code class="literal">\ref</code> command will split open a window
    (named <code class="literal">__OUTLINE__</code>) which contains a nicely
    formatted list of all the <code class="literal">\label</code>s found in the
    present project.  The <code class="literal">\label</code>s are heirarchically
    arranged according to which <code class="literal">\section</code>,
    <code class="literal">\subsection</code> etc of the overall document structure
    they are present in. For example, when you first press
    <code class="literal">&lt;F9&gt;</code> after typing <code class="literal">\ref{</code>,
    you should see something like:
    </p><pre class="programlisting">
+-- 54 lines: 2. Kinematics--------------------------------
+-- 98 lines: 3. Aerodynamics of the MFI thorax------------
+-- 40 lines: 4. Jump Resonance in Fourbar Mechanisms------
+-- 28 lines: 5. Design and Fabrication Issues-------------
    </pre><p>
    Each chapter is |fold|ed away so that you can quickly jump to the
    correct section/subsection in which the relevant equation is defined.
    This makes inserting references significantly faster for large projects
    with hundreds of equations. You can then open some of the folds to see
    for example:
    </p><pre class="programlisting">
+-- 54 lines: 2. Kinematics--------------------------------
3. Aerodynamics of the MFI thorax
    3.1. Aerodynamic modeling of the MFI wing forces
        3.1.1. Geometric Specification
               eqn:wingnormal-pos
                 \nhat =  T_z(\theta_2) T_y(\theta_y)T_x(\theta_x)\nhat_0,
               eqn:T-1
                 T_1(\theta_2) &amp;=&amp; T_z(\theta_2)
    </pre><p>
    The <code class="literal">&lt;Tab&gt;</code> key is mapped in this window to
    toggle folds so that you can quickly open/close folds in order to
    navigate the heirarchy faster. Once you are positioned on a
    label, press <code class="literal">&lt;Enter&gt;</code>. This closes the
    <code class="literal">__OUTLINE__</code> window, returns to the window in which
    you pressed <code class="literal">&lt;F9&gt;</code> and inserts the reference
    at the current cursor position.
   </p><div class="note" title="Filtering labels by prefix" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Filtering labels by prefix</h3><p>
     You can press <code class="literal">&lt;F9&gt;</code> after typing part of the
     <code class="literal">\label</code>. In this case, Latex-Suite only presents
     <code class="literal">\label</code>s which begin with the already filled
     characters. You can use this to choose between equations, figures,
     tables etc. if you consistently label equations to begin with
     <code class="literal">eqn:</code>, figures to begin with <code class="literal">fig:</code>
     etc. For example, with this scheme, pressing
     <code class="literal">&lt;F9&gt;</code> after typing
     <code class="literal">\ref{eqn:</code> will only list equations.
   </p></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     Latex-Suite works the same way if you press <code class="literal">&lt;F9&gt;</code>
     after any command which contains the letters <code class="literal">ref</code>.
     Thus you can complete <code class="literal">\eqref</code> in exactly the same
     manner.
   </p></div><div class="note" title="Requirements" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Requirements</h3><p>
     This method of preseting the <code class="literal">\label</code>s depends on Vim
     being compiled with python support. To check if you have this, see the
     output of the <code class="literal">:ver</code> command. If you see something
     like <code class="literal">+python</code>, you are all set. Failing this, you
     will need to have <code class="literal">python</code> somewhere in your
     <code class="literal">$PATH</code>.
    </p></div></div><div class="section" title="5.3 Latex-Suite \cite completion"><div class="titlepage"><div><div><h3 class="title"><a id="latex-completion-cite"></a>5.3 Latex-Suite <code class="literal">\cite</code> completion</h3></div></div></div><p>
    Latex-Suite provides an easy way to insert references to bibliographic
    entries. Pressing <code class="literal">&lt;F9&gt;</code> when the cursor is
    placed inside a partially completed <code class="literal">\cite</code> command
    will split open a new window (named <code class="literal">__OUTLINE__</code>)
    which contains a formatted and syntax highlighted list of all bibtex
    entries found. For example, pressing <code class="literal">&lt;F9&gt;</code>
    after typing <code class="literal">\ref{</code> should present you with a window
    which looks something like this:
    </p><pre class="programlisting">
Article [dickinson:science:99]
   "Wing rotation and aerodynamic basis of insect flight"
   M. H. Dickinson and F-O. Lehman and S. P. Sane
   In Science, 1999

Article [ellington:84:part1]
   "The Aerodynamics of Hovering Insect Flight. I. The Quasi-Steady Analysis"
   Ellington, C P
   In Philosophical Transactions of the Royal Society of London. Series B, Biological Sciences, 1984

Article [ellington:84:part2]
   "The Aerodynamics of Hovering Insect Flight. II. Morphological Parameters"
   Ellington, C P
   In Philosophical Transactions of the Royal Society of London. Series B, Biological Sciences, 1984
    </pre><p>
   </p><p>
    You can easily jump from one entry to another using the
    <code class="literal">'n'</code> and <code class="literal">'p'</code> keys (to go to the
    next / previous entry respectively).
   </p><p>
    You can also filter out a subset of the bibtex entries by pressing
    <code class="literal">'f'</code> while in this window. Doing this presents the
    following prompt:
    </p><pre class="programlisting">
Field acronyms: (`:let g:Tex_EchoBibFields = 0` to avoid this message)
 [t] title         [a] author        [b] booktitle
 [j] journal       [y] year          [p] bibtype
 (you can also enter the complete field name)
Enter filter criterion [field&lt;space&gt;value]:
    </pre><p>
    At the prompt, type
    </p><pre class="programlisting">a ellington</pre><p>
    Notice that the letter a is an acronym for <code class="literal">author</code>
    according to the prompt above. Therefore this filter only shows those
    bibtex entries whose author field contains the text
    <code class="literal">ellington</code>. You can keep narrowing your selection by
    repeatedly filtering the results. If you would like to remove all the
    filters and see all entries again, press 'a', which removes
    all the filters.
   </p><p>
    You can also sort the bibtex entries based on a field. To do this,
    press 's'. This will present you with a prompt like in the case of the
    filter and you are asked to choose a field. In this case, you would
    type in a single character. This sorts the entries according to that
    field.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    <code class="literal">&lt;F9&gt;</code> will also work in a similar way after any
    command which contains the word <code class="literal">cite</code> in it. For
    example, pressing <code class="literal">&lt;F9&gt;</code> will also work with
    <code class="literal">\citenum</code> etc.
   </p></div><p>
    The following logic is applied to find out which bibliographic entries
    are included in the completion.
   </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
      Firstly, if the present file has a <a class="link" href="#latex-master-file" title="9.2 Specifying which file to compile">master-file</a> defined for it, then Latex-Suite
      will perform the following steps on that file instead of on the
      current file.
     </p></li><li class="listitem"><p>
      First, the file is scanned for a <code class="literal">\bibliography</code>
      command. To explain better, assume that a command
      </p><pre class="programlisting">\bibliography{file1,file2}</pre><p> is found
      in the present file. For each bibliography file, say
      <code class="literal">file1</code>, Latex-Suite first tries to see if a
      <code class="literal">.bib</code> file, <code class="literal">file1.bib</code> can be
      found. If so, it will scan it for bib-keys of the form
      <code class="literal">@BOOK{</code> etc., and add these searches to the
      completion list. If a <code class="literal">.bib</code> file cannot be found,
      then it will try to see if <code class="literal">file1.bbl</code> can be found.
      If so, Latex-Suite will search it for bib-keys of the form
      <code class="literal">\bibitem</code> and add these to the completion list.
     </p><p>
      You can set the location where Latex-Suite will search for
      <code class="literal">.bib</code> and <code class="literal">.bbl</code> files using the
      <a class="link" href="#Tex_BIBINPUTS" title="11.5.2 g:Tex_BIBINPUTS"><code class="literal">|Tex_BIBINPUTS|</code></a>
      variable.
     </p></li><li class="listitem"><p>
      If a <code class="literal">\bibliography</code> command is not found, then Latex-Suite
      tries to scan the present file for a
      <code class="literal">\begin{thebibliography}</code> environment. If found,
      Latex-Suite searches the present file for bib-keys of the form
      <code class="literal">\bibitem</code>.
     </p></li><li class="listitem"><p>
      Finally, it will try to see if this file includes other files
      via the <code class="literal">\input</code> command. For each such file found,
      Latex-Suite will repeat the previous two steps stopping at the first file
      which has either a <code class="literal">\bibliography</code> command or a
      <code class="literal">thebibliography</code> environment.
     </p></li></ol></div><div class="section" title="5.3.1 Caching the \cite completion results"><div class="titlepage"><div><div><h4 class="title"><a id="cite-search-caching"></a>5.3.1 Caching the <code class="literal">\cite</code> completion results</h4></div></div></div><a id="TClearCiteHist"></a><p>
     Often times, the editing cycle proceeds by first laying out a
     comprehensive bibliography and then completing all the
     <code class="literal">\cite</code> commands in one session. In such situations,
     it is inefficient to scan the whole list of bibliography files for
     bib-keys each time. Latex-Suite provides a way to cache the results of the
     cite completion search using the <a class="link" href="#Tex_RememberCiteSearch" title="11.5.5 g:Tex_RememberCiteSearch"><code class="literal">Tex_RememberCiteSearch</code></a>
     variable. If set, Latex-Suite will perform the search only the first time
     <code class="literal">&lt;F9&gt;</code> is used. Next time on, it will reuse the
     search results. If you wish to redo the search results, issue the
     command
     </p><pre class="programlisting">TClearCiteHist</pre><p>
     This will redo the completion list next time you use
     <code class="literal">&lt;F9&gt;</code>.
    </p></div></div><div class="section" title="5.4 Latex-Suite filename completion"><div class="titlepage"><div><div><h3 class="title"><a id="ls-filename-completion"></a>5.4 Latex-Suite filename completion</h3></div></div></div><p>
    When you press <code class="literal">&lt;F9&gt;</code> at a location where Latex-Suite
    guesses a filename needs to be typed, then a new explorer window will
    open up with the list of files. You can use this window to change
    directories etc. Pressing <code class="literal">&lt;enter&gt;</code> on a filename
    in the explorer window will automatically close the explorer window,
    return to the location where you pressed <code class="literal">&lt;F9&gt;</code>
    from and insert the filename into that position.
   </p><p>
    Latex-Suite also tries to guess what kinds of files you might not want to
    insert and hides those accordingly. For example, if you press
    <code class="literal">&lt;F9&gt;</code> when you are located at
    <code class="literal">\includegraphics{</code>, then Latex-Suite knows that you will not
    want to insert <code class="literal">.tex</code> files. Therefore, the explorer
    window will automatically hide these files.
   </p><p>
    As of now, Latex-Suite recognizes the following commands for filename
    completion. Along with the commands, this table also lists the
    files which Latex-Suite will not show for completing each command.
   </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>command</th><th>hide pattern</th></tr></thead><tbody><tr><td><code class="literal">\bibliography</code></td><td><code class="literal">'^\.,\.[^b]..$'</code></td></tr><tr><td><code class="literal">\include</code> <code class="literal">\includeonly</code></td><td><code class="literal">'^\.,\.[^t]..$'</code></td></tr><tr><td><code class="literal">\includegraphics</code> <code class="literal">\psfig</code></td><td><code class="literal">'^\.,\.tex$,\.bib$,\.bbl$,\.zip$,\.gz$'</code></td></tr><tr><td><code class="literal">\input</code></td><td><code class="literal">''</code></td></tr></tbody></table></div></div><div class="section" title="5.5 Custom command completion"><div class="titlepage"><div><div><h3 class="title"><a id="ls-completion-custom"></a>5.5 Custom command completion</h3></div></div></div><p>
    Latex-Suite also recognizes certain commonly used LaTeX commands for the
    <code class="literal">&lt;F9&gt;</code> key. At the moment, the
    <code class="literal">\bibliographystyle</code>, <code class="literal">\addtocontents</code>
    and the <code class="literal">\addcontentsline</code> commands are recognized,
    although more will be added in the future. When you press the
    <code class="literal">&lt;F9&gt;</code> after such a command, Latex-Suite will prompt
    you with a list of arguments which make sense for the command.
   </p><p>
    This functionality is available for commands for which a global
    variable of the form
    <code class="literal">g:Tex_completion_{&lt;command&gt;}</code> is defined where
    <code class="literal">&lt;command&gt;</code> is the command name. This variable
    is a comma separated list of values which this command takes. For
    example, the argument to the <code class="literal">\bibliographystyle</code>
    command is commonly one of <code class="literal">abbr,alpha,plain,unsrt</code>.
    Therefore, Latex-Suite defines
    </p><pre class="programlisting">let g:Tex_completion_bibliographystyle = 'abbr,alpha,plain,unsrt'</pre><p>
    You can define your own completion variables in a similar manner for
    commands which you might use.
   </p></div></div><div class="section" title="6 LaTeX Compiling"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-compiling"></a>6 LaTeX Compiling</h2></div></div></div><p>
   This functionality, available via the TeX-Suite menu, provides various tools
   to compile and debug LaTeX files from within Vim.
  </p><p>
   If you are using commonly used LaTeX tools, then you should be all set
   as soon as you download and install Latex-Suite.  In order to compile a
   LaTeX file, simply press <code class="literal">\ll</code> while editing the file.
   This runs latex on the current file and displays the errors in a
   |quickfix-window| below the file being edited. You can then scroll
   through the errors and press <code class="literal">&lt;enter&gt;</code> to be
   taken to the location of the corresponding error. Along with the errors
   being listed in the quickfix window, the corresponding log file is also
   opened in |preview| mode beneath the quickfix window. It is scrolled
   automatically to keep in sync with the error being viewed in the
   quickfix window. You will be automatically taken to the location of the
   first error/warning unless you set the <a class="link" href="#Tex_GotoError" title="11.6.8 g:Tex_GotoError">g:Tex_GotoError</a> variable to 0.
  </p><p>
   Latex-Suite also supports compiling LaTeX into formats other than DVI. By
   default, Latex-Suite supports PDF and PS formats. In order to choose a format
   other than DVI, use the <code class="literal">TTarget</code> command or the
   <code class="literal">TeX-Suite &gt; Target Format</code> menu item. This will ask you
   to type in the name of the target format you want to compile to. If a rule
   has been defined for the format (as described in the next
   <a class="link" href="#compiler-rules" title="6.1 Setting Compilation rules">section</a>), then Latex-Suite will switch to
   that format.
  </p><p>Trying to choose a format for which no rule has been defined will
   result in Latex-Suite displaying a warning message without taking any action.
  </p><p>
   If you are using a multiple file project and need to compile a master
   file while editing other files, then Latex-Suite provides a way to specify the
   file to be compiled as described in <a class="link" href="#latex-master-file" title="9.2 Specifying which file to compile">latex-master-file</a>.
  </p><div class="section" title="6.1 Setting Compilation rules"><div class="titlepage"><div><div><h3 class="title"><a id="compiler-rules"></a>6.1 Setting Compilation rules</h3></div></div></div><p>
    In order to compile LaTeX files into various formats, Latex-Suite needs to know
    which external programs to call and in which way they need to be called.
    This information is provided to Latex-Suite via a number of "rules". For each
    format you want to compile to, you need to specify a rule. A rule is
    specified by defining a variable of the form:
    </p><pre class="programlisting">g:Tex_CompileRule_&lt;format&gt;</pre><p>
    where <code class="literal">&lt;format&gt;</code> is a string like
    <code class="literal">"pdf"</code>, <code class="literal">"dvi"</code> etc.
   </p><p>
    Example: By default, Latex-Suite uses the following rule for compiling LaTeX
    documents into DVI.
    </p><pre class="programlisting">g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'</pre><p>
   </p><p>
    Default values are also provided for ps and pdf formats. You might want to
    change these rules in texrc according to your local tex environment.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     For win32 users user MikTeX, sometimes the latex compiler's output has a
     bug where a single number is split across different lines. In this case,
     put the included <code class="literal">vim-latex</code> file distributed with Latex-Suite.
    </p></div></div><div class="section" title="6.2 Handling dependencies in compilation"><div class="titlepage"><div><div><h3 class="title"><a id="compiler-dependency"></a>6.2 Handling dependencies in compilation</h3></div></div></div><p>
    Latex-Suite also handles compiling dependencies automatically via certain
    rules which specify the "dependency chain" for each target format. 
    For example, if in your case, you use
    </p><pre class="programlisting">.tex -&gt; .dvi -&gt; .ps -&gt; .pdf</pre><p>
    to generate <code class="literal">pdf</code> files from <code class="literal">dvi</code>
    files, then you will need to specify the following setting in your
    Latex-Suite configuration (see <a class="link" href="#customizing-latex-suite" title="11 Customizing Latex-Suite">customizing Latex-Suite</a> for where
    these settings should go):
    </p><pre class="programlisting">
let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
</pre><p>
    This is a comma separated string of formats specifying the order in
    which the formats to be compiled into should be chosen.  With this
    setting, if you set the target format to <code class="literal">pdf</code>, then
    the next time you compile via the <code class="literal">\ll</code> shortcut, Latex-Suite
    will first generate a <code class="literal">dvi</code> file, then use that to
    generate the <code class="literal">ps</code> file and finally create the
    <code class="literal">pdf</code> file from that.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     If any of the intermediate formats is listed in the
     <code class="literal">g:Tex_MultipleCompileFormats</code> setting as described
     in the section <a class="link" href="#compiling-multiple" title="6.3 Compiling multiple times">Compiling multiple
      times</a>, then Latex-Suite might make multiple calls to the compiler to
     generate the output file of that format.
    </p></div><p>
    Along with the <code class="literal">g:Tex_FormatDependency_{format}</code>
    setting, you should ofcourse specify the rule for compiling to each of
    the formats as described in the <a class="link" href="#compiler-rules" title="6.1 Setting Compilation rules">previous
    section</a>. For example, with the setting above, you could use:
    </p><pre class="programlisting">
let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'
let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'</pre><p>
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     By default, Latex-Suite does not specify any compiler dependencies. Each
     target format for which a rule has been derived will be compiled
     independently.
    </p></div></div><div class="section" title="6.3 Compiling multiple times"><div class="titlepage"><div><div><h3 class="title"><a id="compiling-multiple"></a>6.3 Compiling multiple times</h3></div></div></div><p>
    Most LaTeX compilers need to be re-run several times in several
    commonly occurring situations in order to get a final camera ready copy.
    For example, when <code class="literal">\label</code>'s change, when new
    <code class="literal">\cite</code> commands are added etc. If the target format
    you are compiling to requires multiple compilations, then you will
    need to include the format in the
    <code class="literal">g:Tex_MultipleCompileFormats</code> setting. This is a
    comma separated string of formats which need multiple compilations to
    be generated correctly.
   </p><p>
    By default, this setting contains just the <code class="literal">dvi</code>
    format. If you use the <code class="literal">pdflatex</code> compiler to generate
    <code class="literal">pdf</code> files, then you might want to also include
    <code class="literal">pdf</code> into the above setting.
   </p><p>
    For every format included in the
    <code class="literal">g:Tex_MultipleCompileFormats</code> setting described
    above, Latex-Suite will use the following logic to generate the file. Note
    that although the following description uses <code class="literal">latex</code>
    to refer to the compiler, it could be some other compiler such as
    <code class="literal">pdflatex</code> for generating <code class="literal">pdf</code>
    output.
   </p><p>
    </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">If there was a <code class="literal">.idx</code> file, then remember
      its contents.</li><li class="listitem">Run <code class="literal">latex</code>.</li><li class="listitem">If the <code class="literal">.idx</code> file changed due to the latex
      compiler, then run <code class="literal">makeindex</code> to redo the
      <code class="literal">.ind</code> file and then remember to rerun latex.
     </li><li class="listitem"><p>
       If the <code class="literal">.aux</code> file generated by the latex
       compiler contains a <code class="literal">\bibdata</code> line, then it
       means that we are using a <code class="literal">.bib</code> file. Therefore,
       run <code class="literal">bibtex</code>.
      </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
        This means that we will always run <code class="literal">bibtex</code>
        whenever we use the <code class="literal">\bibliography</code> command
        whether or not we actually need to. At this time, Latex-Suite does not
        parse the <code class="literal">.aux</code> file before and after the latex
        compiler to see if we are required to rerun
        <code class="literal">bibtex</code>.
       </p></div></li><li class="listitem">
      If the <code class="literal">.bbl</code> file changes because of this, then
      remember to rerun latex again.
     </li><li class="listitem">Also, we check to see if the LaTeX compiler gives certain
      standard warnings which notify that we need to compile once again. In
      this case also, remember to rerun LaTeX.</li><li class="listitem">If we found we had to rerun latex, then we repeat
      the steps above but not running <code class="literal">makeindex</code> or
      <code class="literal">bibtex</code> again.</li></ol></div><p>
   </p><p>
    The LaTeX file is compiled atmost 5 times using this logic.  These
    steps will ensure that on most platforms/environments, you will get a
    clean output with all the cross-references, citations etc correctly
    labelled and ordered. 
   </p></div><div class="section" title="6.4 Customizing the compiler output"><div class="titlepage"><div><div><h3 class="title"><a id="compiler-output-customization"></a>6.4 Customizing the compiler output</h3></div></div></div><p>
    Most LaTeX compilers produce a very large amount of output during
    compilation, most of which is not relevant to debugging type-setting
    errors. The compiler plugin provided with Latex-Suite (which is an enhanced
    version of the standard compiler plugin maintained by Artem Chuprina),
    provides a way to filter the compiler output so that the actual
    errors/warnings can be presented much more concisely.
   </p><p>
    The compiler plugin is set up by default to function in a "non-verbose",
    "ignore-common-warnings" mode, which means that irrelevant lines from the
    compiler output will be ignored and some very common warnings are also
    ignored.
    Latex-Suite does this via the global variable <a class="link" href="#Tex_IgnoredWarnings" title="11.6.5 g:Tex_IgnoredWarnings"><code class="literal">g:Tex_IgnoredWarnings</code></a>.
    This is a list of patterns, which can be used to filter out (or ignore)
    some or the warnings and errors reported by the compiler. See the link
    above for its default value.
   </p><p>
    Latex-Suite uses the <a class="link" href="#Tex_IgnoreLevel" title="11.6.6 g:Tex_IgnoreLevel"><code class="literal">g:Tex_IgnoreLevel</code></a>
    setting to set a default ignore level. For example, for the default
    value of 4, Latex-Suite ignores warnings and errors matching the first 4
    patterns in <code class="literal">g:Tex_IgnoredWarnings</code>.
   </p><p>
    In addition to setting a default value of the ignore level, Latex-Suite
    provides the ability to set the level dynamically, using the
    <code class="literal">TCLevel</code> command. For example, if you issue the
    command:
    </p><pre class="programlisting">TCLevel 3</pre><p>
    from within Vim, then the next time you compile the document, Latex-Suite will
    ignore warnings and errors which match the first three patterns in
    <code class="literal">g:Tex_IgnoredWarnings</code>.
   </p><p>
    When TCLevel is called with the unquoted string strict as follows:
    </p><pre class="programlisting">TClevel strict</pre><p>
    then Latex-Suite switches to a "verbose", "no-lines-ignored" mode which is useful
    when you want to make final checks of your document and want to be careful
    not to let things slip by.
   </p><p>
    See the explanation of the settings <a class="link" href="#Tex_IgnoredWarnings" title="11.6.5 g:Tex_IgnoredWarnings">g:Tex_IgnoredWarnings</a> and <a class="link" href="#Tex_IgnoreLevel" title="11.6.6 g:Tex_IgnoreLevel">g:Tex_IgnoreLevel</a> to find out how to
    customize the filtering done by Latex-Suite
   </p></div><div class="section" title="6.5 Compiling parts of a file"><div class="titlepage"><div><div><h3 class="title"><a id="part-compiling"></a>6.5 Compiling parts of a file</h3></div></div></div><p>
    Latex-Suite also provides a way to compile a fragment of a document. This can be
    very useful while debugging a complex equation or one chapter in a book,
    etc. 
   </p><p>
    To do this, visually select a portion of the text and press
    <code class="literal">\ll</code> while in visual mode. The visually selected portion
    will be saved to a temporary file with the preamble from the current
    document prepended. Latex-Suite will then switch focus to this temporary file and
    compile it. Continue to debug this file as required and then replace the
    portion of the original file with this one. 
   </p><p>
    Pressing <code class="literal">\lv</code> while viewing the temporary file will
    view the output file generated from the temporary file, not the original
    file
   </p><p>
    Two commands |TPartComp| and |TPartView| are provided to be able to get
    this functionality via the command line.
   </p><p>
    From release 1.6 onwards of Latex-Suite, the temporary file created
    for part compilation will reside in the same directory as the file from
    which the fragment is being created. This ensures that any relative
    path-names defined in the fragment will still work. Latex-Suite will
    attempt to clean the temporary file(s) created when Vim exits.
   </p></div></div><div class="section" title="7 Latex Viewing and Searching"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-viewing"></a>7 Latex Viewing and Searching</h2></div></div></div><div class="section" title="7.1 Setting Viewing rules"><div class="titlepage"><div><div><h3 class="title"><a id="latex-viewing-rules"></a>7.1 Setting Viewing rules</h3></div></div></div><p>
    In order to view the output files created by compiling the source
    files, you need to specify which external program Latex-Suite should call. You
    can specify the external program using one of two settings
    <a class="link" href="#Tex_ViewRule_format" title="11.7.1 g:Tex_ViewRule_&lt;format&gt;">Tex_ViewRule_format</a> or <a class="link" href="#Tex_ViewRuleComplete_format" title="11.7.2 Tex_ViewRuleComplete_&lt;format&gt;">Tex_ViewRuleComplete_format</a>.
    By default, Latex-Suite has default settings for viewing various common output
    formats via the <code class="literal">Tex_ViewRule_format</code> settings, so
    that if you are using commonly used programs, you should be all set to
    view compiled files from within Vim by simply pressing
    <code class="literal">\lv</code>.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     The viewing function also takes the <a class="link" href="#latex-master-file" title="9.2 Specifying which file to compile"><code class="literal">*.latexmain</code></a> file
     into account to decide which file to show.
    </p></div><p>
    If pressing <code class="literal">\lv</code> does not work, then it most probably
    has to do with incorrect settings of the <a class="link" href="#Tex_ViewRule_format" title="11.7.1 g:Tex_ViewRule_&lt;format&gt;"><code class="literal">g:Tex_ViewRule_&lt;format&gt;</code></a>
    where <code class="literal">&lt;format&gt;</code> is the format you are
    attempting to view. See the link above for how to set this according to
    your system.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     On Windows and OS/X, you can leave the view rule empty to open the document
     with the default viewer on your system. On Linux/UNIX systems, you can use
     the <code class="literal">xdg-open</code> command to open the document with the default
     viewer.
    </p></div><p>
    In addition to viewing the files, Latex-Suite also supports forward and inverse
    searching for certain common tools for viewing documents.
    See the next few sections for details on forward and inverse searching,
    including an overview of viewers.
   </p></div><div class="section" title="7.2 Forward Searching documents"><div class="titlepage"><div><div><h3 class="title"><a id="forward-searching"></a>7.2 Forward Searching documents</h3></div></div></div><p>
    Forward searching refers to making a viewer display a given document at
    a given location from within Vim. At present, these viewers are known to support
    forward searching, but viewers that are not listed here may work, too:
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col><col></col></colgroup><thead><tr><th>Viewer</th><th>OS</th><th>Supported documents</th><th>Comment</th></tr></thead><tbody><tr><td><a class="ulink" href="http://skim-app.sourceforge.net/" target="_top">Skim</a></td><td>Apple / OS X Tiger</td><td>PDF</td><td>Supports also inverse searching</td></tr><tr><td><a class="ulink" href="http://pdfview.sourceforge.net/" target="_top">PDFView</a></td><td>Apple / OS X</td><td>PDF</td><td>No longer in development, supports also inverse searching</td></tr><tr><td><a class="ulink" href="http://www2.ing.unipi.it/~d9615/homepage/texniscope.html" target="_top">TeXniscope</a></td><td>Apple</td><td>PDF, DVI</td><td></td></tr><tr><td><a class="ulink" href="http://www.miktex.org/" target="_top">YAP</a></td><td>Windows</td><td>DVI, PS</td><td>ships with MikTex</td></tr><tr><td><a class="ulink" href="http://blog.kowalczyk.info/software/sumatrapdf/" target="_top">Sumatra PDF</a></td><td>Windows</td><td>PDF</td><td></td></tr><tr><td><a class="ulink" href="http://developer.kde.org/~kdvi/" target="_top">kdvi</a></td><td>Linux/UNIX</td><td>DVI</td><td></td></tr><tr><td><a class="ulink" href="http://okular.kde.org/" target="_top">okular</a></td><td>Linux/UNIX</td><td>DVI, PDF, PS and many more</td><td>Included in KDE 4</td></tr><tr><td><a class="ulink" href="http://math.berkeley.edu/~vojta/xdvi.html" target="_top">xdvi</a></td><td>Linux/UNIX</td><td>DVI</td><td></td></tr><tr><td><a class="ulink" href="http://xdvi.sourceforge.net/" target="_top">xdvik</a></td><td>Linux/UNIX</td><td>DVI</td><td></td></tr></tbody></table></div><p>
    
    Pressing <code class="literal">\ls</code> from within Vim
    should make the viewer display the portion of the document where your
    cursor is placed.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     OS/X users need to set the <code class="literal">g:TreatMacViewerAsUNIX</code> flag
     to <code class="literal">1</code> and provide a UNIX-like viewrule, that expects as
     arguments the document, the linenumber and the sourcefile in this order.
    </p></div><p>
   </p><a id="enabling-searching"></a><div class="note" title="Enabling Forward and Inverse Searching" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Enabling Forward and Inverse Searching</h3><p>
     Most DVI viewers need "source-special" information in order to do
     forward (and inverse) searching. This information is embedded in the
     <code class="literal">dvi</code> file if the LaTeX source is compiled with the
     <code class="literal">--src-specials</code> option. By default, Latex-Suite does not
     supply this argument to the compiler. See the section on
     <code class="literal"><a class="link" href="#Tex_CompileRule_format" title="11.6.2 g:Tex_CompileRule_&lt;format&gt;">g:Tex_CompileRule_dvi</a></code>
     to find out how this option can be set.

     For pdf viewers you need to use the <a class="ulink" href="http://itexmac.sourceforge.net/pdfsync.html" target="_top">pdfsync</a>
     package in your LaTeX document.
    </p></div></div><div class="section" title="7.3 Inverse Searching"><div class="titlepage"><div><div><h3 class="title"><a id="inverse-searching"></a>7.3 Inverse Searching</h3></div></div></div><p>
    Inverse searching refers to the viewer telling Vim to display the
    LaTeX source file at a given location when you double-click in the 
    viewer window.
   </p><p>
    You will need to <a class="link" href="#enabling-searching">enable
     searching</a> in order to use this functionality.
   </p><p>
    You will also need to specify certain settings to the DVI viewer
    conveying the syntax which it needs to use to tell Vim how to display
    the source file. In <code class="literal">YAP</code>, you can set this option in
    <code class="literal">View &gt; Options &gt; Inverse Search</code>. The
    <code class="literal">Command Line</code> field needs to be set as follows:
    </p><pre class="programlisting">"C:\Program Files\vim\vim61\gvim" -c ":RemoteOpen +%l %f"</pre><p>
    The command <code class="literal">:RemoteOpen</code> is supplied when you install
    Latex-Suite.
   </p><p>
    On *nix machines, Latex-Suite attempts to call the DVI viewer in such a way
    that it already knows how to communicate with Vim. If this does not
    seem to be working, you can use the <code class="literal">RemoteOpen</code>
    command described above.
   </p></div></div><div class="section" title="8 Latex Folding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-folding"></a>8 Latex Folding</h2></div></div></div><p>
   Latex-Suite ships with the plugin SyntaxFolds.vim which is a plugin for
   creating "fake" syntax folds on the fly. The fold method is actually manual
   but the folding is based on LaTeX syntax. This offers a speed increase over
   regular syntax folding. Ofcourse it has the disadvantage that the folds are
   not dynamic, i.e newly created syntax items are not automatically folded up.
   (This is a compromise between speed and convenience).
  </p><p>
   When you open up a LaTeX file, all the portions will be automatically folded
   up. However, no new folds will be created until you press
   <code class="literal">&lt;F6&gt;</code> or <code class="literal">\rf</code>. (rf
   stands for "refresh folds").
  </p><p>
   The fold-text is set to the first line of the folded text unless the fold is a
   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
   </p><pre class="programlisting">\begin{figure}[h]
    \centerline{\psfig{figure=slidercrank.eps,height=6cm}}
    \caption{The Slider Crank Mechanism.}
    \label{fig:slidercrank}
\end{figure}
% a LaTeX comment.
\begin{eqnarray}
    \sin(\pi) = 0
\end{eqnarray}</pre><p>
  </p><p>
   will be shown as:
   </p><pre class="programlisting">+---  5 lines: figure (fig:slidercrank) : The Slider Crank Mechanism. -----
% a LaTeX comment.
+---  3 lines: eqnarray () : \sin(\pi) = 0 --------------------------------</pre><p>
  </p><div class="section" title="8.1 Default Folding Scheme in Latex-Suite"><div class="titlepage"><div><div><h3 class="title"><a id="default-folding"></a>8.1 Default Folding Scheme in Latex-Suite</h3></div></div></div><p>
    By default Latex-Suite creates folds in the following manner:
   </p><pre class="programlisting">\chapter
\section
%%fakesection
    \subsection
        \subsubsection
            \item
                \equation
                \eqnarray
                \figure
                \table
                \footnote</pre><p>
    The indentation shows the "nestedness" of the folding scheme.
    See the <a class="link" href="#customizing-what-to-fold" title="8.2 Customizing what to fold">next section</a> to
    see how you can change this scheme.
   </p></div><div class="section" title="8.2 Customizing what to fold"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-what-to-fold"></a>8.2 Customizing what to fold</h3></div></div></div><p>
    From version 1.6 onwards, the folding in Latex-Suite can be controlled
    to a large extent via a number of global variables.
   </p><div class="section" title="8.2.1 Tex_FoldedSections"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_FoldedSections"></a>8.2.1 Tex_FoldedSections</h4></div></div></div><p>
     This entry defines which sections will be folded. This
     setting is a comma separated list of section names. 
     The default value is:
     </p><pre class="programlisting">part,chapter,section,%%fakesection,
subsection,subsubsection,paragraph</pre><p>
     Each of the entries in the list will fold up a section of the
     corresponding name. The <code class="literal">%%fakesection</code> section is
     provided as a means for the user to group lines into "fake" sections.
     A <code class="literal">%%fakesection</code> is assumed to start on a line which
     begins with the string <code class="literal">%%fakesection</code> and continue
     till the start of the next <code class="literal">\section</code>,
     <code class="literal">\subsection</code> or any other section.
    </p><p>
     See also <a class="link" href="#fold-setting-advanced" title="8.2.5 Advanced Fold setting details">advanced fold
      settings</a>.
    </p></div><div class="section" title="8.2.2 Tex_FoldedEnvironments"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_FoldedEnvironments"></a>8.2.2 Tex_FoldedEnvironments</h4></div></div></div><p>
     This entry defines which environments will be folded. It is a
     comma separated string of words each of which defines a single
     environment. The default setting is
     </p><pre class="programlisting">verbatim,comment,eq,gather,
align,figure,table,thebibliography,
keywords,abstract,titlepage</pre><p>
     The words need not be standard Latex environments. You can
     add any word you like. Also, each word will fold up all
     environments whose name begins with that word. For example, in
     the setting above, the word <code class="literal">"eq"</code> folds up the
     <code class="literal">\begin{equation}</code>,
     <code class="literal">\begin{eqnarray}</code>,
     <code class="literal">\begin{eqnarray*}</code> environments. To avoid
     this, you can replace the word <code class="literal">"eq"</code> with
     <code class="literal">"eq}"</code>.
    </p><p>
     See also <a class="link" href="#fold-setting-advanced" title="8.2.5 Advanced Fold setting details">advanced fold
      settings</a>.
    </p></div><div class="section" title="8.2.3 Tex_FoldedCommands"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_FoldedCommands"></a>8.2.3 Tex_FoldedCommands</h4></div></div></div><p>
     This entry defines which commands will be folded. It is a comma
     separated string of words each of which defines a single command.
     The default setting is empty, i.e no commands are folded.
     The words need not be standard Latex commands. You can use whatever
     words you like. Each word will fold all commands whose name begins
     with that word as in the case of the <a class="link" href="#Tex_FoldedEnvironments" title="8.2.2 Tex_FoldedEnvironments">Tex_FoldedEnvironments</a>
     variable.
    </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      It is very difficult to fold commands reliably because it is very
      difficult to create a regexp which will match a line containing
      unmatched parentheses (or curly brackets), but will not match a line
      containing matched parentheses.
     </p><p>
      Just to make things safer, only lines which start a command but do
      not contain additional curly braces after the command has started are
      folded. In other words, if you wanted to fold the the command
      <code class="literal">"mycommand"</code>, then the  lines
      </p><pre class="programlisting">\mycommand{This is a line
and some more text on the next line
}</pre><p>
      will be folded, but the lines
      </p><pre class="programlisting">\mycommand{This is a \textbf{line}
and some more text
}</pre><p>
      will not be folded. This is a bug which is very difficult to fix.
     </p></div><p>
     See also <a class="link" href="#fold-setting-advanced" title="8.2.5 Advanced Fold setting details">advanced fold
      settings</a>.
    </p></div><div class="section" title="8.2.4 Tex_FoldedMisc"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_FoldedMisc"></a>8.2.4 Tex_FoldedMisc</h4></div></div></div><p>
     This entry defines fold syntax for certain items which do not
     naturally fit into the section, environment of command lists. It is a
     comma separated list of words. The default value is:
     </p><pre class="programlisting">item,preamble,&lt;&lt;&lt;</pre><p>
     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
       Unlike the other Tex_FoldedXXXX variables, the words in this setting
       are limited to take values from the following list:
      </p><p>
       </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Value</th><th>Meaning</th></tr></thead><tbody><tr><td>comments</td><td>Folds up contiguous blocks of comments</td></tr><tr><td>item</td><td>Folds up the <code class="literal">\item</code>s within list
            environments</td></tr><tr><td>preamble</td><td>Folds up the preamble of a document. (The part between
            the <code class="literal">\documentclass</code> command and the
            <code class="literal">\begin{document}</code> environment)</td></tr><tr><td><code class="literal">&lt;&lt;&lt;</code></td><td>Folds defined manually by the user using the
            <code class="literal">&lt;&lt;&lt;</code> and
            <code class="literal">&gt;&gt;&gt;</code> strings as fold-markers.</td></tr></tbody></table></div><p>
       Any other words in the <code class="literal">Tex_FoldedMisc</code> setting
       are silently ignored.
      </p></div><p>
    </p><p>
     See also <a class="link" href="#fold-setting-advanced" title="8.2.5 Advanced Fold setting details">advanced fold
      settings</a>.
    </p></div><div class="section" title="8.2.5 Advanced Fold setting details"><div class="titlepage"><div><div><h4 class="title"><a id="fold-setting-advanced"></a>8.2.5 Advanced Fold setting details</h4></div></div></div><p>
     The order of the words in the <code class="literal">Tex_FoldedXXXX</code>
     variables is <span class="emphasis"><em>important</em></span>. The order defines the
     order in which the folds are nested. For example, the value
     <code class="literal">"subsection,section"</code> for the
     <code class="literal">Tex_FoldedSections</code> variable will not fold any
     subsections at all. This is because the folds are created in the
     <span class="emphasis"><em>reverse</em></span> order in which they occur in the
     <code class="literal">Tex_FoldedSections</code> setting and also, once a fold is
     created, the interior of the fold is not examined for creating
     additional folds. In the above case, this means that a
     <code class="literal">\section</code> is folded first and then its interior is
     not examined further. The correct value should have been
     <code class="literal">"section,subsection"</code>
    </p><a id="fold-setting-adding"></a><p>
     Each of the fold setting variables
     <code class="literal">Tex_FoldedSections</code>,
     <code class="literal">Tex_FoldedEnvironments</code> etc., as explained previously
     is a comma separated string of variables. However, to make it easier
     to <span class="emphasis"><em>add</em></span> to the default settings without having to
     repeat the whole default setting again, Latex-Suite uses the following logic
     in forming the complete setting string from the
     <code class="literal">Tex_FoldedXXXX</code> variables. If the variable starts with
     a comma, then <code class="literal">Tex_FoldedXXXX</code> is added to the end of
     the default string rather than replacing it. Similarly, if it ends
     with a comma, then it will be prepended to the beginning of the
     default setting rather than replacing it.
    </p><p>
     For example, if <code class="literal">Tex_FoldedEnvironments</code> is set to the
     string <code class="literal">"myenv"</code>, then only an environment of the
     form <code class="literal">\begin{myenv}</code> will be folded. However, if the
     <code class="literal">Tex_FoldedEnvironments</code> setting is
     <code class="literal">",myenv"</code>, then the <code class="literal">\begin{myenv}</code>
     environment will be folded after all other environments in the default
     setting have been folded. On the other hand if
     <code class="literal">Tex_FoldedEnvironments</code> is of the form
     <code class="literal">"myenv,"</code>, the <code class="literal">\begin{myenv}</code>
     environment will be folded before the rest of the environments in the
     default setting.
    </p></div></div><div class="section" title="8.3 Editing the folding.vim file directly"><div class="titlepage"><div><div><h3 class="title"><a id="editing-folding"></a>8.3 Editing the folding.vim file directly</h3></div></div></div><p>
    If you are using version 1.5 of Latex-Suite or older, you will need to
    directly edit the
    <code class="literal">$VIM/ftplugin/latex-suite/folding.vim</code> file if you
    wish to modify the folding scheme.  You will need to modify the
    function <code class="literal">MakeTexFolds()</code> defined in that file to
    modify the fold syntax.  <code class="literal">MakeTexFolds</code> makes a number
    of calls to <code class="literal">AddSyntaxFoldItem</code>. Each such call
    defines a new "fold item". The order in which these calls are made
    defines how the folds are nested. For example, if you desire an
    <code class="literal">figure</code> environment to be nested within a
    <code class="literal">section</code>, then you should define the fold for the
    <code class="literal">figure</code> first. The syntax of
    <code class="literal">AddSyntaxFoldItem</code> is as follows:
    </p><pre class="programlisting">AddSyntaxFoldItem(startpat, endpat, startoff, endoff [, startskip, endskip])</pre><p>
    If the last two arguments are omitted, then they are assumed to default
    to the empty strings <code class="literal">''</code>.
    The explanation for each argument is as follows:
   </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Argument</th><th>Explanation</th></tr></thead><tbody><tr><td><code class="literal">startpat</code></td><td>a line matching this pattern defines
        the beginning of a fold.
       </td></tr><tr><td>
        <code class="literal">endpat</code>
       </td><td>
        a line matching this pattern defines the end of a fold.
       </td></tr><tr><td><code class="literal">startoff</code></td><td>
        this is the offset from the starting line at which folding will
        actually start
       </td></tr><tr><td><code class="literal">endoff</code></td><td>
        like <code class="literal">startoff</code>, but gives the offset of the
        actual fold end from the line satisfying <code class="literal">endpat</code>.
        <code class="literal">startoff</code> and <code class="literal">endoff</code> are
        necessary when the folding region does not have a specific end
        pattern corresponding to a start pattern. for example in LaTeX,
        <code class="literal">\section{Section Name}</code> defines the beginning of
        a section, but there is no command which specifically ends a
        section. Thus a <code class="literal">\section</code>  is assumed to end 1
        line <span class="emphasis"><em>before</em></span> another section starts.
       </td></tr><tr><td>
        <code class="literal">startskip</code>  
       </td><td>
        A Pattern Which Defines The Beginning Of A "Skipped" Region.

        For example, suppose we define a \itemize fold as follows:
        <pre class="programlisting"><code class="literal">startpat</code> =  '^\s*\\item',
<code class="literal">endpat</code> = '^\s*\\item\|^\s*\\end{\(enumerate\|itemize\|description\)}',
<code class="literal">startoff</code> = 0,
<code class="literal">endoff</code> = -1</pre>

        This defines a fold which starts with a line beginning with an
        <code class="literal">\item</code> and ending one line before a line beginning with an
        <code class="literal">\item</code> or <code class="literal">\end{enumerate}</code> etc.

        Then, as long as <code class="literal">\item</code>'s are not nested things are fine.
        However, once items begin to nest, the fold started by one
        <code class="literal">\item</code> can end because of an
        <code class="literal">\item</code> in an <code class="literal">\itemize</code>
        environment within this <code class="literal">\item</code>. i.e, the following can happen:

        <pre class="programlisting">\begin{itemize}
\item Some text                         &lt;------- fold will start here
This item will contain a nested item
\begin{itemize}                         &lt;----- fold will end here because next line contains \item...
\item Hello  
\end{itemize}                           &lt;----- ... instead of here.
\item Next item of the parent itemize  
\end{itemize}</pre>

        Therefore, in order to completely define a folding item which
        allows nesting, we need to also define a "skip" pattern.
        <code class="literal">startskip</code> and end skip do that.
        Leave '' when there is no nesting.
       </td></tr><tr><td>
        <code class="literal">endskip</code>  
       </td><td>
        the pattern which defines the end of the "skip" pattern for
        nested folds.
       </td></tr></tbody></table></div><div class="note" title="Example 1" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Example 1</h3><p>
     A syntax fold region for the latex section is defined with the
     following arguments to <code class="literal">AddSyntaxFoldItem</code>:
     </p><pre class="programlisting">startpat = "\\section{"
endpat   = "\\section{"
startoff = 0
endoff   = -1
startskip = ''
endskip = ''</pre><p>
     Note that the start and end patterns are thus the same and
     <code class="literal">endoff</code> has a negative value to capture the effect
     of a section ending one line before the next starts.
    </p></div><div class="note" title="Example 2" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Example 2</h3><p>
     A syntax fold region for the \itemize environment is:
     </p><pre class="programlisting">startpat = '^\s*\\item',
endpat = '^\s*\\item\|^\s*\\end{\(enumerate\|itemize\|description\)}',
startoff = 0,
endoff = -1,
startskip = '^\s*\\begin{\(enumerate\|itemize\|description\)}',
endskip = '^\s*\\end{\(enumerate\|itemize\|description\)}'</pre><p>
     Note the use of <code class="literal">startskip</code> and
     <code class="literal">endskip</code> to allow nesting.
    </p></div></div></div><div class="section" title="9 Multiple file LaTeX projects"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-project"></a>9 Multiple file LaTeX projects</h2></div></div></div><a id="latex-project-example"></a><p>
   Many LaTeX projects contain multiple source files which are
   <code class="literal">\include</code>d from a master file. A typical example of
   this situation is a directory layout such as the following
  </p><p>
   </p><pre class="programlisting">thesis/
    main.tex
    abstract.tex
    intro/
        intro.tex
        figures/
            fig1.eps
            fig2.eps
    chapter1/
        chap1.tex
        figures/
            fig1.eps
    conclusion/
        conclusion.tex
        figures/</pre><p> 
  </p><p>
   In the above case, <code class="literal">main.tex</code> will typically look like
  </p><p>
    </p><pre class="programlisting">% file: main.tex
\documentclass{report}
\begin{document}

\input{abstract.tex}
\input{intro/intro.tex}
\input{chapter1/chap1.tex}
\input{conclusion/conclusion.tex}

\end{document}</pre><p>
  </p><p>
   <a id="latex-master-file-specification"></a> In such situations, you will
   need to convey to Latex-Suite that <code class="literal">main.tex</code> is the main file
   which <code class="literal">\input</code>s the other files. This is done by creating
   an empty file called <code class="literal">main.tex.latexmain</code> in the same
   directory in which <code class="literal">main.tex</code> resides. This file is called
   the <span class="emphasis"><em>master file</em></span> in this manual. See <a class="link" href="#Tex_MainFileExpression">Tex_MainFileExpression</a> for an
   alternative way of specifying the master file.
  </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    Here <code class="literal">main.tex.latexmain</code> is (obviously) a different
    file from <code class="literal">main.tex</code> itself.
    <code class="literal">main.tex</code> need not be renamed. This ofcourse
    restricts each directory to have a single master file.
   </p></div><p>
   Each time Latex-Suite opens a new LaTeX file, it will try to see if it is
   part of a multiple file project by searching upwards (to the root of
   the file-system) from the current file's directory to see if it finds a
   file of the form <code class="literal">*.latexmain</code>. If such a file is
   found, then it is considered that the current file is part of a larger
   project. The name of the LaTeX master file is inferred directly from
   the first part of the <code class="literal">*.latexmain</code> file as described
   in the example above.
  </p><div class="section" title="9.1 Latex-Suite project settings"><div class="titlepage"><div><div><h3 class="title"><a id="latex-project-settings"></a>9.1 Latex-Suite project settings</h3></div></div></div><p>
    If a <a class="link" href="#latex-master-file" title="9.2 Specifying which file to compile">master file</a> is found,
    then Latex-Suite <code class="literal">:source</code>s the file. Thus this file needs to
    contain valid Vim commands. This file is typically used to store
    project specific settings.
   </p><p>
    Some typical per-project settings which are best put in the master file
    are
    </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="link" href="#Tex_ProjectSourceFiles" title="11.5.4 g:Tex_ProjectSourceFiles">Tex_ProjectSourceFiles</a></td></tr></table><p>
   </p></div><div class="section" title="9.2 Specifying which file to compile"><div class="titlepage"><div><div><h3 class="title"><a id="latex-master-file"></a>9.2 Specifying which file to compile</h3></div></div></div><p>
    In the example described <a class="link" href="#latex-project-example">previously</a>, if you are editing
    <code class="literal">intro/intro.tex</code> and press <code class="literal">\ll</code>,
    then you still want Latex-Suite to compile <code class="literal">main.tex</code>,
    because <code class="literal">intro/intro.tex</code> is merely a fragment which
    is <code class="literal">\input</code>'ed into <code class="literal">main.tex</code>. If
    the master file is already specified using the
    <code class="literal">*.latexmain</code> convention described <a class="link" href="#latex-project-example">previously</a>, then Latex-Suite will automatically
    compile the master file when you are editing any of its
    <code class="literal">\input</code>'ed fragments. Thus pressing
    <code class="literal">\ll</code> while editing <code class="literal">intro/intro.tex</code>
    will compile <code class="literal">main.tex</code>.
   </p><a id="Tex_MainFileExpression"></a><p>
    If you wish to use some different logic to specify the main file name,
    you can specify a custom expression via the
    <code class="literal">Tex_MainFileExpression</code> variable. This is a string
    containing a valid vim expression. In addition, you can use a variable
    <code class="literal">modifier</code> which is in the format used for
    <code class="literal">|filename-modifiers|</code>, for example,
    <code class="literal">':p:h'</code>. You should utilize this variable to modify
    the filename of the main file.
    </p><pre class="programlisting">let g:Tex_MainFileExpression = 'MainFile(modifier)'
function! MainFile(fmod)
    if glob('*.latexmain') != ''
        return fnamemodify(glob('*.latexmain'), a:fmod)
    else
        return ''
    endif
endif</pre><p>
   </p></div></div><div class="section" title="10 Latex-Suite Commands and Maps"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-suite-commands-maps"></a>10 Latex-Suite Commands and Maps</h2></div></div></div><p>
   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.
  </p><div class="section" title="10.1 Latex-Suite Maps"><div class="titlepage"><div><div><h3 class="title"><a id="latex-suite-maps"></a>10.1 Latex-Suite Maps</h3></div></div></div><a id="remapping-latex-suite-keys"></a><p>
    Most of the mappings used in Latex-Suite can be mapped to a different key
    combination to suit your particular needs. An example best explains the
    procedure for doing this. Suppose you want to remap the
    <code class="literal">&lt;C-j&gt;</code> key which Latex-Suite (actually imaps.vim) uses
    to jump to the next placeholder. To do this, you first need to find out
    which <code class="literal">&lt;Plug&gt;</code> mapping
    <code class="literal">&lt;C-j&gt;</code> is derived from. You will need to look
    at the relevant section of this manual to do this. For example, the
    section <a class="link" href="#customize-imap-maps" title="10.1.1 IMAP mappings">IMAP mappings</a> has
    the information that the <code class="literal">&lt;C-j&gt;</code> key is derived
    from <code class="literal">&lt;Plug&gt;IMAP_JumpForward</code>. Therefore to
    remap the <code class="literal">&lt;C-j&gt;</code> key to say
    <code class="literal">&lt;C-space&gt;</code>, you will need to put a
    statement like the following in your <code class="literal">~/.vimrc</code>.
    </p><pre class="programlisting">imap &lt;C-space&gt; &lt;Plug&gt;IMAP_JumpForward</pre><p>
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     To change the <code class="literal">IMAP</code> mappings which affect jumping
     between placeholders, the <code class="literal">map</code> statement above has
     to be placed in your <code class="literal">~/.vimrc</code>. For other mappings
     you can place the <code class="literal">map</code> statement in your
     <code class="literal">$VIM/ftplugin/tex.vim</code> file.  The reason for this is
     that the <code class="literal">&lt;C-j&gt;</code> maps are created in
     <code class="literal">plugin/imaps.vim</code>, which is sourced as soon as Vim
     starts before sourcing any ftplugin files.
    </p></div><div class="section" title="10.1.1 IMAP mappings"><div class="titlepage"><div><div><h4 class="title"><a id="customize-imap-maps"></a>10.1.1 IMAP mappings</h4></div></div></div><p>
     These mappings are utilized for jumping between placeholders as
     described <a class="link" href="#place-holders" title="Place Holders">here</a>. See the <a class="link" href="#latex-suite-maps" title="10.1 Latex-Suite Maps">parent section</a> to find out how to
     use this information to change the default maps.
    </p><a id="Plug_IMAP_JumpForward"></a><a id="Plug_IMAP_JumpBack"></a><a id="Plug_IMAP_DeleteAndJumpForward"></a><a id="Plug_IMAP_DeleteAndJumBack"></a><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Plug map</th><th>Default Key</th></tr></thead><tbody><tr><td><code class="literal">&lt;Plug&gt;IMAP_JumpForward</code></td><td><code class="literal">&lt;C-j&gt;</code></td></tr><tr><td><code class="literal">&lt;Plug&gt;IMAP_JumpBack</code></td><td>(none)</td></tr><tr><td><code class="literal">&lt;Plug&gt;IMAP_DeleteAndJumpForward</code></td><td>(none)</td></tr><tr><td><code class="literal">&lt;Plug&gt;IMAP_DeleteAndJumpBack</code></td><td>(none)</td></tr></tbody></table></div><p>
     <code class="literal">&lt;Plug&gt;IMAP_JumpForward</code> takes you to the
     location of the next <a class="link" href="#place-holders" title="Place Holders">place-holder</a>.
    </p><p>
     <code class="literal">&lt;Plug&gt;IMAP_JumpBack</code> takes you to the previous
     <a class="link" href="#place-holders" title="Place Holders">place-holder</a>.
    </p><p>
     <code class="literal">&lt;Plug&gt;IMAP_DeleteAndJumpForward</code> deletes the
     presently selected place-holder and jumps to the next place-holder
     irrespective of whether the present placeholder is empty or not and
     ignoring the value of place-holder settings like <a class="link" href="#Imap_DeleteEmptyPlaceHolders" title="11.2.3 g:Imap_DeleteEmptyPlaceHolders"><code class="literal">g:Imap_DeleteEmptyPlaceHolders</code></a>
     and <a class="link" href="#Imap_StickyPlaceHolders" title="11.2.4 g:Imap_StickyPlaceHolders"><code class="literal">g:Imap_StickyPlaceHolders</code></a>
    </p><p>
     <code class="literal">&lt;Plug&gt;IMAP_DeleteAndJumpBack</code> deletes the
     presently selected place-holder and jumps to the previous place-holder
     irrespective of whether the present placeholder is empty or not and
     ignoring the value of place-holder settings like <a class="link" href="#Imap_DeleteEmptyPlaceHolders" title="11.2.3 g:Imap_DeleteEmptyPlaceHolders"><code class="literal">g:Imap_DeleteEmptyPlaceHolders</code></a>
     and <a class="link" href="#Imap_StickyPlaceHolders" title="11.2.4 g:Imap_StickyPlaceHolders"><code class="literal">g:Imap_StickyPlaceHolders</code></a>
    </p></div><div class="section" title="10.1.2 Alt-Key mappings"><div class="titlepage"><div><div><h4 class="title"><a id="customize-alt-key-maps"></a>10.1.2 Alt-Key mappings</h4></div></div></div><p>
     These mappings are are described in the section <a class="link" href="#altkey-mappings" title="3.10 Alt Key Macros">Alt key macros</a>. See <a class="link" href="#remapping-latex-suite-keys">the parent section</a> to see
     how to use the following information to remap keys.
    </p><a id="Plug_Tex_MathBF"></a><a id="Plug_Tex_MathCal"></a><a id="Plug_Tex_LeftRight"></a><a id="Plug_Tex_InsertItemOnThisLine"></a><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Plug Mapping</th><th>Default Key</th></tr></thead><tbody><tr><td><code class="literal">&lt;Plug&gt;Tex_MathBF</code></td><td><code class="literal">&lt;Alt-B&gt;</code></td></tr><tr><td><code class="literal">&lt;Plug&gt;Tex_MathCal</code></td><td><code class="literal">&lt;Alt-C&gt;</code></td></tr><tr><td><code class="literal">&lt;Plug&gt;Tex_LeftRight</code></td><td><code class="literal">&lt;Alt-L&gt;</code></td></tr><tr><td><code class="literal">&lt;Plug&gt;Tex_InsertItemOnThisLine</code></td><td><code class="literal">&lt;Alt-I&gt;</code></td></tr></tbody></table></div></div></div><div class="section" title="10.2 Latex Suite Commands"><div class="titlepage"><div><div><h3 class="title"><a id="latex-suite-commands"></a>10.2 Latex Suite Commands</h3></div></div></div><div class="section" title="10.2.1 :TMacro [{macro}]"><div class="titlepage"><div><div><h4 class="title"><a id="TMacro"></a>10.2.1 :TMacro [{macro}]</h4></div></div></div><p>
    When used without any arguments lists all available macros defined
    in runtime ftplugin/latex-suite/macros/ directories and prompts you
    to choose one of them. With one argument |:read| this macro under
    cursor position. With more than one argument it will not work :) In
    Vim &gt;= 6.2 works completion of names of macros (see 'wildmenu',
    'wildmode' for more about command-line completion).
    </p></div><div class="section" title="10.2.2 :TMacroEdit [{macro}]"><div class="titlepage"><div><div><h4 class="title"><a id="TMacroEdit"></a>10.2.2 :TMacroEdit [{macro}]</h4></div></div></div><p>
    Splits window for editing {macro}. When used without any arguments
    lists all available macros defined in runtime
    ftplugin/latex-suite/macros/ directories and prompt you to choose
    one of them.  When you try to edit {macro} not from local directory
    Latex-Suite will copy it to your local directory with suffix
    "-local". If local copy already exists Latex-Suite prompt for
    overwriting it.  In Vim &gt;= 6.2 works completion of names of macros
    (see 'wildmenu', 'wildmode' for more about command-line completion).
    </p></div><div class="section" title="10.2.3 :TMacroNew"><div class="titlepage"><div><div><h4 class="title"><a id="TMacroNew"></a>10.2.3 :TMacroNew</h4></div></div></div><p>
     Splits window to write new macro. Directory in new buffer is
     locally changed to Latex-Suite/macros/.
    </p></div><div class="section" title="10.2.4 :TMacroDelete [{macro}]"><div class="titlepage"><div><div><h4 class="title"><a id="TMacroDelete"></a>10.2.4 :TMacroDelete [{macro}]</h4></div></div></div><p>
    Delets {macro} from your local ftplugin/latex-suite/macros/
    directory.  When used without any arguments lists all available
    macros defined in Latex-Suite/macros/ directory and prompt you to
    choose one of them.  When you choose to delete {macro} which is not
    in your local directory Latex-Suite will refuse to delete it.  In
    Vim &gt;= 6.2 works completion of names of macros (see 'wildmenu',
    'wildmode' for more about command-line completion)
    </p></div><div class="section" title="10.2.5 :TPackage [{package, ...}]"><div class="titlepage"><div><div><h4 class="title"><a id="TPackage"></a>10.2.5 :TPackage [{package, ...}]</h4></div></div></div><p>
     When used without any arguments lists name of the packages for
     which support is available. If you are using Vim GUI and have
     <code class="literal">Tex_Menus</code> set to 1, then it will list all files
     found in the <code class="literal">$VIM/ftplugin/latex-suite/packages</code>
     directory. Otherwise, Latex-Suite will list files found in the
     <code class="literal">$VIM/ftplugin/latex-suite/dictionaries</code> directory.
     Choosing a file from the list will insert a
     </p><pre class="programlisting">\usepackage[&lt;++&gt;]{&lt;packname&gt;}</pre><p> line into the
     buffer at the current cursor location. For Vim 6.2 and above, you
     can use command-line completion to choose a package file. You can also
     call <code class="literal">TPackage</code> with one or more package names
     separated with spaces in which case, Latex-Suite will insert
     <code class="literal">\usepackage</code> lines for each of them in turn.
    </p><p>
     After inserting the <code class="literal">\usepackage</code> line(s), Latex-Suite will
     support it (them) in various ways as described in the section <a class="link" href="#package-actions" title="4.2 Actions taken for supported packages">Actions taken for supported
      packages</a>.
    </p></div><div class="section" title="10.2.6 :TPackageUpdate"><div class="titlepage"><div><div><h4 class="title"><a id="TPackageUpdate"></a>10.2.6 :TPackageUpdate</h4></div></div></div><p>
     This command `reads' name of package under cursor and turns on
     possible support.
    </p></div><div class="section" title="10.2.7 :TPackageUpdateAll"><div class="titlepage"><div><div><h4 class="title"><a id="TPackageUpdateAll"></a>10.2.7 :TPackageUpdateAll</h4></div></div></div><p>
     After issuing this command latexSuite scans the file in
     looking for not declared packages, removing not needed entries
     from Packages menu and turning off not necessary packages'
     dictionaries.
    </p></div><div class="section" title="10.2.8 :TTemplate [{template}]"><div class="titlepage"><div><div><h4 class="title"><a id="TTemplate"></a>10.2.8 :TTemplate [{template}]</h4></div></div></div><p>
     When used without any arguments lists all available templates
     from latex-suite/templates/ directory and prompts to choose
     one of them.
     With one argument :0|read| {template} file.
     With more than one argument it will not work :)
     In Vim &gt;= 6.2 works completion of names of macros (see 'wildmenu',
     'wildmode' for more about command-line completion)
    </p></div><div class="section" title="10.2.9 :TSection [{argument}]"><div class="titlepage"><div><div><h4 class="title"><a id="TSection"></a>10.2.9 :TSection [{argument}]</h4></div></div></div><p>
     Used without any arguments inserts last section type
     (|latex-sectioning|).
     Accepts arguments:
     n&gt;     inserts section name in &lt;n&gt; logical level.
     Levels are:
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>0</td><td>part</td></tr><tr><td>1</td><td>chapter</td></tr><tr><td>2</td><td>section</td></tr><tr><td>3</td><td>subsection</td></tr><tr><td>4</td><td>subsubsection</td></tr><tr><td>5</td><td>paragraph</td></tr><tr><td>6</td><td>subparagraph</td></tr></tbody></table></div><p>

     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>
          +&lt;n&gt;    
         </td><td>
          inserts section name &lt;n&gt; logical levels above the last
          used comand
         </td></tr><tr><td>
          -&lt;n&gt;    
         </td><td>
          inserts section name &lt;n&gt; logical levels below the last
          used comand
         </td></tr><tr><td>
          +       
         </td><td>
          inserts section name one logical level below the last
          used command (equal to +1).
         </td></tr><tr><td>
          ++      
         </td><td>
          inserts section name two logical levels below the last
          used command (equal to +2).
         </td></tr><tr><td>
          -       
         </td><td>
          inserts section name one logical level over the last
          used command (equal to -1).
         </td></tr><tr><td>
          --      
         </td><td>
          inserts section name two logical levels over the last
          used command (equal to -2).
         </td></tr></tbody></table></div><p>

     Command accepts also latexSuite mappings (|latex-macros|)
     without preceding S and in lowercase:
     </p><pre class="programlisting">:TSection pa</pre><p>
     will result in <code class="literal">\part{}</code>. It is possible to use full names of
     sections: <code class="literal">:TSection part</code>
    </p></div><div class="section" title="10.2.10 :TSectionAdvanced"><div class="titlepage"><div><div><h4 class="title"><a id="TSectionAdvanced"></a>10.2.10 :TSectionAdvanced</h4></div></div></div><p>
     Accepts the same arguments as |TSection| but leads to a couple
     of questions (whether you want to include the section in the
     table of contents, whether there is a shorter name for the
     table of contents) and then creates a more intelligent
     template.
    </p></div><div class="section" title="10.2.11 :TLook"><div class="titlepage"><div><div><h4 class="title"><a id="TLook"></a>10.2.11 :TLook</h4></div></div></div><p>
     Accepts one argument. Will look through .tex files in
     directory of edited file for argument. It can be regexp. You
     don't have to enclose argument in "". &lt;cr&gt; takes you to
     location. Other keys work as described in |latex-viewer|.
     Note: TLook uses :grep command and is using 'grepprg'. Its
     regular expressions can be different from those of Vim.
    </p></div><div class="section" title="10.2.12 :TLookBib"><div class="titlepage"><div><div><h4 class="title"><a id="TLookBib"></a>10.2.12 :TLookBib</h4></div></div></div><p>
     Accepts one argument. Will look through .bib files in
     directory of edited file for argument. It can be regexp. You
     don't have to enclose argument in "". &lt;cr&gt; takes you to
     location. Other keys work as described in |latex-viewer|.
    </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      TLookBib uses :grep command and is using 'grepprg'.  Its
      regular expressions can be different from those of Vim.
     </p></div></div><div class="section" title="10.2.13 :TLookAll"><div class="titlepage"><div><div><h4 class="title"><a id="TLookAll"></a>10.2.13 :TLookAll</h4></div></div></div><p>
     Accepts one argument. Will look through all files in directory
     of edited file for argument. It can be regexp. You don't have
     to enclose argument in "". &lt;cr&gt; takes you to location. Other
     keys work as described in |latex-viewer|.
     Note: TLook uses :grep command and is using 'grepprg'.  Its
     regular expressions can be different from those of Vim.
    </p></div><div class="section" title="10.2.14 :TPartComp"><div class="titlepage"><div><div><h4 class="title"><a id="TPartComp"></a>10.2.14 :TPartComp</h4></div></div></div><p>
     No argument allowed but accepts range in all formats. Define
     fragment of interest with :'a,'b, :/a/,/b/, :'&lt;,'&gt; or :20,30.
     All other rules of compilation apply.
    </p></div><div class="section" title="10.2.15 :TPartView"><div class="titlepage"><div><div><h4 class="title"><a id="TPartView"></a>10.2.15 :TPartView</h4></div></div></div><p>
     Show last compiled fragment. All rules of viewing apply but
     |latex-searching|.
    </p></div><div class="section" title="10.2.16 :Tshortcuts [{arg}]"><div class="titlepage"><div><div><h4 class="title"><a id="Tshortcuts"></a>10.2.16 :Tshortcuts [{arg}]</h4></div></div></div><p>
     Show shortcuts in terminal (not using menu). Without {arg}
     you will see simple menu prompting for one of them. Possible
     arguments:
     </p><div class="informaltable"><table border="0"><colgroup><col></col><col></col></colgroup><tbody><tr><td>g</td><td>General shortcuts</td></tr><tr><td>e</td><td>Environment shortcuts</td></tr><tr><td>f</td><td>Font shortcuts</td></tr><tr><td>s</td><td>Section shortcuts</td></tr><tr><td>m</td><td>Math shortcuts</td></tr><tr><td>a</td><td>All shortcuts</td></tr></tbody></table></div><p>
    </p></div></div></div><div class="section" title="11 Customizing Latex-Suite"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="customizing-latex-suite"></a>11 Customizing Latex-Suite</h2></div></div></div><p>
   Customizing Latex-Suite is done by defining certain global variables in
   <code class="literal">$VIM/ftplugin/tex.vim</code>, where
   <code class="literal">$VIM</code> corresponds to <code class="literal">~/.vim</code> for *nix
   machines and <code class="literal">~/vimfiles</code> for windows machines. This file
   is not part of the Latex-Suite distribution. You will need to create this file
   yourself (or modify it if it exists) if
   you need to change any default settings. Since this file is not
   included as part of the Latex-Suite distribution, it will not be over-written in
   subsequent updates.
  </p><p>
   The default settings in Latex-Suite are defined in
   <code class="literal">$VIM/ftplugin/latex-suite/texrc</code>. Please take a look at
   this file if you find this documentation incomplete or confusing. That file
   is also well documented.
  </p><p>
   This chapter describes the various settings which effect Latex-Suite and their
   default values. The settings are broken up into sections according to the
   behavior which they influence. 
  </p><div class="section" title="11.1 General Settings"><div class="titlepage"><div><div><h3 class="title"><a id="ls-general-purpose-settings"></a>11.1 General Settings</h3></div></div></div><div class="section" title="11.1.1 Tex_Debug"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Debug"></a>11.1.1 Tex_Debug</h4></div></div></div><p>
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>boolean</td></tr><tr><td>Default Value</td><td><code class="literal">0</code></td></tr></tbody></table></div><p>
     </p><p>
      If set to 1, then Latex-Suite will create certain global debug
      statements which can be printed by doing
      </p><pre class="programlisting">:call Tex_PrintDebug()</pre><p>
     </p><p>
    </p></div><div class="section" title="11.1.2 Tex_UsePython"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_UsePython"></a>11.1.2 Tex_UsePython</h4></div></div></div><p>
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     </p><p>
      If Latex-Suite detects that your vim is python enabled (using
      <code class="literal">has('python')</code>), then it tries to use python in
      certain places to speed things up. If this misbehaves, you can set
      this to zero, in which case, Latex-Suite will use vimscript to accomplish
      the same.
     </p><p>
    </p></div></div><div class="section" title="11.2 Place-Holder Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-place-holders"></a>11.2 Place-Holder Customization</h3></div></div></div><p>
    Latex-Suite uses <a class="link" href="#place-holders" title="Place Holders">place-holders</a> to minimize
    using the movement keys while typing. The following settings affect how
    place-holders are used.
   </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     These setting need to be set in your <code class="literal">~/.vimrc</code>, not
     <code class="literal">$VIM/ftplugin/tex.vim</code> because these settings affect
     the behavior of <code class="literal">imaps.vim</code>, which is a global plugin,
     not a file-type plugin.
    </p></div><div class="section" title="11.2.1 g:Imap_UsePlaceHolders"><div class="titlepage"><div><div><h4 class="title"><a id="Imap_UsePlaceHolders"></a>11.2.1 g:Imap_UsePlaceHolders</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     Setting this to zero completely disables using place-holders.
    </p></div><div class="section" title="11.2.2 g:Imap_PlaceHolderStart &amp; g:Imap_PlaceHolderEnd"><div class="titlepage"><div><div><h4 class="title"><a id="Imap_PlaceHolderStart"></a>11.2.2 g:Imap_PlaceHolderStart &amp; g:Imap_PlaceHolderEnd</h4></div></div></div><a id="Imap_PlaceHolderEnd"></a><div class="informaltable"><table border="1"><colgroup><col></col><col></col><col></col></colgroup><thead><tr><th>Setting</th><th>Type</th><th>Value</th></tr></thead><tbody><tr><td><code class="literal">Imap_PlaceHolderStart</code></td><td>String</td><td><code class="literal">'&lt;+'</code></td></tr><tr><td><code class="literal">Imap_PlaceHolderEnd</code></td><td>String</td><td><code class="literal">'+&gt;'</code></td></tr></tbody></table></div><p>
     These settings affect the strings displayed at the beginning and end of
     the place-holder string. Set these strings to a value different than a
     commonly occurring sequence of characters. 
    </p><div class="note" title="TIP" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">TIP</h3><p>
      If you use the <code class="literal">latin1</code> encoding and do not type in
      french, then you can set these strings to the <code class="literal">\xab</code>
      and <code class="literal">\xbb</code> characters (the french quotation marks).
     </p></div></div><div class="section" title="11.2.3 g:Imap_DeleteEmptyPlaceHolders"><div class="titlepage"><div><div><h4 class="title"><a id="Imap_DeleteEmptyPlaceHolders"></a>11.2.3 g:Imap_DeleteEmptyPlaceHolders</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     When set to one, non-descriptive or empty place-holders are deleted on
     pressing <code class="literal">&lt;Ctrl-J&gt;</code>.
    </p></div><div class="section" title="11.2.4 g:Imap_StickyPlaceHolders"><div class="titlepage"><div><div><h4 class="title"><a id="Imap_StickyPlaceHolders"></a>11.2.4 g:Imap_StickyPlaceHolders</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     When set to 1, in visual mode, <code class="literal">&lt;Ctrl-J&gt;</code> takes
     you to the next placeholder without deleting the current placeholder.
    </p></div></div><div class="section" title="11.3 Macro Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-macros"></a>11.3 Macro Customization</h3></div></div></div><div class="section" title="11.3.1 Tex_Env_name"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Env_name"></a>11.3.1 Tex_Env_name</h4></div></div></div><p>
      If you wish to wish to expand certain environments differently from
      the way Latex-Suite does it, you can define custom expansions using global
      variables of the form <code class="literal">Tex_Env_{name}</code> where
      <code class="literal">name</code> corresponds to the environment.
     </p><p>
      For example, if you press <code class="literal">&lt;F5&gt;</code> after typing
      <code class="literal">theorem</code>, Latex-Suite will by default expand it to
      </p><pre class="programlisting">\begin{theorem}
     \label{&lt;++&gt;}&lt;++&gt;
\end{theorem}&lt;++&gt;</pre><p>
       However, if you wish change this to
      </p><pre class="programlisting">\begin{theorem}
     &lt;++&gt;
\end{theorem}&lt;++&gt;</pre><p>
       then define the following variable
      </p><pre class="programlisting">let g:Tex_Env_theorem = "\\begin{theorem}\&lt;CR&gt;&lt;++&gt;\&lt;CR&gt;\\end{theorem}"</pre><p>
      </p><p>
      If the expansion uses special keys such as carriage return etc, then
      use double-quotes and use the <code class="literal">"\&lt;key&gt;"</code>
      notation for special keys. Backslashes have to be doubled.
     </p><p>
      You could even use strings returned by functions as the expansion by
      using the <a class="link" href="#IMAP_PutTextWithMovement">IMAP_PutTextWithMovement()</a>
      function.
     </p><p>
      If the name of the environment contains special characters (for
      example, the <code class="literal">eqnarray*</code> environment), then use the
      following form:
      </p><pre class="programlisting">let g:Tex_Env_{'eqnarray*'} = 
        \ "\\begin{eqnarray*}\&lt;CR&gt;&lt;++&gt; &amp;=&amp; &lt;++&gt;\&lt;CR&gt;\\end{eqnarray*}&lt;++&gt;"</pre><p>
       This will make pressing <code class="literal">&lt;F5&gt;</code> after
       <code class="literal">eqnarray*</code> expand to
       </p><pre class="programlisting">\begin{eqnarray*}
    &lt;++&gt; &amp;=&amp; &lt;++&gt;
\end{eqnarray*}&lt;++&gt;</pre><p>
     </p></div><div class="section" title="11.3.2 Tex_Com_name"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Com_name"></a>11.3.2 Tex_Com_name</h4></div></div></div><p>
     If you wish to define new expansions for fast command insertion as
     described <a class="link" href="#latex-command-maps" title="3.2 Command Mappings">here</a>, or redefine
     expansions from the default values in Latex-Suite, you will need to define
     variables of the form <code class="literal">g:Tex_Com_{name}</code> where
     <code class="literal">name</code> is a command name. For example, with the
     setting
     </p><pre class="programlisting">let g:Tex_Com_frac = "\\frac{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt;"</pre><p>
     pressing <code class="literal">&lt;F7&gt;</code> after typing
     <code class="literal">frac</code> will change it to <code class="literal">\frac{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt;</code>
    </p><p>
     See <a class="link" href="#Tex_Env_name" title="11.3.1 Tex_Env_name">Tex_Env_name</a> for additional
     details on how to create this setting in various special
     circumstances.
    </p></div><div class="section" title="11.3.3 Enabling / disabling macros"><div class="titlepage"><div><div><h4 class="title"><a id="macro-enabling"></a>11.3.3 Enabling / disabling macros</h4></div></div></div><p>
     The following variables disable various parts of the macro functionality
     of Latex-Suite. See the links to the relevant sections to see what functionality
     setting each of the variables to zero will take away.
    </p><a id="Tex_EnvironmentMaps"></a><a id="Tex_EnvironmentMenus"></a><a id="Tex_FontMaps"></a><a id="Tex_FontMenus"></a><a id="Tex_SectionMaps"></a><a id="Tex_SectionMenus"></a><div class="informaltable"><table border="1"><colgroup><col></col><col></col><col></col></colgroup><thead><tr><th>Setting</th><th>Link to relevant section</th><th>Default Value</th></tr></thead><tbody><tr><td><code class="literal">g:Tex_EnvironmentMaps
       </code></td><td><a class="link" href="#environment-mappings" title="3.1 Environment Mappings">Environment Mappings</a></td><td>1</td></tr><tr><td><code class="literal">g:Tex_EnvironmentMenus</code></td><td></td><td>1</td></tr><tr><td><code class="literal">g:Tex_FontMaps        </code></td><td><a class="link" href="#font-maps" title="3.3 Font Mappings">Font Mappings</a></td><td>1</td></tr><tr><td><code class="literal">g:Tex_FontMenus       </code></td><td></td><td>1</td></tr><tr><td><code class="literal">g:Tex_SectionMaps     </code></td><td><a class="link" href="#section-mappings" title="3.4 Section Mappings">Section Mappings</a></td><td>1</td></tr><tr><td><code class="literal">g:Tex_SectionMenus    </code></td><td></td><td>1</td></tr></tbody></table></div></div><div class="section" title="11.3.4 g:Tex_UseMenuWizard"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_UseMenuWizard"></a>11.3.4 g:Tex_UseMenuWizard</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">0</code></td></tr></tbody></table></div><p>
     If this variable is set to 1, then when an environment is chosen from the
     menu then for selected environments, Latex-Suite asks a series of
     questions on the command line and inserts a template with the
     corresponding fields already filled in.  Setting this to zero will insert
     a template with <a class="link" href="#place-holders" title="Place Holders">place-holders</a>
     marking off the places where fields need to be filled.
    </p></div><div class="section" title="11.3.5 g:Imap_FreezeImap"><div class="titlepage"><div><div><h4 class="title"><a id="Imap_FreezeImap"></a>11.3.5 g:Imap_FreezeImap</h4></div></div></div><p>
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>boolean</td></tr><tr><td>Default Value</td><td><code class="literal">0</code></td></tr></tbody></table></div><p>
     </p><p>
      This option when set to 1, temporarily freezes Latex-Suite's macro
      expansion. It might be useful when you are using some other keymap
      which is causing excessive macro expansion. Use a buffer-local
      variable of the same name if you wish to affect just the present
      buffer. 
     </p><p>
    </p></div><div class="section" title="11.3.6 g:Tex_CatchVisMapErrors"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_CatchVisMapErrors"></a>11.3.6 g:Tex_CatchVisMapErrors</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     With so many visual maps, its helpful to have a way of catching typing
     errors made in visual mode. What this does is to prompt you to correct
     your visual mode mapping if you start out with <code class="literal"><a class="link" href="#Tex_Leader" title="11.3.8 g:Tex_Leader">g:Tex_Leader</a></code> and then type some
     illegal keys. It basically maps just the <code class="literal">g:Tex_Leader</code>
     character to a function.
    </p></div><div class="section" title="11.3.7 g:Tex_Diacritics"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Diacritics"></a>11.3.7 g:Tex_Diacritics</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">0</code></td></tr></tbody></table></div><p>
     Whether or not you want to use <a class="link" href="#diacritic-mappings" title="3.7 Diacritics">diacritics</a>.
    </p></div><div class="section" title="11.3.8 g:Tex_Leader"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Leader"></a>11.3.8 g:Tex_Leader</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">'`'</code></td></tr></tbody></table></div><p>
     The mappings in Latex-Suite are by default prefixed with the back-tick
     character. For example, <code class="literal">`/</code> inserts
     <code class="literal">\frac{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt;</code> etc. You can change the
     prefix with the following setting.
     <code class="literal">','</code>, <code class="literal">'/'</code>,
     <code class="literal">'`'</code> are preferred values. <code class="literal">''</code> or
     <code class="literal">'\'</code> will lead to a <span class="emphasis"><em>lot</em></span> of
     trouble.
    </p><p>
     g:Tex_Leader is also used for visual mode mappings for fonts.
    </p></div><div class="section" title="11.3.9 g:Tex_Leader2"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Leader2"></a>11.3.9 g:Tex_Leader2</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">','</code></td></tr></tbody></table></div><p>
     In order to avoid clashes between the large number of visual mode macros
     provided, the <a class="link" href="#enclosing-env-threeletter" title="3.1.2.2 Method 2: Using three letter mappings">visual mode
      macros for environments</a> and sections start with a character
     different from <code class="literal">g:Tex_Leader</code>.
    </p></div><div class="section" title="11.3.10 g:Tex_PromptedEnvironments"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_PromptedEnvironments"></a>11.3.10 g:Tex_PromptedEnvironments</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">'eqnarray*,eqnarray,equation,equation*,\[,$$,align,align*'</code></td></tr></tbody></table></div><p>
     This string represents a comma separated list of fields corresponding to
     environments. Pressing <code class="literal">&lt;F5&gt;</code> in insert-mode in
     the body of the document asks you to choose from one of these
     environments to insert.
    </p><p>
     Leaving this string empty will leave the <code class="literal">&lt;F5&gt;</code>
     key unmapped
    </p></div><div class="section" title="11.3.11 g:Tex_HotKeyMappings"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_HotKeyMappings"></a>11.3.11 g:Tex_HotKeyMappings</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">'eqnarray*,eqnarray,bmatrix'</code></td></tr></tbody></table></div><p>
     This string represents a comma separated list of environments which are
     mapped to <code class="literal">&lt;Shift-F-1&gt;</code> through
     <code class="literal">&lt;Shift-F-4&gt;</code>. For example, pressing
     <code class="literal">&lt;Shift-F-2&gt;</code> with this setting inserts the
     <code class="literal">eqnarray</code> environment.
    </p><p>
     Leaving this string empty will leave <code class="literal">&lt;Shift-F-1&gt;</code> through
     <code class="literal">&lt;Shift-F-4&gt;</code> unmapped.
    </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      Only the first four fields of this list are used. The rest are silently
      ignored.
     </p></div></div><div class="section" title="11.3.12 g:Tex_PromptedCommands"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_PromptedCommands"></a>11.3.12 g:Tex_PromptedCommands</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td>
         <code class="literal">'footnote,cite,pageref,label'</code>
        </td></tr></tbody></table></div><p>
     This string represents a comma separated list of LaTeX commands
     which Latex-Suite uses for the <code class="literal">&lt;F7&gt;</code> and
     <code class="literal">&lt;S-F7&gt;</code> maps as described <a class="link" href="#latex-command-maps" title="3.2 Command Mappings">here</a>.
    </p><p>
     Leaving this string empty will leave the <code class="literal">&lt;F7&gt;</code>
     key unmapped.
    </p></div><div class="section" title="11.3.13 Tex_ItemStyle_environment"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_ItemStyle_environment"></a>11.3.13 Tex_ItemStyle_environment</h4></div></div></div><p>
     This setting affects the style which Latex-Suite uses to insert an
     <code class="literal">\item</code> when <code class="literal">&lt;Alt-I&gt;</code> is
     pressed as described <a class="link" href="#Alt-I" title="3.10.4 &lt;Alt-I&gt;">here</a>. By default
     Latex-Suite defines styles for the following environments:
    </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Environment</th><th>Style</th></tr></thead><tbody><tr><td>itemize</td><td>\item </td></tr><tr><td>enumerate</td><td>\item </td></tr><tr><td>theindex</td><td>\item </td></tr><tr><td>thebibliography</td><td>\item[&lt;+biblabel+&gt;]{&lt;+bibkey+&gt;} &lt;++&gt;</td></tr><tr><td>description</td><td>\item[&lt;+label+&gt;] &lt;++&gt;</td></tr></tbody></table></div><p>
     Each style is defined by a variable of the form
     <code class="literal">g:Tex_ItemStyle_{envname}</code> where
     <code class="literal">envname</code> is the name of the environment for which
     the style is defined. For example, by default
     </p><pre class="programlisting">g:Tex_ItemStyle_description = '\item[&lt;+label+&gt;] &lt;++&gt;'</pre><p>
     Redefining the style for a particular environment or defining a style
     for an entirely new environment is simply a matter of setting the
     value of a variable of the corresponding name.
    </p></div></div><div class="section" title="11.4 Smart Key Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-smart-keys"></a>11.4 Smart Key Customization</h3></div></div></div><p>
    These settings affect the smart key functionality as described <a class="link" href="#smart-keys" title="3.9 Smart Key Mappings">here</a>.
   </p><div class="section" title="11.4.1 g:Tex_SmartKeyBS"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_SmartKeyBS"></a>11.4.1 g:Tex_SmartKeyBS</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     Whether or not <code class="literal">&lt;Backspace&gt;</code> deletes diacritics.
    </p></div><div class="section" title="11.4.2 g:Tex_SmartKeyQuote"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_SmartKeyQuote"></a>11.4.2 g:Tex_SmartKeyQuote</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     Whether or not the <a class="link" href="#smart-keys" title="3.9 Smart Key Mappings">smart quotes</a>
     functionality is available.
    </p><p>
     If enabled, the quote characters can be customized by setting the
     following variables:
    </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><thead><tr><th>Setting</th><th>Value</th></tr></thead><tbody><tr><td><code class="literal">g:Tex_SmartQuoteOpen</code></td><td><code class="literal">"``"</code></td></tr><tr><td><code class="literal">g:Tex_SmartQuoteClose</code></td><td><code class="literal">"''"</code></td></tr></tbody></table></div><p>
     Non-English users will want to change these settings to their locale.
     These global variables will be ignored if there are buffer-local
     variables (with the same name), which may be set in the language specific
     package files, such as
     <code class="literal">$VIM/ftplugin/latex-suite/packages/german</code>.
    </p></div></div><div class="section" title="11.5 Latex Completion Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-latex-completion"></a>11.5 Latex Completion Customization</h3></div></div></div><p>
    The following settings affect the <a class="link" href="#latex-completion" title="5 Latex Completion">
     completion</a> functionality in Latex-Suite.
   </p><div class="section" title="11.5.1 Window size settings"><div class="titlepage"><div><div><h4 class="title"><a id="completion-window-preferences"></a>11.5.1 Window size settings</h4></div></div></div><p>
     These three settings affect the aesthetics of the completion
     functionality.
    </p><a id="Tex_ViewerCwindowHeight"></a><a id="Tex_ViewerPreviewHeight"></a><a id="Tex_ExplorerHeight"></a><a id="Tex_ImageDir"></a><div class="informaltable"><table border="1"><colgroup><col></col><col></col><col></col></colgroup><thead><tr><th>Setting</th><th>Explanation</th><th>Default Value</th></tr></thead><tbody><tr><td><code class="literal">g:Tex_ViewerCwindowHeight</code></td><td>The height of the <code class="literal">cwindow</code> which displays the
         list of <code class="literal">\label</code>s etc.</td><td>5</td></tr><tr><td><code class="literal">g:Tex_ViewerPreviewHeight</code></td><td>The height of the preview window which shows the context of a
         <code class="literal">\label</code> etc.</td><td>10 </td></tr><tr><td><code class="literal">g:Tex_ExplorerHeight</code></td><td>The height of the explorer window which lists the files from
         which to choose an image file.</td><td>10</td></tr><tr><td><code class="literal">g:Tex_ImageDir</code></td><td>The directory to scan for images</td><td>''</td></tr></tbody></table></div></div><div class="section" title="11.5.2 g:Tex_BIBINPUTS"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_BIBINPUTS"></a>11.5.2 g:Tex_BIBINPUTS</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>string</td></tr><tr><td>Default Value</td><td><code class="literal">''</code></td></tr></tbody></table></div><p>
     This string describes the directories which are scanned while trying
     to search for <code class="literal">.bib</code> and <code class="literal">.bbl</code>
     files.  See the <a class="link" href="#latex-completion-cite" title="5.3 Latex-Suite \cite completion">cite completion
      section</a> for more details.
    </p><p>
     This string should be set in the syntax accepted by Vim's native
     <code class="literal">'path'</code> setting. Do not include the present
     directory <code class="literal">'.'</code>. While searching for
     <code class="literal">bibliography</code> files, the present directory will be
     prepended to this variable.
    </p></div><div class="section" title="11.5.3 Tex_UseSimpleLabelSearch"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_UseSimpleLabelSearch"></a>11.5.3 Tex_UseSimpleLabelSearch</h4></div></div></div><p>
     When set to 1, Latex-Suite searches for <code class="literal">\label</code>s in all
     <code class="literal">.tex</code> files in the directory containing the file
     being edited when &lt;F9&gt; is pressed. See <a class="link" href="#ls-completion-ref" title="5.2 Latex-Suite \ref completion">\ref completion</a> for details.
    </p></div><div class="section" title="11.5.4 g:Tex_ProjectSourceFiles"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_ProjectSourceFiles"></a>11.5.4 g:Tex_ProjectSourceFiles</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">''</code></td></tr></tbody></table></div><p>
     This setting is meant to be initialized on a per-project basis using
     the <a class="link" href="#latex-master-file" title="9.2 Specifying which file to compile">Latex-Suite master file</a> as
     described in <a class="link" href="#latex-project" title="9 Multiple file LaTeX projects">Latex-Suite Project</a>
     section. It is a list of source files which are used in the project.
     If defined, then instead of using the logic described in 
     <a class="link" href="#Tex_UseSimpleLabelSearch" title="11.5.3 Tex_UseSimpleLabelSearch">Tex_UseSimpleLabelSearch</a> to
     search for files in which to search for <code class="literal">\label</code>s, we
     simply search for <code class="literal">\label</code>s in this list. This
     significantly reduces the time it takes to generate the list of
     possible completions for large projects.
    </p><p>
     The list is specified as a whitespace separated list of filenames
     relative to the location of the main file.
    </p></div><div class="section" title="11.5.5 g:Tex_RememberCiteSearch"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_RememberCiteSearch"></a>11.5.5 g:Tex_RememberCiteSearch</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">0</code></td></tr></tbody></table></div><p>
     When this variable is non-zero, then Latex-Suite will try to remember results
     from the <code class="literal">\cite</code> completion as described in <a class="link" href="#cite-search-caching" title="5.3.1 Caching the \cite completion results">this section</a>.
    </p></div></div><div class="section" title="11.6 Compiler Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-compiling"></a>11.6 Compiler Customization</h3></div></div></div><p>
    The following settings affect Latex-Suite's compilation functionality
   </p><div class="section" title="11.6.1 g:Tex_DefaultTargetFormat"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_DefaultTargetFormat"></a>11.6.1 g:Tex_DefaultTargetFormat</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">dvi</code> for windows/*nix and
         <code class="literal">pdf</code> for mac</td></tr></tbody></table></div><p>
     Use this setting to choose the default target format. For example,
     setting this to <code class="literal">pdf</code> makes Latex-Suite compile a pdf file
     when you press <code class="literal">\ll</code> and fire up the
     <code class="literal">pdf</code> viewer on pressing <code class="literal">\lv</code>. Make
     sure that a rules for compiling and viewing have been defined for this
     target format as described <a class="link" href="#Tex_CompileRule_format" title="11.6.2 g:Tex_CompileRule_&lt;format&gt;">here</a> and <a class="link" href="#Tex_ViewRule_format" title="11.7.1 g:Tex_ViewRule_&lt;format&gt;">here</a>.
    </p></div><div class="section" title="11.6.2 g:Tex_CompileRule_&lt;format&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_CompileRule_format"></a>11.6.2 g:Tex_CompileRule_&lt;format&gt;</h4></div></div></div><p>
     Here <code class="literal">&lt;format&gt;</code> refers to the target format for
     which this rule is defined. Latex-Suite supports compiling into
     <code class="literal">dvi</code>, <code class="literal">ps</code> and <code class="literal">pdf</code>
     by default. All these rules are strings defined by default as follows:
    </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td><code class="literal">g:Tex_CompileRule_dvi</code></td><td><code class="literal">'latex -interaction=nonstopmode $*'</code></td></tr><tr><td><code class="literal">g:Tex_CompileRule_ps</code></td><td><code class="literal">'ps2pdf $*'</code></td></tr><tr><td><code class="literal">g:Tex_CompileRule_pdf</code></td><td><code class="literal">'pdflatex -interaction=nonstopmode $*'</code></td></tr></tbody></table></div><p>
     If you desire forward and inverse searching via Latex-Suite, you will need to
     change <code class="literal">g:Tex_CompileRule_dvi</code> to include
     <code class="literal">-src-specials</code>. However, this has been known to cause
     problems with the output file. Therefore, use this with care.
    </p></div><div class="section" title="11.6.3 g:Tex_FormatDependency_&lt;format&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="id587026"></a>11.6.3 g:Tex_FormatDependency_&lt;format&gt;</h4></div></div></div><p>
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>string</td></tr><tr><td>Default Value</td><td><code class="literal">''</code></td></tr></tbody></table></div><p>
     By default, there are no format dependencies defined. Each definition
     is of the form above where <code class="literal">&lt;format&gt;</code> is a
     string such as <code class="literal">'dvi'</code> etc.
    </p><p>
     The value of each string is a comma separated string such as 'dvi,ps'.
     See the <a class="link" href="#compiler-dependency" title="6.2 Handling dependencies in compilation">Compiler dependency</a>
     section to see how to use/specify this setting
    </p></div><div class="section" title="11.6.4 g:Tex_MultipleCompileFormats"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_MultipleCompileFormats"></a>11.6.4 g:Tex_MultipleCompileFormats</h4></div></div></div><p>
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>string</td></tr><tr><td>Default Value</td><td><code class="literal">'dvi'</code></td></tr></tbody></table></div><p>
    </p><p>
     This is a comma separated string of formats for which the compiler
     needs to be called multiple times in order to get cross-references,
     citations etc right. See the <a class="link" href="#compiling-multiple" title="6.3 Compiling multiple times">Compiling multiple times</a> section
     for details.
    </p></div><div class="section" title="11.6.5 g:Tex_IgnoredWarnings"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_IgnoredWarnings"></a>11.6.5 g:Tex_IgnoredWarnings</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">a new-line separated list of patterns as described
          below</code></td></tr></tbody></table></div><p>
     The default value of this setting is
     </p><pre class="programlisting">\"Underfull\n".
\"Overfull\n".
\"specifier changed to\n".
\"You have requested\n".
\"Missing number, treated as zero.\n".
\"There were undefined references\n"
\"Citation %.%# undefined"</pre><p>
     This setting defines a set of patterns which will be filtered out when
     displaying the output from the latex compiler. This is to aid in
     filtering out very common warnings/errors.
    </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      Remember to check the value of <a class="link" href="#Tex_IgnoreLevel" title="11.6.6 g:Tex_IgnoreLevel"><code class="literal">g:Tex_IgnoreLevel</code></a>
      when you change this setting. For example, if you append a new pattern
      which you would like to ignore by default, increase the value of
      <code class="literal">g:Tex_IgnoreLevel</code>.
     </p></div></div><div class="section" title="11.6.6 g:Tex_IgnoreLevel"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_IgnoreLevel"></a>11.6.6 g:Tex_IgnoreLevel</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Integer</td></tr><tr><td>Default Value</td><td><code class="literal">7</code></td></tr></tbody></table></div><p>
     This setting defines a "filter level" or an "ignore level". A value of 7
     for instance means that any warning/error matching with any of the first
     7 fields of <a class="link" href="#Tex_IgnoredWarnings" title="11.6.5 g:Tex_IgnoredWarnings"><code class="literal">g:Tex_IgnoredWarnings</code></a>
     will be ignored. Setting this value to zero will mean that no
     error/warning is ignored. However, even with a value of zero, Latex-Suite will
     filter out most of the text which a LaTeX compiler typically produces.
     Use
     </p><pre class="programlisting">TCLevel strict</pre><p>
     from within Vim in order to see all the lines from the compiler's
     output.
    </p></div><div class="section" title="11.6.7 Tex_UseMakefile"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_UseMakefile"></a>11.6.7 Tex_UseMakefile</h4></div></div></div><p>
     </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     </p><p>
      When set to 1, then if a <code class="literal">makefile</code> or
      <code class="literal">Makefile</code> is present in the current directory, then
      Latex-Suite sets the <code class="literal">makeprg</code> option to just
      <code class="literal">"make &lt;target&gt;"</code>, where
      <code class="literal">&lt;target&gt;</code> is the target format chosen using
      the <code class="literal">TCTarget</code> or <code class="literal">TTarget</code>
      commands.
     </p><p>
     </p><p>
      When set to 0, then Latex-Suite will set the <code class="literal">makeprg</code>
      setting to whatever is defined by the <a class="link" href="#Tex_CompileRule_format" title="11.6.2 g:Tex_CompileRule_&lt;format&gt;">g:Tex_CompileRule_target</a>
      setting.
     </p><p>
    </p></div><div class="section" title="11.6.8 g:Tex_GotoError"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_GotoError"></a>11.6.8 g:Tex_GotoError</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     If set to 1, then pressing <code class="literal">\ll</code> will take you to
     the location of the first warning/error, otherwise you will remain in
     the original location but the errors/warnings will be listed in the
     preview window.
    </p></div></div><div class="section" title="11.7 Viewer Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-viewing"></a>11.7 Viewer Customization</h3></div></div></div><p>
    The following settings affect how Latex-Suite will display compiled files.
   </p><div class="section" title="11.7.1 g:Tex_ViewRule_&lt;format&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_ViewRule_format"></a>11.7.1 g:Tex_ViewRule_&lt;format&gt;</h4></div></div></div><p>
     Here <code class="literal">&lt;format&gt;</code> refers to a format such as
     <code class="literal">dvi</code>, <code class="literal">ps</code>, etc. This variable defines
     the program which will be called to display a file of that format.
    </p><p>
     By default, Latex-Suite defines viewer programs for viewing DVI, PS and PDF
     formats as follows:
    </p><div class="informaltable"><table border="1"><colgroup><col></col><col></col><col></col></colgroup><thead><tr><th></th><th>Windows</th><th>Unix</th></tr></thead><tbody><tr><td><code class="literal">g:Tex_ViewRule_dvi</code></td><td><code class="literal">'yap -1'</code></td><td><code class="literal">'xdvi'</code></td></tr><tr><td><code class="literal">g:Tex_ViewRule_ps</code></td><td><code class="literal">'gsview32'</code></td><td><code class="literal">'ghostview'</code></td></tr><tr><td><code class="literal">g:Tex_ViewRule_pdf</code></td><td><code class="literal">'AcroRd32'</code></td><td><code class="literal">'xpdf'</code></td></tr></tbody></table></div><p>
     For Macintosh systems, these strings are left empty by default. This lets
     the system pick the program for each format. If you define these variables
     for Mac, the system choice will be over-ridden.
    </p><p>
     Latex-Suite appends <code class="literal">file.format</code> to the above settings
     while calling the external programs. For example, with
     </p><pre class="programlisting">let g:Tex_ViewRule_dvi = 'yap -1'</pre><p>
     <code class="literal">yap</code> is called as 
     </p><pre class="programlisting">!start yap -1 file.dvi</pre><p> from within
     Vim. (The initial <code class="literal">start</code> is used on
     <code class="literal">Windows</code> platforms is to make <code class="literal">yap</code>
     start as a separate process.) If you find the way Latex-Suite constructs the
     command line too restrictive, you can use the <a class="link" href="#Tex_ViewRuleComplete_format" title="11.7.2 Tex_ViewRuleComplete_&lt;format&gt;"><code class="literal">Tex_ViewRuleComplete_format</code></a>
     setting for more complete control on how the command line is
     constructed while calling the external program for viewing.
    </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      For windows, you will need to set the <code class="literal">$PATH</code> variable
      to include the paths to <code class="literal">yap</code>,
      <code class="literal">AcroRd32</code>, <code class="literal">gsview32</code> and any other
      programs. See your system documentation for how to do this.
     </p></div><div class="note" title="Default Viewing Format" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Default Viewing Format</h3><p>
      To change the default format for viewing files, set the <a class="link" href="#Tex_DefaultTargetFormat" title="11.6.1 g:Tex_DefaultTargetFormat">g:Tex_DefaultTargetFormat</a>
      variable.
     </p></div></div><div class="section" title="11.7.2 Tex_ViewRuleComplete_&lt;format&gt;"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_ViewRuleComplete_format"></a>11.7.2 Tex_ViewRuleComplete_&lt;format&gt;</h4></div></div></div><p>
     Here <code class="literal">&lt;format&gt;</code> refers to the extension of a
     output format such as <code class="literal">dvi</code>, <code class="literal">html</code>
     etc.
    </p><p>
     <code class="literal">Tex_ViewRuleComplete_format</code> takes precedence over
     <code class="literal">Tex_ViewRule_format</code> if both are specified. By
     default, Latex-Suite does not define values for
     <code class="literal">Tex_ViewRuleComplete_format</code> for any
     <code class="literal">format</code>. Unlike in the case of
     <code class="literal">Tex_ViewRule_format</code>, Latex-Suite does not modify
     <code class="literal">Tex_ViewRuleComplete_format</code> at all in constructing
     the command line. The only modification is to substitute
     <code class="literal">'$*'</code> everywhere in the string with the name of the
     file being viewed (without the extension).
    </p><div class="note" title="IMPORTANT" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">IMPORTANT</h3><p>
      Make sure you make the process go into the background otherwise vim
      will wait for the viewer to terminate before letting you edit the file
      again.
     </p><p>
      To make a process go into the background on a <code class="literal">*nix</code>
      platform, use a trailing <code class="literal">&amp;</code> in the setting. On
      <code class="literal">Windows</code>, use <code class="literal">start</code> at the
      beginning of the setting. Example: Suppose you have a latex-&gt;html
      converter which converts a file say foo.tex to a file foo/index.html.
      Then you would use:
      </p><pre class="programlisting">" On *nix platform
let g:Tex_ViewRuleComplete_html = 'MozillaFirebird $*/index.html &amp;'
" On windows platform
let g:Tex_ViewRuleComplete_html = 'start MozillaFirebird $*/index.html'</pre><p>
     </p></div></div></div><div class="section" title="11.8 Menu Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-menus"></a>11.8 Menu Customization</h3></div></div></div><p>
    In addition to using the variables defined in this section to affect
    the menu-layout permanently (i.e, the layout Latex-Suite will start with), you
    can also use the <code class="literal">TeX-Suite &gt; Configure Menu</code> menu to
    dynamically configure the menu layout after Latex-Suite has started.
   </p><div class="section" title="11.8.1 g:Tex_Menus"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Menus"></a>11.8.1 g:Tex_Menus</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     If set to 0, Latex-Suite will suppress showing all menus. Useful if you mostly
     work in terminals.
    </p></div><div class="section" title="11.8.2 g:Tex_MainMenuLocation"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_MainMenuLocation"></a>11.8.2 <code class="literal">g:Tex_MainMenuLocation</code></h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>number</td></tr><tr><td>Default Value</td><td><code class="literal">80</code></td></tr></tbody></table></div><p>
     This setting decides the location of the first top-level Latex-Suite
     menu. You can for example shift all the menus created by Latex-Suite
     to the very end by setting this value to a large number like 990.
    </p></div><div class="section" title="11.8.3 g:Tex_MathMenus"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_MathMenus"></a>11.8.3 g:Tex_MathMenus</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     The <code class="literal">Tex-Math</code> menu consists of hundreds of mathematical
     symbols used in LaTeX. This menu comprises about 75% of the menus.
    </p></div><div class="section" title="11.8.4 g:Tex_NestElementMenus"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_NestElementMenus"></a>11.8.4 g:Tex_NestElementMenus</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     This setting controls the "compactness" of the menus. If set to 1, then the
     Font, Counter and Dimensioning menus are collected together in a single
     menu called <code class="literal">Tex-Elements</code>, otherwise, they will each get
     a separate menu.
    </p></div><div class="section" title="11.8.5 g:Tex_PackagesMenu"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_PackagesMenu"></a>11.8.5 g:Tex_PackagesMenu</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     Setting this to zero will stop Latex-Suite from automatically creating the
     <code class="literal">TeX-Suite &gt; Packages &gt; Supported</code> menu at startup. You
     can still create the menu after startup by going to
     <code class="literal">TeX-Suite &gt; Configure Menu</code>.
    </p></div><div class="section" title="11.8.6 g:Tex_NestPackagesMenu"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_NestPackagesMenu"></a>11.8.6 g:Tex_NestPackagesMenu</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>String</td></tr><tr><td>Default Value</td><td><code class="literal">'TeX-'</code></td></tr></tbody></table></div><p>
     This string is the prefix added to all the menus created by Latex-Suite. If you
     define this variable with a dot (<code class="literal">'.'</code>) as the last
     character, then all the menus created by Latex-Suite will be nested under a
     single master menu. For example, set this to
     <code class="literal">'&amp;LaTeX-Suite.'</code> to nest all menus under a menu
     called <code class="literal">&amp;LaTeX-Suite</code>.
    </p></div><div class="section" title="11.8.7 g:Tex_UseUtfMenus"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_UseUtfMenus"></a>11.8.7 g:Tex_UseUtfMenus</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">0</code></td></tr></tbody></table></div><p>
     This setting controls whether Latex-Suite uses utf-8 symbols to display some of
     the mathematical symbols in the <code class="literal">TeX-Math</code> menu. It is
     necessary for your system/GUI to support utf-8. Setting this to 1 has the
     side-effect of setting the <code class="literal">'encoding'</code> option of Vim
     to 'utf-8'.
    </p></div></div><div class="section" title="11.9 Folding Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-folding"></a>11.9 Folding Customization</h3></div></div></div><p>
    The following settings control the <a class="link" href="#latex-folding" title="8 Latex Folding">folding</a> functionality of Latex-Suite.
   </p><div class="section" title="11.9.1 g:Tex_Folding"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_Folding"></a>11.9.1 g:Tex_Folding</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     Setting this to zero completely disables Latex-Suite's folding functionality.
     However, the <code class="literal">TexFoldTextFunction()</code> is still available
     in case you want to use another folding scheme but still want to continue
     using the fold text function.
    </p></div><div class="section" title="11.9.2 g:Tex_AutoFolding"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_AutoFolding"></a>11.9.2 g:Tex_AutoFolding</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>Boolean</td></tr><tr><td>Default Value</td><td><code class="literal">1</code></td></tr></tbody></table></div><p>
     This setting controls whether Latex-Suite automatically creates manual folds for
     a file when it is opened. You can still use the <code class="literal">\rf</code>
     mapping to refresh/create folds even when this variable is set to zero.
    </p></div></div><div class="section" title="11.10 Package Handling Customization"><div class="titlepage"><div><div><h3 class="title"><a id="customizing-packages"></a>11.10 Package Handling Customization</h3></div></div></div><p> 
    These settings affect the <a class="link" href="#custom-packages" title="4.3.1 Custom Packages">custom
     packages</a> functionality in Latex-Suite
   </p><div class="section" title="11.10.1 g:Tex_TEXINPUTS"><div class="titlepage"><div><div><h4 class="title"><a id="Tex_TEXINPUTS"></a>11.10.1 g:Tex_TEXINPUTS</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Type</td><td>string</td></tr><tr><td>Default Value</td><td><code class="literal">''</code></td></tr></tbody></table></div><p>
     This setting describes the directories scanned by Latex-Suite while searching
     for custom user packages as described in the <a class="link" href="#custom-packages" title="4.3.1 Custom Packages">custom packages</a> section. Do not
     include the present directory in this setting. The present directory
     is always scanned for custom packages.
    </p><p>
     This string should be set in the syntax accepted by Vim's native
     <code class="literal">'path'</code> setting.
    </p></div></div></div><div class="section" title="12 Credits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="latex-suite-credits"></a>12 Credits</h2></div></div></div><p>
   And finally, the credits:
  </p><div class="informaltable"><table border="0"><colgroup><col></col><col></col></colgroup><tbody><tr><td>Artur R. Czechowski</td><td>maintains the BSD package of Latex-Suite. Lots of valuable
       feedback.</td></tr><tr><td>
       Lubomir Host      
      </td><td>
       provided the diacritics and also helped in development.
       
      </td></tr><tr><td>
       Alexander Wagner  
      </td><td>
       valuable suggestions during development.
       
      </td></tr><tr><td>
       Luc Hermitte      
      </td><td>
       his variation of Stephen Riehm's bracketing system is used
       in Latex-Suite.
       
      </td></tr><tr><td>
       Gergely Kontra    
      </td><td>
       the clever little JumpFunc() in imaps.vim is due to him.
       The implementation of the templates also borrows from
       mu-template.vim by him.
       
      </td></tr><tr><td>
       Dimitri Antoniou  
      </td><td>
       author of ltags and also provided the nice tip about
       forward / reverse search on DVI documents.
       
      </td></tr><tr><td>
       Stephen Riehm     
      </td><td>
       the extremely helpful bracketing system is from him.
       
      </td></tr><tr><td>
       Alan Schmitt      
      </td><td>
       provided macros/folding elements. Continued feedback,
       bug-reports/fixes.
       
      </td></tr><tr><td>
       Hari Krishna Dara 
      </td><td>
       for ExecMap(), the clever little function which makes
       typing visual mode mappings so much easier and error-free.
       
      </td></tr><tr><td>
       Alan G Isac       
      </td><td>
       for the comprehensive BibT() function for entering bibtex
       entries.
       
      </td></tr><tr><td>
       Gontran Baerts    
      </td><td>
       for libList.vim
       
      </td></tr><tr><td>
       Peter Heslin      
      </td><td>
       useful discussion and also a lot of bug fixes.
       the %%fakesection in folding.vim.
       
      </td></tr><tr><td>
       Zhang Lin-bo
      </td><td>
       lots of very useful additions to folding. The code for customizing
       the folding scheme is due to him.
      </td></tr></tbody></table></div><p>
   A large number of functions in Latex-Suite come from various other people.
   Some of those people might have been missed here. Each function should however
   have the author's name/e-mail above it. Thats the more authoritative place to
   check out who has done what.
  </p><a id="latex-suite-maintainer"></a><p>
   The current maintainer(s) of Latex-Suite is(are)
  </p><table border="0" summary="Simple list" class="simplelist"><tr><td>Srinath Avadhanula &lt;srinath@fastmail.fm&gt;</td></tr><tr><td>Mikolaj Machowski &lt;mikmach@wp.pl&gt;</td></tr><tr><td>Benji Fisher &lt;benji@member.AMS.org&gt;</td></tr></table></div></div></body></html>