From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: filter module: call function before calling the filter command?
Date: Thu, 13 Oct 2016 15:41:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.OSX.2.02.1610131537040.19840@nqv-znpobbx> (raw)
In-Reply-To: <E50A730F-EF80-4088-99F3-6EF9EFE018BA@fiee.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 968 bytes --]
On Wed, 12 Oct 2016, Henning Hraban Ramm wrote:
> Now, I’d like to overwrite "texsettings.ly", containing the setting of
> ConTeXt’s text width, each time before I call LilyPond, to adapt its
> note line width to the current text width. That would automate the line
> width adaption to e.g. columns.
>
> In the module’s documentation under "Dealing with expansion" I found the example of creating the filter command in a macro.
> Can I use this to call a Lua function first and then LilyPond? Or is there a better way?
There is an internal option: filtersetups that may be useful for what you
have in mind.
You can create a lua function, say lilypond.initialize(...), that does all
the initializations, and then write
\startsetups lilypond:initialize
\ctxlua{lilypond.initialize()}
\stopsetups
\defineexternalfilter[...]
[ ...
filtersetups=lilypond:initialize,
...
]
This is untested, but it should work.
Aditya
[-- Attachment #2: Type: text/plain, Size: 489 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://context.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-10-13 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 9:11 Henning Hraban Ramm
2016-10-13 22:41 ` Aditya Mahajan [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=alpine.OSX.2.02.1610131537040.19840@nqv-znpobbx \
--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).