From: Andre Caldas <andre.em.caldas@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Frozen callback.
Date: Mon, 1 Oct 2012 21:30:50 -0300 [thread overview]
Message-ID: <CADVh14U7ZDLxJUFP2+h4AjxORkHhsJJOV8_Zc6C623XSwcb9eA@mail.gmail.com> (raw)
In-Reply-To: <20121001200255.GC5059@phlegethon.router_intern>
>> I am trying to redefine the ’open_read_file’ callback.
>
> [...]
> direct callback access is disabled. There are usually some layers
> of abstraction on top of them, different ones for different
> callbacks. Mapping them all is a huge effort, so best refer to
> the source.
>
> In your case the function resolvers.openers.helpers.textopener()
> takes the place of the open_read_file callback. It can be found
> in data-tex.lua.
Shall I simply do something like this?
local function textopener(tag, filename, filehandle, coding)
result = old_textopener(tag, filename, filehandle, coding)
-- Do lots of things
return result
end
resolvers.openers.helpers.textopener = textopener
Thank you,
André Caldas.
___________________________________________________________________________________
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:[~2012-10-02 0:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 19:11 Andre Caldas
2012-10-01 20:02 ` Philipp Gesang
2012-10-02 0:30 ` Andre Caldas [this message]
2012-10-02 8:05 ` Hans Hagen
2012-10-02 11:31 ` Andre Caldas
2012-10-02 12:02 ` Sietse Brouwer
2012-10-02 12:13 ` Philipp Gesang
2012-10-02 12:37 ` Hans Hagen
2012-10-10 19:40 ` Andre Caldas
2012-10-02 11:41 ` Andre Caldas
2012-10-02 11:54 ` Wolfgang Schuster
2012-10-02 12:27 ` Hans Hagen
2012-10-01 20:49 ` Hans Hagen
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=CADVh14U7ZDLxJUFP2+h4AjxORkHhsJJOV8_Zc6C623XSwcb9eA@mail.gmail.com \
--to=andre.em.caldas@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).