Changes

httphttps://www.vim.org/

This page will be is about editing ConTeXt source in (g)vimVim, gVim, MacVim, and other Vim clones.The page describes the scripts available in Vim v8.0.0055 or later. If you are using Vim 7, see''Using the scripts with an older Vim'' below.

<b>If you feel that something is missing, please contribute!</b> Information about providing feedback is in the header of the scripts. == Filetype detection Using ConTeXt in Vim ==Tex Nikolai Weibull was the first one who wrote <tt>context.vim</tt> files and submitted them to the official Vim repository.They are part of the official Vim 7, and were expanded and improved in Vim 8. Starting with Vim 9.0.0218, the scripts supporting ConTeXt in Vim have been rewritten in Vim 9 script (the new Vim's scripting language). For the complete documentation, see <tt>:help ft-context</tt>. === Asciicast === [[File:context-in-vim.png]] This asciicast[https://asciinema.org/a/91111] gives you a taste of ConTeXt editing in Vim. === Typesetting === The recommended way to typeset a ConTeXt document is to use the <tt>:ConTeXt</tt> command. Just type: :ConTeXt %to compile the document in the current buffer.Typesetting happens in the background,so you may continue working on your document. If there are errors, the quickfix window will open automaticallyto show the errors (one per line). The cursor will stay in the main document, so your typing workflow will notbe disrupted. You may use standard quickfix commands to jump between errors: <tt>:cfirst</tt>, <tt>:cprev</tt>,<tt>:cnext</tt>, etc… (plain texsee <tt>:help quickfix</tt>). See below for useful mappings for these commands. If your document is typeset without errors, <tt>Success!</tt> is printed at the bottom of the screen. The <tt>:ConTeXt</tt> command accepts an optional path, in case you want to typeset a document differentfrom the current one (useful for big projects). You may check the status of your ConTeXt jobs with <tt>:ConTeXtJobStatus</tt>, latex and you may stop allrunning jobs with <tt>:ConTeXtStopJobs</tt>. === Setting a custom typesetting engine === The <tt>:ConTeXt</tt> command invokes the <tt>mtxrun</tt> script that is found in <tt>$PATH</tt>. For more fine grained control over the command and its environment, you may invoke `context.Typeset()` directly (or `context all #Typeset()` from legacy Vim script). For instance, if you have installed a version of ConTeXt in <tt>$HOME/context</tt> (where <tt>$HOME</tt> is the path to your home directory), you may define a function to use it similar to the following (you may put the following code in <codett>~/.vim/after/ftplugin/context.vim</tt>, creating the file and the directories if they do not exist):  import autoload 'context.vim'  def MyConTeXt() const env = {'PATH': printf("%s/context/tex/texmf-<os>-<arch>/codebin:%s", $HOME, $PATH)} context.Typeset("%", env) enddef and perhaps use it with a mapping:  nnoremap <silent><buffer><leader>t <scriptcmd>MyConTeXt()<cr> <tt>context.Typeset()</tt> accepts a third optional argument to specify a customtypesetting command. That must be a function that takes a path and returns thecommand as a List. For example:  def ConTeXtCustomCommand(path: string): list<string> extension for return ['mtxrun', '--script', 'context', '--nonstopmode', path] enddef  context.ConTeXtTypeset("%", v:none, ConTeXtCustomCommand) === Working with large projects === Large projects are often organized as a root document and various chapterfiles . When editing a chapter file, it is convenient to invoke <tt>:ConTeXt</tt>directly on it, rather than having to switch to the root file. A “magic line”can be added at the beginning of each chapter file, which makes it difficult specifies therelative path to detect the filetype based on root file. For instance:  % !TEX root = ../MyRoot.tex Vim searches for the magic line in the first ten lines of the current buffer:if the magic line is found, the document specified by that line is typeset rather than theone in the current buffer. The root document does not have to be opened inVim. === Updating the extensionsyntax files === Vim includes syntax files generated by <tt>mtxrun</tt>. If you want to use more up-to-date files, overriding those distributed with Vim, you may proceed as follows. From Assuming your Vim 7 onwardsconfiguration lives in <tt>~/.vim</tt>, you may type:  mkdir -p ~/.vim/syntax/shared cd ~/.vim/syntax/shared mtxrun --script interface --vim The last command will create the following syntax files: * <tt>context-data-context.vim</tt>;* <tt>context-data-interfaces.vim</tt>;* <tt>context-data-metafun.vim does some intelligent checking </tt>;* <tt>context-data-tex.vim</tt>.  === Editing features === You may use the following commands to quickly jump to different parts of your document: * <tt>[[</tt>: jump to the previous start of subject, section, chapter, part, component, or product;* <tt>]]</tt>: jump to the next start of subject, section, chapter, part, component, or product;* <tt>[]</tt>: jump to the previous end of section, chapter, etc…;* <tt>][</tt>: jump to the next end of section, chapter, etc…;* <tt>[{</tt>: jump to the previous <tt>\start…</tt> or <tt>\setup…</tt> command;* <tt>]}</tt>: jump to the next <tt>\stop…</tt> or <tt>\setup…</tt> command; Each of the above accepts an optional count. For example, you may type <tt>3[{</tt> to jumpthree <tt>\start…</tt> commands before. You may use the following ConTeXt-specific text objects, to be used in Visual or Operator-pending mode(see <tt>:help text-objects</tt>): * <tt>i$</tt>: inside <tt>$…$</tt> (dollars excluded);* <tt>a$</tt>: around <tt>$…$</tt> (dollars included);* <tt>tp</tt>: a ConTeXt paragraph. So, for example, you may copy (“yank” in Vim's jargon) a paragraph by typing <tt>ytp</tt> (“yank a TeXparagraph“), delete it with <tt>dtp</tt>, select it with <tt>vtp</tt>, reflow it with <tt>gqtp</tt>, etc…Similarly, you may yank a formula with <tt>vi$</tt> (or <tt>va$</tt>), and delete it, select it, etc…, in asimilar fashion. If you have enabled the <tt>matchit</tt> plugin included in Vim (see <tt>:help matchit</tt>), you may alsotype <tt>%</tt> to jump between matching <tt>\start…</tt> and <tt>\stop…</tt> commands, or betweenmatching parentheses. You may jump to a different file by positioning the cursor over the file name and typing <tt>gf</tt> (<tt>:help gf</tt>).For example, if you have the following in your document: \component my_componentputting the cursor over <tt>my_component</tt> and pressing <tt>gf</tt> will open <tt>my_component.tex</tt>. Similarly, you may use <tt>[<c-i></tt> (this is square bracket followed by ctrl-i)to jump to the definition of the word under the cursor (even if it is plaintex in a differentfile), or latex <tt>[i</tt> to display the (first line of the) definition under the status line. For these and similar commands,see <tt>:help include-search</tt>. Vim searches for files in the locations specified by the <tt>path</tt> option. You mayneed to adjust the value of <tt>path</tt> for the above to work (see <tt>:help 'path'</tt>). === Integration with MetaPost === Vim offers excellent support for editing METAFONT and MetaPost documents (<tt>mf</tt> and <tt>mp</tt> filetypes).See <tt>:help ft-metapost</tt> for the details.Most of the features of such filetypes work also inside ConTeXt's MetaPost environments,such as <tt>\startMPpage… \stopMPpage</tt>. In particular, Vim automatically highlights and indents MetaPost and MetaFun code inside a ConTeXt document.Besides, when you are inside a MetaPost environment, you may press CTRL-X followed by CTRL-Oto complete a MetaPost/MetaFun keyword (see below for a list of several autocompletion plugins to streamline this).This works out of the box: no configuration is required. Watch the asciicast above for a demo. === Integration with other languages === Lua syntax highlighting is used inside <tt>\directlua{}</tt> and <tt>\ctxlua{}</tt> commands,and inside <tt>\startluacode… \stopluacode</tt>. XML highlighting is used inside <tt>\startXML… \stopXML</tt>. You may embed other filetypes. Just define <tt>g:context_include</tt> (or context<tt>b:context_include</tt> forbuffer-specific settings). For example, if you want to highlight C++ code inside, say, <tt>\startCPP… \stopCPP</tt>,define: let g:context_include = { 'cpp' : 'CPP' }The key is the name of the filetype and the corresponding value is name of the command.

If the first line of a *.tex file has the form %&<format>then this determined the file type: plaintex (for plain TeX), context (forConTeXt), or tex (for LaTeX). Otherwise, the file is searched for keywords tochoose context or tex. If no keywords are found, it defaults to plaintex.You can change the default by defining the variable g:tex_flavor to the format(not === Using the file type) you use most. Use one of these: let g:tex_flavor scripts with an older Vim = "plain" let g:tex_flavor = "context" let g:tex_flavor = "latex"Currently no other formats are recognized.

* If you use ConTeXt most of the time, but occasionally use latex or plaintexare using an older Vim, you can add may copy the following to scripts from Vim's distribution (https://github.com/vim/vim) into correspondingfolders in your <codett>.vimrcvim</codett> let g:tex_flavor = "folder (so, for example <tt>runtime/ftplugin/context"* If you only use ConTeXt, you can add the following lines to filetype.vim:</tt> must be copied into " ConTeXt augroup filetypedetect au! BufRead,BufNewFile *<tt>~/.tex setfiletype vim/ftplugin/context augroup ENDso the next time you open a <code>*.texvim</codett> file, vim will recognise always recognize it as a context file.):

Enabling the spell-ckecker has been "forgotten" in <codeb>context.vimNote:</codeb>the runtime scripts in Vim 9.0. Either say :syn[tax] spell toplevelafter opening the document 0218 or add syn spell toplevelsomewhere on later are written in Vim 9 script (the top new scripting language embedded in Vim) and there is no guarantee that they will work with older versions of <code>runtime/syntax/context.vim</code>, as in: runtimeVim! syntax/plaintex.vim let s:cpo_save = &cpo set cpo&vim syn spell toplevel

Additionally, If you have to set :set spell spelllang=en_USor get the language of your preference once following error when you have installed it into vim.open a ConTeXt or MetaPost document:

== ftplugin and E410: Invalid :syntax file ==subcommand: iskeyword

Nikolai Weibull was edit the first one who wrote context.vim syntax files and submitted them to remove the official vim cvs repository<tt>syn iskeyword</tt> or <tt>syntax iskeyword</tt> line.They are part of the official Vim 7Instead, put a corresponding command in <tt>~/.vim/after/ftplugin/context. vim</tt>:

If you are using an older Vim setlocal iskeyword=@, you can download the files at:* [http://cvs.sourceforge.net/viewcvs.py/vim/vim7/runtime/syntax/context.vim runtime/syntax/context.vim] 48- syntax highlighting* [http://cvs.sourceforge.net/viewcvs.py/vim/vim7/runtime/ftplugin/context.vim runtime/ftplugin/context.vim] 57,a-z,A-Z,192- filetype specific behaviour (like repeating comments at the beginning of line)255

It's mostly up to you which syntax highlighting scheme you prefer. <code>context.vim</code> is a lighter version than <code>tex.vim</code>. It knows some ConTeXt details that are not implemented in <code>tex.vim</code> setlocal iskeyword=@, while math and some other TeX features are not supported yet in <code>context.vim</code>._

<b>If you feel that something is missingEverything should work, please contribute!</b>at least with Vim 7.4.

* extract data from texweb and create syntax highlighting definitions for ConTeXt* add metafun macros (from metafun manual)* enable metapost/metafun, JavaScript and XML inside ConTeXt* some Some essential math support.* proper Proper URL highlighting ('%' doesn't start a comment, ...) [request by VnPenguin].* perhaps Perhaps borrow something from https://github.com/lervag/vimtex or http://vim-latex.sourceforge.net/?* Have a better filetype detection for *.tex files, to distinguish between plain tex, latex and context files (can this be deleted now? --[[User:Adityam|Aditya]])* vim auto-complete for vim

== Other useful vim plugins Filetype detection ==

* autocomplete: http://vimTeX (Plain TeX), LaTex and ConTeXt all use the <tt>.sourceforge.nettex</scripts/scripttt> extension for files, which makes it difficult to detect the filetype based on the extension.php?script_id=182From Vim 7 onwards, almost undocumented, but life-saving* spell-checker: http:Vim does some intelligent checking to see it the file is <tt>plaintex</tt> or <tt>latex</www.vim.orgtt> or <tt>context</scripts/scripttt>.php?script_id=499, but native spell-checking support will be included in Vim 7

If the first line of a <tt>*.tex</tt> file has the form %&<format>then this determines the file type: <tt>plaintex</tt> (for Plain TeX), <tt>context</tt> (forConTeXt), or <tt>tex</tt> (for LaTeX). Otherwise, the file is searched for keywords tochoose <tt>context</tt> or <tt>tex</tt>. If no keywords are found, it defaults to <tt>plaintex</tt>.You can change the default by defining the variable <tt>g:tex_flavor</tt> to the format(not the file type) you use most. Use one of these: let g:tex_flavor ="plain" let g:tex_flavor = using "context" let g:tex_flavor = "latex-suite =="Currently no other formats are recognized.

[http* If you use ConTeXt most of the time, but occasionally use LaTeX or Plain TeX, you can add the following to your <tt>vimrc</tt> let g:tex_flavor = "context"* If you only use ConTeXt, you can add the following lines to <tt>filetype.vim</tt>: " ConTeXt augroup filetypedetect au! BufRead,BufNewFile *.tex setfiletype context augroup ENDso the next time you open a <tt>*.tex</vimtt> file, Vim will always recognize it as a ConTeXt document. == Spell checking == Vim 7 or later has a built-latexin spell checker.sourceforgeTo enable it or disable it, use: :set spellor :set nospellrespectively.To set the language to be used for spell checking, set the <tt>spelllang</tt> option accordingly.netFor example: :set spelllang=en_usUse lowercase letters (<tt>en_us</ latex-suite] currently doesn't support ConTeXttt>, but if not <tt>en_US</tt>). When you use itset <tt>spelllang</tt>, Vim offers todownload the language data into your <tt>.vim</tt> folder, here's what if such language is not available.You can put the above settings in your <tt>vimrc</tt> if you have to do to compile ConTeXt documents:like. == Powerful key mappings ==

1. After downloading and installing latex-suiteIn the following, locate the file "texrc" <tt><leader></tt> denotes your “leader” (usually located in <codett>~/.vim/ftplugin/latex-suite:help mapleader</codett>), that is,the prefix for user-defined mappings. Copy By default, the leader is the backslash character, but that may be changed by the user.For example, to use a comma as a leader, put this file to in your <codett>~vimrc</tt>: map <leader> ,Rather than overriding the default leader, you may define an alternative key.vimThe <tt><space></ftplugintt> is a goodchoice, because by default it has the same function as the <tt><right></tex/texrctt> key, and it is comfortable to type: map <space> <leader> " Use </codespace>as an alternative leader (backslash can still be used)

3The following function can be used to clean up temporary files: fun! ConTeXtClean() let l:currdir = expand("%:p:h") let l:tmpdirs = ['out'] " Temporary directories let l:suffixes = ['aux', 'bbl', 'blg', 'fls', 'log', 'tuc'] " Suffixes of temporary files for ff in glob(l:currdir . '/*.{' . join(l:suffixes, ',') . After line 80 '}', 1, 1) call delete(ff) endfor for dd in this filel:tmpdirs let l:subdir = l:currdir . '/' . dd if isdirectory(l:subdir) for ff in glob(l:subdir . '/*.{' . join(l:suffixes, ',') . '}', 1, there is a series of 1) call delete(ff) endfor endif call delete(l:subdir) " Delete directory (only if empty) endfor echomsg "Aux files removed"Compiler rules endfCustomize <tt>l:tmpdirs</tt> and <tt>l:suffixes</tt> to suit your needs." Just add this line In Windows systems, you may have to the section:replace each slash with a backslash, too.

The following mapping allows you to remove auxiliary files by pressing <tt>\tc</tt>: TexLet gnnoremap <silent><buffer> <leader>tc :Tex_CompileRule_cont = 'texexec --pdf -<c-nonstopmode $*'u>call ConTeXtClean()<cr>

4Vim allows you to define abbreviations for frequently used pieces of text (see <tt>:help abbreviations</tt>). When youHere are a few examples:<pre>fun! Eatchar(pat) " See :help abbreviations let c = nr2char(getchar(0)) return (c =~ a:pat) ? ''re in vim normal mode, run this command:cendfun

TGTarget cont iab <buffer> ch- \startchapter[thattitle={<c-o>ma}]<cr><c-o>mb<cr>\stopchapter<esc>`a`b<c-o>a<c-r>=Eatchar('\s')<cr>iab <buffer> s- \startsection[title={<c-o>ma}]<cr><c-o>mb<cr>\stopsection<esc>`a`b<c-o>a<c-r>=Eatchar('\s')<cr>iab <buffer> ss- \startsubsection[title={<c-o>ma}]<cr><c-o>mb<cr>\stopsubsection<esc>`a`b<c-o>a<c-r>=Eatchar('\s "colon TGTarger cont"')<cr>iab <buffer> sss- \startsubsubsection[title={<c-o>ma}]<cr><c-o>mb<cr>\stopsubsubsection<esc>`a`b<c-o>a<c-r>=Eatchar('\s')<cr>iab <buffer> slide- \startslide[title={<c-o>ma}]<cr><c-o>mb<cr>\stopslide<esc>`a`b<c-o>a<c-r>=Eatchar('\s')<cr>iab <buffer> fig- \startplacefigure<cr><tab>\externalfigure[<c-o>ma]%<cr>[]<c-o>mb<cr><c-d>\stopplacefigure<esc>`a`b<c-o>a<c-r>=Eatchar('\s')<cr>iab <buffer> item- \startitemize<cr><cr>\stopitemize<up><tab>\itemiab <buffer> enum- \startitemize[n] <cr><cr>\stopitemize<up><tab>\itemiab <buffer> i- \item</pre>

5. Edit your TeX-files, save Type the changes; when you want abbreviation followed by Space to compileexpand the snippet, switch to normal mode and just type <code>\ll</code> (that's '' 'backslash el el' '')then continue typing normally.

VoilaInside the definition of an abbreviation, marks may be set (see <tt>:h m</tt>), compilation should start. You'll have which allow you to specify this compiler target every timeI you open jump between the differentparts of a TeXsnippet with TAB (CTRL-file i) and CTRL-O (in VimNormal mode) after the abbreviation is expanded (see <tt>:h jump-motions</tt>).For example, after typing <tt>ch- </tt>, the cursor will be at the title's position. If you press <tt><esc><tab></tt> (or<tt><c-o><tab></tt> if you want to make this stay in Insert mode after the default compilerjump), you should have this line in your texrc:will jump between <tt>\startchapter</tt>and <tt>\stopchapter</tt>.

TexLet g:Tex_DefaultTargetFormat = 'cont' == Buffer-local Insert-mode macros to speed up editing ===

==key = Key mappings borrowed from sciteSciTE === If you use the stand-alone distribution for windowsWindows/Linux.You can reset the key mappingto speed ConTeXt compiling.

just Just add the following code to your <tt>_vimrc</tt> (or <tt>.vimrc </tt> file under Linux) file:

=== Quickfix mappings === It is useful to define mappings for quickfix commands, to be able to navigate among ConTeXt errors.For example: nnoremap <silent> ]q :<c-u><c-r>=v:count1<cr>cnext<cr>zz nnoremap <silent> [q :<c-u><c-r>=v:count1<cr>cprevious<cr>zz nnoremap <silent> ]Q :<c-u>clast<cr>zz nnoremap <silent> [Q :<c-u>cfirst<cr>zzOr install Tim Pope's <i>unimpaired</prei>plugin.

== Makefile Makefiles ==

texexec context paper

rm *.bbl aux *.dvi bbl *.aux blg *.log *.blgtuc

If you put these mappings to your <code>.vimrc</code> file, you can than then compile the document with F9 and preview it with F8:

imap <F9> <ESC>:exe "lcd" fnameescape(expand("%:p:h"))<CR>:make<CR> nmap <F9> :exe "lcd" fnameescape(expand("%:p:h"))<CR> :make<CR>

imap <F8> <ESC>:exe "lcd" fnameescape(expand("%:p:h"))<CR>:make test<CR> nmap <F8> :exe "lcd" fnameescape(expand("%:p:h"))<CR> :make test<CR> Note that if you use <tt>:make</tt> typesetting will happen synchronously. == Other useful Vim plugins == === Autocompletion === Vim offers a rich completion mechanism (<tt>:help ins-completion</tt>), but there are several pluginsthat improve on it, in particular, to provide automatic completion of keywords: * MUcomplete[https://github.com/lifepillar/vim-mucomplete]* Coc [https://github.com/neoclide/coc.nvim].* Completor[https://github.com/maralla/completor.vim]* NeoComplete[https://github.com/Shougo/neocomplete.vim]* Deoplete (for NeoVim)[https://github.com/Shougo/deoplete.nvim]* YouCompleteMe[https://github.com/Valloric/YouCompleteMe]* AutoComplPop[https://github.com/vim-scripts/AutoComplPop]* SuperTab[https://github.com/ervandew/supertab]

== MetaPost extension = UltiSnips ===

Should highlight UltiSnips[https://github.com/SirVer/ultisnips] is a sophisticated snippets manager.Here are a few examples of useful UltiSnips snippets for ConTeXt:  snippet "s(tart)?" "start / stop" br \start${1:something}$2 ${3:${VISUAL}} \stop$1 endsnippet snippet enum "Enumerate" b \startitemize[n] \item ${0:${VISUAL}} \stopitemize endsnippet snippet item "Itemize" b \startitemize \item ${0:${VISUAL}} \stopitemize endsnippet snippet it "Individual item" b \item ${0:${VISUAL}} endsnippet snippet fig "External figure" b \startplacefigure \externalfigure[${1:${VISUAL}}][$2] \stopplacefigure endsnippet Save the above text into <tt>~/.vim/UltiSnips/context.snippets</tt>. Click on the asciicast linked at the top of this document to see UltiSnips snippets in action. === Outline of a document === Tagbar[https://github.com/majutsushi/tagbar] is a useful plugin to display an outline or a table of contents of a document.It uses Ctags, which you must install, too. Ctags does not support ConTeXt out of the box, but it is easy to extend.Create a <tt>.ctags</tt> file in your home directory, then copy and paste the syntax between following:  --langdef=context --regex-context=/^<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\\startsection<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\<nowiki>[[</nowiki>^<nowiki>]]</nowiki>*title<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*=<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\{<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*(.+)\}/\. \1/s,section/ --regex-context=/^<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\\startsubsection<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\<nowiki>[[</nowiki>^<nowiki>]]</nowiki>*title<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*=<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\{<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*(.+)\}/\.\. \1/s,subsection/ --regex-context=/^<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\\startsubsubsection<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\<nowiki>[[</nowiki>^<nowiki>]]</nowiki>*title<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*=<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\{<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*(.+)\}/\.\.\. \1/s,subsubsection/ --regex-context=/^<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\\startchapter<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\<nowiki>[[</nowiki>^<nowiki>]]</nowiki>*title<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*=<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\{<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*(.+)\}/\1/c,chapter/ --regex-context=/^<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\\startsubject<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\<nowiki>[[</nowiki>^<nowiki>]]</nowiki>*title<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*=<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\{<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*(.+)\}/SUBJ \1/c,subject/ --regex-context=/^<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\\startpart<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\<nowiki>[[</nowiki>^<nowiki>]]</nowiki>*title<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*=<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*\{<nowiki>[[</nowiki>:space:<nowiki>]]</nowiki>*(.+)\}/\1/p,part/ Put this in your <tt>vimrc</tt>: let g:tagbar_type_context = { \ 'ctagstype': 'context', \ 'kinds': [ \ 'p:parts', \ 'c:chapters', \ 's:sections' \ ], \ 'sort': 0 \ } That's it! See the image at the top of this document for an example. === Using LaTeX-Suite === [http://vim-latex.sourceforge.net/ latex-suite] currently doesn't support ConTeXt, but if you use it, here's what you have to do to compile ConTeXt documents: 1. After downloading and installing latex-suite, locate the file "texrc" (usually located in <code>btex~/.vim/ftplugin/verbatimtexlatex-suite</code> ).Copy this file to <code>~/.vim/ftplugin/tex/texrc</code> 2. Open this copy in your favorite editor (vim comes to mind...) 3. After line 80 in this file, there is a series of "Compiler rules." Just add this line to the section:  TexLet g:Tex_CompileRule_cont = 'texexec --pdf --nonstopmode $*' This will add compilation for ConTeXT. In order to use it: 4. When you're in vim normal mode, run this command:  TGTarget cont [that's "colon TGTarger cont"]  5. Edit your TeX-files, save the changes; when you want to compile, switch to normal mode and just type <code>etex\ll</code> as (that's '' 'backslash el el' '') Voila, compilation should start. You'll have to specify this compiler target every timeI you open a TeX-file in Vim.If you want to make this the default compiler, you should have this line in your texrc:  TexLet g:Tex_DefaultTargetFormat = 'cont'

unlet b[[Category:current_syntax syn include @texTop syntax/tex.vim " MetaPost has TeX inserts for typeset labels " verbatimtex, btex, and etex will be treated as keywords syn match mpTeXbegin "\(verbatimtex\|btex\)" syn match mpTeXend "etex" syn region mpTeXinsert start="\(verbatimtex\|btex\)"hs=e+1 end="etex"he=s-1 \ contains=@texTop,mpTeXbegin,mpTeXend containedin=ALL keependText Editors]]