From: Andy Wong <andywong1981@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: t-vim failed under windows
Date: Thu, 9 Apr 2009 19:06:24 -0500 [thread overview]
Message-ID: <bf0ab5a50904091706oede54dej56afe7a8aa6e75a0@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0904091721390.27169@ybpnyubfg.ybpnyqbznva>
[-- Attachment #1.1: Type: text/plain, Size: 1685 bytes --]
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 <adityam@umich.edu> wrote:
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 2601 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-04-10 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 15:31 Andy Wong
2009-04-09 21:22 ` Aditya Mahajan
2009-04-10 0:06 ` Andy Wong [this message]
2009-04-10 2:54 ` Aditya Mahajan
2009-04-10 13:59 ` Andy
2009-04-10 14:22 ` Aditya Mahajan
2009-04-10 15:12 ` Andy Wong
2009-04-10 20:13 ` Aditya Mahajan
2009-04-10 20:23 ` Andy Wong
2009-04-10 20:28 ` Aditya Mahajan
2009-04-10 20:33 ` Andy Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf0ab5a50904091706oede54dej56afe7a8aa6e75a0@mail.gmail.com \
--to=andywong1981@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).