ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: "Jairo A. del Rio" <jairoadelrio6@gmail.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Commands with arguments before in ConTeXt
Date: Mon, 29 Jun 2020 16:45:15 +0200	[thread overview]
Message-ID: <61992165-1cb4-6d23-ace1-6d205df1d743@xs4all.nl> (raw)
In-Reply-To: <CAKyqqaYm_3KVvyQ=_SvEgtEoa7W-n3dHxy7gPT5mhTSBOZX=LA@mail.gmail.com>

On 6/29/2020 3:48 PM, Jairo A. del Rio wrote:
> |Oh, I was just asking about
> 
> luatexbase.add_to_callback("process_input_buffer", blabla, "blabla" )|
> |
> |
> 
> |and
> |
> 
> |
> luatexbase.remove_from_callback("process_input_buffer", "blabla" )
> 
> |

We always had such things but I never advertise their usage.
> |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.
Well, good luck with that as it will never be robust (apart from 
possible performance issues) ... make sure you also parse macros and 
included styles and everything that can contain some nested funny 
syntax. (Read: when there are issues with that kind of parsing and 
interference with other preprocessing etc etc users are on their own i 
guess.)

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
___________________________________________________________________________________

      reply	other threads:[~2020-06-29 14:45 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
2020-06-29 14:45         ` Hans Hagen [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=61992165-1cb4-6d23-ace1-6d205df1d743@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=jairoadelrio6@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).