ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: vbox construct breaking MKII
Date: Wed, 04 Aug 2010 23:20:42 +0200	[thread overview]
Message-ID: <4C59D9AA.90206@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.1008041534590.18669@ybpnyubfg.ybpnyqbznva>

On 4-8-2010 9:36, Aditya Mahajan wrote:
> On Wed, 4 Aug 2010, Hans Hagen wrote:
>
>> On 4-8-2010 7:23, Aditya Mahajan wrote:
>>
>>> (that writes contents to file and inputs the result) but cannot easily
>>> create \typevimTEX. For that I will need to reimplement all the catcode
>>> trickery of \definetype and \definebuffer.
>>
>> \definetype[TEXtype][option=TEX]
>>
>> test \TEXtype{oeps \test{oeps}} test
>
> But I want to store the argument "oeps \test{oeps}" in an external file,
> process that external file with vim, and \input the result.

As pretty printing happens in lua, you can intercept the string there. 
Just look at pret-*.lua: there is a visualizer.flush_line in there that 
can write to a file, apply vim, and read in the result (can also be 
words instead of lines).

Hans



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2010-08-04 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  7:16 Willi Egger
2010-08-04  8:19 ` Hans Hagen
2010-08-04 16:51   ` Aditya Mahajan
2010-08-04 16:51     ` Hans Hagen
2010-08-04 17:23       ` Aditya Mahajan
2010-08-04 18:21         ` Hans Hagen
2010-08-04 19:36           ` Aditya Mahajan
2010-08-04 21:20             ` Hans Hagen [this message]

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=4C59D9AA.90206@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=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).