From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: pretty C with MKIV
Date: Tue, 7 Jul 2009 13:09:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.00.0907071306300.31926@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4A537B46.9000705@wxs.nl>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1843 bytes --]
On Tue, 7 Jul 2009, Hans Hagen wrote:
> Aditya Mahajan wrote:
>> On Tue, 7 Jul 2009, Peter Münster wrote:
>>
>>> On Tue, 7 Jul 2009, Peter Münster wrote:
>>>
>>>> (I've tried t-vim.tex, but it seems to be broken:
>>>> ERROR: I can't find file `test-vimsyntax.tmp-vimsyntax.tmp'.)
>>>
>>> Ok, t-vim.tex works now. The mtxrun part was the problem. Here my new
>>> version of the \runvimsyntax macro (perhaps no more MS-Windows
>>> compatibility):
>>>
>>> \def\runvimsyntax#1
>>> {\executesystemcommand
>>> {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 "set tabstop=\@@vstab"
>>> -c "syntax on"
>>> -c "set syntax=\@@vssyntax"
>>> -c "let contextstartline=\@@vsstart"
>>> -c "let contextstopline=\@@vsstop"
>>> -c "source `kpsewhich 2context.vim`"
>>> -c "wqa" "#1"}}
>>
>> Hey, `kpsewhich 2context.vim` is cheating!
>>
>> In MkIV, I think that it should be possible to get the full file name
>> using luatex's kpse library. Once I figure that out, the call to mtxrun
>> can be omitted in a platform independent manner. However, I have no time
>> for it right now.
>
> starting point :
>
> mtxrun --run vim full:2context.vim
>
> inside a context run you can use
>
> resolvers.resolve("full:2context.vim")
>
> or just resolvers.find_file("2context.vim","other text file")
>
> so using:
>
> \ctxlua{os.execute("....")}
>
> should be doable
Thanks, this seems to work as expected. I will work on a new version that
will use resolvers.resolve in MkIV, and the old method in MkII.
Aditya
[-- 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-07-07 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 8:37 Peter Münster
2009-07-07 12:32 ` Peter Münster
2009-07-07 13:57 ` Renaud Aubin
2009-07-07 16:32 ` Aditya Mahajan
2009-07-07 16:43 ` Hans Hagen
2009-07-07 17:09 ` Aditya Mahajan [this message]
2009-07-08 8:26 ` Peter Münster
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=alpine.LNX.2.00.0907071306300.31926@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).