From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typing within doifmode leads to error
Date: Sat, 20 Mar 2021 22:40:47 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2103202237060.819312@nqv-guvaxcnq> (raw)
In-Reply-To: <388305dc-1e93-e380-2274-35ed896af2c0@xs4all.nl>
On Sun, 21 Mar 2021, Hans Hagen wrote:
> On 3/20/2021 10:03 PM, Aditya Mahajan wrote:
> > On Sat, 20 Mar 2021, Hans Hagen wrote:
> >
> > > >
> > > > I wonder if we could have an environment, say \startluatemplate ...
> > > > \stopluatemplate, which is evaluated on the fly rather than when loading
> > > > a
> > > > file.
> > >
> > > define 'evaluated on the fly'
> >
> > Consider the following example:
> >
> > \enablemode[A]
> > \starttext
> > \startluatemplate
> > <?lua if tex.modes["A"] and not tex.modes["B"] then ?>
> > \starttyping
> > A and not B
> > \stoptyping
> > <?lua else ?>
> > \starttyping
> > not (A and not B)
> > \stoptyping
> > <?lua end ?>
> > \stopluatemplate
> > \stoptext
> >
> > What I am thinking is that \startluatemplate ... \stopluatemplate grabs the
> > content (like a buffer) and then processes it using the mkix conversion
> > mechanism. Thus, in terms of output, it should be equivalent to:
> >
> > \enablemode[A]
> > \starttext
> > \startbuffer[luatemplate]
> > <?lua if tex.modes["A"] and not tex.modes["B"] then ?>
> > \starttyping
> > A and not B
> > \stoptyping
> > <?lua else ?>
> > \starttyping
> > not (A and not B)
> > \stoptyping
> > <?lua end ?>
> > \stopbuffer
> > \savebuffer[file={\jobname-luatemplate.mkix}, list={luatemplate}]
> > \input \jobname-luatemplate.mkix
> > \stoptext
> >
> > but without the need to save to an external file.
> this is just for the mode right? in that case we can also can provide
>
> <?lua tex.enablemode("A") ?>
:-)
I don't use templates too often, so I don't have other examples in mind where the \startluatemplate ... \stopluatemplate might be needed. So, just adding tex.enablemode at the lua will also work. We can see if another use case comes up in the future!
Aditya
___________________________________________________________________________________
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:[~2021-03-21 2:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 3:58 Christoph Reller
2021-03-19 4:37 ` Aditya Mahajan
2021-03-19 6:59 ` Christoph Reller
2021-03-19 8:49 ` Hans Hagen
2021-03-20 5:24 ` Christoph Reller
2021-03-20 7:24 ` Aditya Mahajan
2021-03-20 11:11 ` Hans Hagen
2021-03-20 15:00 ` Christoph Reller
2021-03-20 17:07 ` Hans Hagen
2021-03-20 20:23 ` Aditya Mahajan
2021-03-20 20:49 ` Hans Hagen
2021-03-20 21:03 ` Aditya Mahajan
2021-03-21 1:43 ` Hans Hagen
2021-03-21 2:40 ` Aditya Mahajan [this message]
2021-03-21 14:44 ` Christoph Reller
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=nycvar.YAK.7.78.908.2103202237060.819312@nqv-guvaxcnq \
--to=adityam@umich.edu \
--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).