From: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
luigi scarso <luigi.scarso@gmail.com>
Subject: Re: Commands with arguments before in ConTeXt
Date: Mon, 29 Jun 2020 05:21:38 -0500 [thread overview]
Message-ID: <CAKyqqabpipB10E_JBCAst9sYxMYEi9UvcwEQWn34KLYub1wY0g@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsCjN9HbzR347JdOsQE0dzu8mmjPbEAAYTChVomqJyHFSg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1440 bytes --]
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.
Jairo :)
El lun., 29 de jun. de 2020 a la(s) 02:50, luigi scarso (
luigi.scarso@gmail.com) escribió:
>
>
> On Sun, Jun 28, 2020 at 10:48 PM Jairo A. del Rio <jairoadelrio6@gmail.com>
> wrote:
>
>> I've read the following is not possible in TeX
>>
>> \def#1\macro{blabla#1}
>>
>> where arguments come before. The only partial exceptions are commands
>> like \atop or \over, which are in fact primitives. Is there a way to do
>> this in ConTeXt?
>>
>>
> you can build a lpeg and parse the your "extended tex" source, obtaining a
> valid tex source.
>
>
> --
> luigi
>
> ___________________________________________________________________________________
> 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: 2656 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 10:21 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 [this message]
2020-06-29 13:27 ` Hans Hagen
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=CAKyqqabpipB10E_JBCAst9sYxMYEi9UvcwEQWn34KLYub1wY0g@mail.gmail.com \
--to=jairoadelrio6@gmail.com \
--cc=luigi.scarso@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).