Changes

httphttps://www.vim.org/

This page is about editing ConTeXt source in Vim, gVim, MacVim, NeoVim, and other Vim clones. Some of The page describes the described features are scripts available only in Vim v8.0.0047 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. == Using ConTeXt in Vim == 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>. == Filetype detection =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… (see <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 differentTeX from the current one (Plain TeXuseful 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 all </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#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>/bin:%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()</codett> 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>. From If you want to use more up-to-date files, overriding those distributed with Vim 7 onwards, you may proceed as follows. Assuming your Vim does some intelligent checking configuration 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</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 see it the file is previous <codett>plaintex\start…</codett> or <codett>\setup…</tt> command;* <tt>]}</tt>: jump to the next <tt>latex\stop…</codett> or <codett>context\setup…</codett>.command;

If the first line Each of a <code>*.tex</code> file has the form %&<format>then this determines the file type: <code>plaintex</code> (for Plain TeX), <code>context</code> (forConTeXt), or <code>tex<code> (for LaTeX)above accepts an optional count. OtherwiseFor example, the file is searched for keywords tochoose <code>context</code> or you may type <codett>tex3[{</codett>. If no keywords are found, it defaults to <code>plaintex</code>.jumpYou can change the default by defining the variable three <codett>g:tex_flavor\start…</codett> to the format(not the file type) you use most. Use one of these: let g:tex_flavor = "plain" let g:tex_flavor = "context" let g:tex_flavor = "latex"Currently no other formats are recognizedcommands before.

* If you You may use ConTeXt most of the time, but occasionally use LaTeX or Plain TeX, you can add the following to your <code>.vimrc</code> let g:tex_flavor = "context"* If you only use ConTeXt-specific text objects, you can add the following lines to be used in Visual or Operator-pending mode(see <codett>filetype.vim:help text-objects</codett>): " ConTeXt augroup filetypedetect au! BufRead,BufNewFile *.tex setfiletype context augroup ENDso the next time you open a <code>*.tex</code> file, Vim will always recognize it as a ConTeXt document.

Vim 7 has a built-So, for example, you may copy (“yank” in spell checker. To enable Vim's spell checking:jargon) a paragraph by typing <tt>ytp</tt> (“yank a TeX :set spellTo set the language to be used for spell checkingparagraph“), delete it with <tt>dtp</tt>, set the `spelllang` option accordingly. For example: :set spelllang=en_usUse lowercase letters (select it with <codett>en_usvtp</codett>, not reflow it with <codett>en_USgqtp</codett>)., etc…You can put such lines in your Similarly, you may yank a formula with <tt>vi$</tt> (or <codett>.vimrcva$</codett> if you like), and delete it, select it, etc…, in asimilar fashion.

== ftplugin 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 syntax file ==<tt>\stop…</tt> commands, or betweenmatching parentheses.

Nikolai Weibull was You may jump to a different file by positioning the first one who wrote contextcursor over the file name and typing <tt>gf</tt> (<tt>:help gf</tt>).vim files and submitted them to For example, if you have the official vim cvs repository.following in your document: \component my_componentThey are part of putting the official Vim 7cursor over <tt>my_component</tt> and pressing <tt>gf</tt> will open <tt>my_component.tex</tt>.

If you are using an older VimSimilarly, you can download may use <tt>[<c-i></tt> (this is square bracket followed by ctrl-i)to jump to the files at:definition of the word under the cursor (even if it is in a different* file), or <tt>[http:i<//cvstt> to display the (first line of the) definition under the status line.sourceforge.net/viewcvs.py/vim/vim7/runtime/syntax/context.vim runtime/syntax/context.vim] - syntax highlightingFor these and similar commands,* [httpsee <tt>:help include-search<//cvs.sourceforge.net/viewcvs.py/vim/vim7/runtime/ftplugin/contexttt>.vim runtime/ftplugin/context.vim] - filetype specific behaviour (like repeating comments at the beginning of line)

Vim offers excellent support for editing METAFONT and MetaPost documents (<btt>If you feel that something is missingmf</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, please contribute!such as <tt>\startMPpage… \stopMPpage</btt>.

Context complier plugin for vim is available from httpYou may embed other filetypes. Just define <tt>g:context_include</tt> (or <tt>b:context_include</wwwtt> forbuffer-specific settings).vim.orgFor example, if you want to highlight C++ code inside, say, <tt>\startCPP… \stopCPP</scripts/scripttt>,define: let g:context_include = { 'cpp' : 'CPP' }The key is the name of the filetype and the corresponding value is name of the command.php?script_id=1925

If you are using an older Vim, you may copy the following scripts from Vim's distribution (https://github.com/vim/vim) into correspondingfolders in your <tt>.vim</tt> folder (so, for example <tt>runtime/ftplugin/context.vim</tt> must be copied into<tt>~/.vim/ftplugin/context.vim</tt>):make %

which will also highlight the error messages runtime/autoload/context. If you prefer keymappingsvim runtime/autoload/contextcomplete.vim runtime/compiler/context.vim runtime/ftplugin/{context,mf,mp}.vim runtime/indent/{context,mf, you can addmp}.vim runtime/syntax/{context,mf,mp}.vim

nmap <F5b> Note:make %<cr/b>the runtime scripts in Vim 9.0.0218 or later are written in Vim 9 script (the new scripting language embedded in Vim) and there is no guarantee that they will work with older versions of Vim!

to your <code>.vimrc</code> If you get the following error when you open a ConTeXt or your <code>ftplugin/context.vim</code>, after which pressing <code><F5></code> will compile the file.MetaPost document:

* autocomplete: http:edit the syntax files and remove the <tt>syn iskeyword</tt> or <tt>syntax iskeyword</vimtt> line.sourceforgeInstead, put a corresponding command in <tt>~/.netvim/scripts/script.php?script_id=182, almost undocumented, but life-saving* spell-checker: http:after/ftplugin/wwwcontext.vim.org</scripts/script.php?script_id=499, but native spell-checking support is included in Vim 7 (see above).tt>:

setlocal iskeyword== using latex@,48-57,a-z,A-Z,192-suite ==255

[http:and in <tt>~/.vim/after/ftplugin/mp.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 documentstt> for MetaPost:

1. After downloading and installing latex-suite setlocal iskeyword=@, locate the file "texrc" (usually located in <code>~/.vim/ftplugin/latex-suite</code>). Copy this file to <code>~/.vim/ftplugin/tex/texrc</code>_

2Everything should work, at least with Vim 7. Open this copy in your favorite editor (vim comes to mind4...)

TexLet g* Some essential math support.* Proper URL highlighting ('%' doesn't start a comment, ...) [request by VnPenguin].* Perhaps borrow something from https:Tex_CompileRule_cont = 'texexec --pdf -//github.com/lervag/vimtex or http://vim-nonstopmode $*'latex.sourceforge.net/?

4TeX (Plain TeX), LaTex and ConTeXt all use the <tt>.tex</tt> extension for files, which makes it difficult to detect the filetype based on the extension. When you're in vim normal modeFrom Vim 7 onwards, run this command:Vim does some intelligent checking to see it the file is <tt>plaintex</tt> or <tt>latex</tt> or <tt>context</tt>.

If the first line of a <tt>*.tex</tt> file has the form TGTarget cont [that's %&<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 = "context" let g:tex_flavor = "colon TGTarger contlatex"] Currently no other formats are recognized.

5. Edit your * If you use ConTeXt most of the time, but occasionally use LaTeX or Plain TeX-files, save you can add the changes; when following to your <tt>vimrc</tt> let g:tex_flavor = "context"* If you want only use ConTeXt, you can add the following lines to compile<tt>filetype.vim</tt>: " ConTeXt augroup filetypedetect au! BufRead, switch to normal mode and just type BufNewFile *.tex setfiletype context augroup ENDso the next time you open a <codett>\ll*.tex</codett> (that's '' 'backslash el el' '')file, Vim will always recognize it as a ConTeXt document.

Vim 7 or later has a built-in spell checker. To 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. For example: TexLet g:Tex_DefaultTargetFormat set spelllang= 'cont' en_usUse lowercase letters (<tt>en_us</tt>, not <tt>en_US</tt>). When you set <tt>spelllang</tt>, Vim offers todownload the language data into your <tt>.vim</tt> folder, if such language is not available.You can put the above settings in your <tt>vimrc</tt> if you like.

In the following, <tt><leader></tt> denotes your “leader” (<tt>:help mapleader</tt>), that is,the prefix for user-defined mappings.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 in your <tt>vimrc</tt>: map <leader> ,Rather than overriding the default leader, you may define an alternative key. The <tt><space></tt> is a goodchoice, because by default it has the same function as the <tt><right></tt> key, and it is comfortable to type: map <space> <leader> " Use <space> as an alternative leader (backslash can still be used) === Clean up auxiliary files === The 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, ',') . '}', 1, 1) call delete(ff) endfor for dd in l:tmpdirs let l:subdir = l:currdir . '/' . dd if isdirectory(l:subdir) for ff in glob(l:subdir . '/*.{' . join(l:suffixes, ',') . '}', 1, 1) call delete(ff) endfor endif call delete(l:subdir) " Delete directory (only if empty) endfor echomsg "Aux files removed" endfCustomize <tt>l:tmpdirs</tt> and <tt>l:suffixes</tt> to suit your needs.In Windows systems, you may have to replace each slash with a backslash, too. The following mapping allows you to remove auxiliary files by pressing <tt>\tc</tt>: nnoremap <silent><buffer> <leader>tc :<c-u>call ConTeXtClean()<cr> === Snippets === Vim allows you to define abbreviations for frequently used pieces of text (see <tt>:help abbreviations</tt>).Here are a few examples:<pre>fun! Eatchar(pat) " See :help abbreviations let c = nr2char(getchar(0)) return (c =~ a:pat) ? '' : cendfun iab <buffer> ch- \startchapter[title={<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')<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> Type the abbreviation followed by Space to expand the snippet, then continue typing normally. Inside the definition of an abbreviation, marks may be set (see <tt>:h m</tt>), which allow you to jump between the differentparts of buffera snippet with TAB (CTRL-i) and CTRL-O (in Normal 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 stay in Insert mode after the jump), you will jump between <tt>\startchapter</tt>and <tt>\stopchapter</tt>. === Buffer-local insertInsert-mode macros to speed up ConTeXt source editing === (by By [[User:David antos|D.A.]] 19:52, 8 Jul 2005 (CEST)) 

==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:

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] In the asciicast at the top of this page MUcomplete was used. === UltiSnips === 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 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>~/.vim/ftplugin/latex-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:

Should highlight 5. Edit your TeX-files, save the syntax between changes; when you want to compile, switch to normal mode and just type <code>btex/verbatimtex\ll</code> ... <code>etex</code> as TeX.(that's '' 'backslash el el' '')

This doesnVoila, compilation should start. You't work 100% (problems with commands inside comments): ll have to specify this compiler target every timeI you open a TeX-file in Vim. If anyone knows how you want to repair thatmake this the default compiler, please do so. It would be nice if you should have this would have landed line in the official metapost syntax highlighting script for vim one day.your texrc:

unlet bTexLet g: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 startTex_DefaultTargetFormat ="\(verbatimtex\|btex\)"hs=e+1 end="etex"he=s-1 \ contains=@texTop,mpTeXbegin,mpTeXend containedin=ALL keepend'cont'