From: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Commands with arguments before in ConTeXt
Date: Mon, 29 Jun 2020 08:48:53 -0500 [thread overview]
Message-ID: <CAKyqqaYm_3KVvyQ=_SvEgtEoa7W-n3dHxy7gPT5mhTSBOZX=LA@mail.gmail.com> (raw)
In-Reply-To: <e6bf62c6-30e4-b4e8-64be-c5593c3080e3@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2303 bytes --]
Oh, I was just asking about
luatexbase.add_to_callback("process_input_buffer", blabla, "blabla" )
and
luatexbase.remove_from_callback("process_input_buffer", "blabla" )
LuaLaTeX users do that way and I want to be sure it won't interfere
with ConTeXt way of doing things so I can play with the suggestion
made by Luigi.
Regards,
Jairo :)
El lun., 29 de jun. de 2020 a la(s) 08:27, Hans Hagen (j.hagen@xs4all.nl)
escribió:
> On 6/29/2020 12:21 PM, Jairo A. del Rio wrote:
> > Wouldn't it be slow for larger documents? I will try anyway. By the way,
> > I've seen Lua(La)TeX users recurring to callbacks (process input buffer)
> > to make string replacements and I've done so myself sometimes. Does
> > ConTeXt do preprocessing the same way or is a better alternative
> > possible? Thank you very much.
> You mean "Does context use callbacks?" You can bet on that. It is how we
> came to implementing callbacks (over a decade ago now, Taco and I spend
> quite some time exploring all these things in the process of luatex dev
> ... fond memories and so).
>
> I don't know what latex does but context doesn't do much input
> processing apart from some unicode related juggling. There are plenty of
> ways to hook in additional processing but there are multiple ways to
> solve problems. Most of these mechanism in context are already pretty
> old and hardly change.
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 4380 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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 : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-29 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 20:48 Jairo A. del Rio
2020-06-29 7:28 ` Hans Hagen
2020-06-29 10:15 ` Jairo A. del Rio
2020-06-29 10:36 ` Taco Hoekwater
2020-06-29 11:06 ` Taco Hoekwater
2020-06-29 13:21 ` Hans Hagen
2020-06-30 0:18 ` Jairo A. del Rio
2020-06-29 7:50 ` luigi scarso
2020-06-29 10:21 ` Jairo A. del Rio
2020-06-29 13:27 ` Hans Hagen
2020-06-29 13:48 ` Jairo A. del Rio [this message]
2020-06-29 14:45 ` 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='CAKyqqaYm_3KVvyQ=_SvEgtEoa7W-n3dHxy7gPT5mhTSBOZX=LA@mail.gmail.com' \
--to=jairoadelrio6@gmail.com \
--cc=j.hagen@xs4all.nl \
--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).