I'm trying to use the t-vim module for context installed from the TexLive 2010 basic package for Mac.

The problem I'm running into is that MTXrun tries to quote too much when calling vim, for example:

vim "-u NONE -e -C -n -c \\\"set tabstop=8\\\" -c \\\"syntax on\\\" -c \\\"set syntax=ruby\\\" -c \\\"let contextstartline=1\\\" -c \\\"let contextstopline=0\\\" -c \\\"source /usr/local/texlive/2010basic/texmf-dist/tex/context/third/vim/2context.vim\\\" -c \\\"wqa\\\" \\\"a-vimsyntax.tmp\\\" "

The command I used to compile the tex file was "context" without any arguments.

Thanks in advance.

Code Used


\definevimtyping [RUBY] [syntax=ruby]
#! /usr/bin/ruby
# This is my first ruby program
puts "Hello World"

Full Log


  • Can you add the input you used as well? – Taco Hoekwater Jan 17 '11 at 9:13

Managed to solve it!

The t-vim.tex file at,


uses the following system command,

{mtxrun --verbose --noquote bin:vim
      "-u NONE  % No need to read unnessary configurations
       -e       % run in ex mode
       -C       % Set compatibile
       -n       % No swap
%      -V10log  % For debugging only, will go away later.
       -c \shellescapedquote set tabstop=\@@vstab \shellescapedquote\space    
       -c \shellescapedquote syntax on\shellescapedquote\space 
       -c \shellescapedquote set syntax=\@@vssyntax\shellescapedquote\space
       -c \shellescapedquote let contextstartline=\@@vsstart\shellescapedquote\space
       -c \shellescapedquote let contextstopline=\@@vsstop\shellescapedquote  \space
       -c \shellescapedquote source kpse:2context.vim\shellescapedquote\space
       -c \shellescapedquote wqa\shellescapedquote\space    
        \shellescapedquote#1\shellescapedquote\space "}

as you can see, it is using --noquote instead of --noquotes. Just add "s" and the problem should be fixed.


Can you check if the latest development version of t-vim works? For testing, copy t-vim.tex, t-filter.tex, and 2context.vim from here and place them in the same directory as your tex file.

  • Hi Aditya, my t-vim.tex version is 2008.07.15. But I managed to solve the problem. I would also upvote you if I could. – Pedro Jan 17 '11 at 18:57
  • @Pedro: Now you can. ;-) – lockstep Jan 17 '11 at 19:03
  • Already did :). – Pedro Jan 22 '11 at 10:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.