The same problem. It seems the \shellescapedquote generated to the wrong
position.
So vim complains the -c parameters is wrong.
Andy.
On Thu, Apr 9, 2009 at 4:22 PM, Aditya Mahajan
On Thu, 9 Apr 2009, Andy Wong wrote:
Hello,
I have tried the example using the vim mode to typeset some c codes. When I run the sample file, context stop with errors. the sample file and log file as list below. I use the windowsXP with the minimal context from ConTeXt garden and \write18 is enabled. From the log file, it seems the vim command is not properly quoted as follows:
MTXrun | executing: vim "-u NONE -e -C -n -V10log -c set" "tabstop=8 -c syntax" "on -c set" "syntax=c -c let" "contextstartline=1 -c let" "contextstopline=0 -c source" "c:/context/tex/texmf-context/tex/context/third/vim/2context.vim -c wqa vimdemo-vimsyntax.tmp " I check the t-vim.tex, the definition of the vim command is correct. I don't know why the \shellescapedquote is not properly resolved. Any help? thanks.
Does changing "noquote" to "noquotes" in line 797 of t-vim help?
Aditya
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net
___________________________________________________________________________________