From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Aditya Mahajan <adityam@umich.edu>
Subject: Re: Using \dorecheckindentation inside a group
Date: Fri, 10 Aug 2018 20:00:00 +0200 [thread overview]
Message-ID: <1858c907-c5e6-477e-e6cb-077a0888f508@gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.76.44.1808101334480.25707@ervasbepr.pvz.zptvyy.pn>
Aditya Mahajan schrieb am 10.08.18 um 19:41:
> Hi,
>
> In t-filter module, I use a group inside \startfilter ... \stopfilter
> to keep various definitions local. However, as reported on [1], this
> breaks the `indentnext` option. The following minimal example
> illustrates the issue:
>
> \unprotect
> \definenamespace
> [whatever]
> [
> name=whatever,
> command=yes,
> setup=list,
> parent=whatever,
> ]
>
> \appendtoks
> \setuevalue{\e!start\currentwhatever}{\start_whatever[\currentwhatever]}%
> \setuvalue {\e!stop\currentwhatever}{\stop_whatever}%
> \to \everydefinewhatever
>
> \starttexdefinition start_whatever
> \dodoubleargument\start_whatever_indeed
> \stoptexdefinition
>
> \starttexdefinition start_whatever_indeed[#1][#2]
> \begingroup % to keep assignments local
> \edef\currentwhatever{#1}
> \setupwhatever[#1][#2]
> \stoptexdefinition
>
> \starttexdefinition stop_whatever
> \useindentnextparameter\whateverparameter
> \dorechecknextindentation
> \endgroup
> \stoptexdefinition
Move \dorechecknextindentation after \endgroup.
\starttexdefinition stop_whatever
\useindentnextparameter\whateverparameter
\endgroup
\dorechecknextindentation
\stoptexdefinition
Wolfgang
___________________________________________________________________________________
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:[~2018-08-10 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 17:41 Aditya Mahajan
2018-08-10 18:00 ` Wolfgang Schuster [this message]
2018-08-10 19:49 ` Aditya Mahajan
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=1858c907-c5e6-477e-e6cb-077a0888f508@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=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).