Changes

httphttps://www.vim.org/

This page is about editing ConTeXt source in Vim, gVim, MacVim, NeoVim, and other Vim clones.The page describes the scripts available with in Vim v8.0.0055 or later. If you are using Vim 7, see

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 <btt>If you feel that something is missing, please contribute!:help ft-context</btt> Information about providing feedback is in the header of the scripts.

:ConTeXt%

Typesetting happens in the background if you are using Vim 8.0.0047 or later,so you may continue working on your document. If there are errors, the quickfix window opens will open automaticallyto show the errors (one per line). The cursor stays will stay in the main document, so your typing workflow is will notbe disrupted. You may use standard quickfix commands to jump between errors: <tt>:cfirst</tt>, <tt>:cprev</tt>,

running jobs with <tt>:ConTeXtStopJobs</tt> (these commands are available only in Vim 8.0.0047 or later).

An alternative way to typeset === Setting a document is to use <tt>:make</tt>. Set the current workingdirectory to the directory of the current buffer, then execute <tt>:make</tt>: lcd /path/to/my/project :makeIf a <tt>Makefile</tt> exists in the working directory, it is used (see below for a sample Makefile).You may <tt>let g:context_ignore_makefilecustom typesetting engine ===1</tt> to ignore an existing Makefile.If no Makefile is found, <tt>mtxrun</tt> will be invoked directly.Note that <tt>:make</tt> always performs synchronous typesetting. Also, if there areerrors, the quickfix list is populated, but you have open it manually with <tt>:copen</tt>.

It is recommended that you map the above commands. For example, you may add nnoremap The <silenttt> :ConTeXt<leader>/tt :<c-u>updatecommand invokes the <crtt>:ConTeXtmtxrun<cr/tt>to your script that is found in <tt>vimrc$PATH</tt>. For more fine grained control over the command and its environment, you may invoke `context.Typeset()` directly (or `context#Typeset(better) nnoremap ` from legacy Vim script). For instance, if you have installed a version of ConTeXt in <buffertt> $HOME/context<silent/tt> (where <leader>tt :<c-u>update$HOME<cr/tt>:ConTeXt<cr>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 <tt>~/.vim/after/ftplugin/context.vim</tt>, after which pressing <tt>\tt</tt> (where <tt>\</tt> is your leader key)will save creating the file and compile the file.directories if they do not exist):

You may customize the path to the <tt>mtxrun</tt> executable by setting <tt>g:context_mtxrun</tt>.For example, if you want to use your ConTeXt Beta installation at <tt>~/Applications/ConTeXt-Beta</tt>,and you are using macOS, you may set the variable as follows: let g:context_mtxrun = import autoload 'PATH=$HOME/Applications/ConTeXt-Beta/tex/texmf-osx-64/bin:$PATH mtxruncontext.vim'

You may enable synctex by setting <tt>g def MyConTeXt() const env = {'PATH':context_synctexprintf("%s/context/tex/texmf-</ttos> to -<ttarch>1</tt> bin:%s", $HOME, $PATH)} context.Typeset(the default is <tt>0</tt>"%", env): let g:context_synctex = 1enddef

You may pass and perhaps use it with a mapping:  nnoremap <silent><buffer><leader>t <ttscriptcmd>mtxrunMyConTeXt()</ttcr> additional options by putting them in  <tt>g:context_extra_optionscontext.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:  let gdef ConTeXtCustomCommand(path:context_extra_options = string): list<string> return ['mtxrun', '--arrange script', 'context', '--autopdfnonstopmode', path] enddef  context.ConTeXtTypeset("%", v:none, ConTeXtCustomCommand) === Working with large projects === Large projects are often organized as a root document and various chapterThe files. When editing a chapter file, it is convenient to invoke <tt>--autogenerate: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 specifies therelative path to the 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 syntax files === Vim includes syntax files generated by <tt>--nonstopmodemtxrun</tt> and . If you want to use more up-to-date files, overriding those distributed with Vim, you may proceed as follows. Assuming your Vim configuration lives in <tt>--synctex~/.vim</tt> options are always included in the, 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:

Finally, for each of the above variables, a corresponding buffer* <tt>context-local variable with the same namedata-context.vim</tt>;may be defined, whose value takes precedence over the global value* <tt>context-data-interfaces.vim</tt>;* <tt>context-data-metafun.vim</tt>;* <tt>context-data-tex.vim</tt>.

<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<upesc>`a`b<c-o>f}a<c-r>=Eatchar('\s')<cr> iab <buffer> s. - \startsection[title={<c-o>ma}]<cr><c-o>mb<cr>\stopsection<upesc>`a`b<c-o>f}a<c-r>=Eatchar('\s')<cr> iab <buffer> ss. - \startsubsection[title={<c-o>ma}]<cr><c-o>mb<cr>\stopsubsection<upesc>`a`b<c-o>f}a<c-r>=Eatchar('\s')<cr> iab <buffer> sss. - \startsubsubsection[title={<c-o>ma}]<cr><c-o>mb<cr>\stopsubsubsection<upesc>`a`b<c-o>f}a<c-r>=Eatchar('\s')<cr> iab <buffer> fig. slide- \startplacefigurestartslide[title={<c-o>ma}]<cr><c-o>mb<cr>\stopslide<esc>`a`b<c-o>a<c-r>=Eatchar('\s')<cr>iab <buffer> fig- \stopplacefigurestartplacefigure<upcr><tab>\externalfigure[<c-o>ma]%<cr>[]<c-o>2mb<cr><c-d>\stopplacefigure<esc>`a`b<c-o>a<leftc-r>=Eatchar('\s')<cr> iab <buffer> item. - \startitemize<cr><cr>\stopitemize<up><tab>\item iab <buffer> enum. - \startitemize[n]<cr><cr>\stopitemize<up><tab>\item iab <buffer> i. - \item</pre> Type the abbreviation (including the dot) followed by CTRL-] Space to expand the snippet, thencontinue typing normally.Abbreviations Inside the definition of an abbreviation, marks may be triggered by any other non-keyword character set (see <tt>:h m</tt>), which allow you to jump between the different from parts of a 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> (orbut in that case such character is inserted <tt><c-o><tab></tt> if you want to stay in Insert mode after the textjump), you will jump between <tt>\startchapter</tt>and <tt>\stopchapter</tt>.

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

* µcompleteMUcomplete[https://github.com/lifepillar/vim-mucomplete]* Coc [https://github.com/neoclide/coc.nvim].

In the asciicast at the top of this page µcomplete MUcomplete was used.