From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Commands with arguments before in ConTeXt
Date: Mon, 29 Jun 2020 15:27:11 +0200 [thread overview]
Message-ID: <e6bf62c6-30e4-b4e8-64be-c5593c3080e3@xs4all.nl> (raw)
In-Reply-To: <CAKyqqabpipB10E_JBCAst9sYxMYEi9UvcwEQWn34KLYub1wY0g@mail.gmail.com>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-29 13:27 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 [this message]
2020-06-29 13:48 ` Jairo A. del Rio
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=e6bf62c6-30e4-b4e8-64be-c5593c3080e3@xs4all.nl \
--to=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).