From: Yanrui Li <liyanrui.m2@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Can not register the callback functions in MkIV
Date: Fri, 19 Feb 2010 20:21:31 +0800 [thread overview]
Message-ID: <c3f901471002190421n53d2ec18m32af722f989dae34@mail.gmail.com> (raw)
In-Reply-To: <c3f901471002182304y5e4b4242kfcf984fc93d5de6f@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 851 bytes --]
2010/2/19 Yanrui Li <liyanrui.m2@gmail.com>
> Hi,
>
> Now it seems that we have not allowed to register the callback functions
> since beta 2010.02.18.
>
> For example:
>
> \startluacode
>
> local old_pre_linebreak_filter = callback.find ('pre_linebreak_filter')
>
> local function my_pre_linebreak_filter (head, groupcode)
> if old_pre_linebreak_filter then
> old_pre_linebreak_filter (head, groupcode)
> end
> print ('This is my pre_linebreak_callback')
> return true
> end
>
> callback.register ('pre_linebreak_filter', my_pre_linebreak_filter)
>
> \stopluacode
>
> \starttext
>
> This is just a test!
>
> \stoptext
>
> The 'my_pre_linebreak_filter' function can not work again. Is this a bug?
>
> --
> Best regards,
>
> Li Yanrui
>
I see. The 'pre_linebreak_filter' callback function is frozen.
--
Best regards,
Li Yanrui
[-- Attachment #1.2: Type: text/html, Size: 1299 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-02-19 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 7:04 Yanrui Li
2010-02-19 12:21 ` Yanrui Li [this message]
2010-02-19 13:05 ` 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=c3f901471002190421n53d2ec18m32af722f989dae34@mail.gmail.com \
--to=liyanrui.m2@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).