From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \bufferprefix in MKIV
Date: Thu, 27 Jan 2011 14:08:23 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1101271401440.16902@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <B852B191-57EC-4239-8B5F-9CFE2A8DEF3B@gmail.com>
On Wed, 26 Jan 2011, Wolfgang Schuster wrote:
>
> Am 26.01.2011 um 17:46 schrieb Mojca Miklavec:
>
>> Dear Hans,
>>
>> one of the latest versions of MKIV breaks the following code:
>> \edef\GNUPLOTfile {\bufferprefix gnuplot-\GNUPLOTnumber}%
>> since \bufferprefix is not defined any more. Is there any reason for
>> that? In particular ...
>
> You should also take a look into Adityas filter module.
On a unrelated note, I have been thinking if I can extend the filter
module to take care of features provided by lilypond and gnuplot modules.
IIUC, in both these modules, the input is transformed before being written
to an output file, then an external filter is run and the output is read
back again. If we restrict ourselves to MkIV, then the transforming the
input can be done in a lua function; the filter module already takes care
of the rest of the book-keeping.
Do you think that it makes sense to have such a feature? Then you could
just define the gnuplot module as:
\usemodule[filter]
\defineexternalfilter[GNUPLOT]
[filter={gnuplot --appropriate options},
conitnue=yes,
transformation=thirddata.GNUPLOT.transformation,
]
where thirddata.GNUPLOT.transformation is a lua function that does all the
fancy processing.
What do you think?
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-01-27 19:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 16:46 Mojca Miklavec
2011-01-26 22:53 ` Wolfgang Schuster
2011-01-26 23:13 ` Mojca Miklavec
2011-01-27 8:51 ` Hans Hagen
2011-01-27 19:08 ` Aditya Mahajan [this message]
2011-01-27 20:10 ` Hans Hagen
2011-01-27 23:37 ` Aditya Mahajan
2011-01-27 23:49 ` Mojca Miklavec
2011-01-28 1:00 ` Aditya Mahajan
2011-01-28 8:32 ` Hans Hagen
2011-01-27 23:36 ` Mojca Miklavec
2011-01-28 13:55 ` Henning Hraban Ramm
2011-01-28 20:18 ` Aditya Mahajan
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.01.1101271401440.16902@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).