From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Using \dorecheckindentation inside a group
Date: Fri, 10 Aug 2018 13:41:22 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.76.44.1808101334480.25707@ervasbepr.pvz.zptvyy.pn> (raw)
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
\protect
\definewhatever[whatever]
\setupindenting[big,yes]
\startbuffer
\input ward
\startwhatever
\input tufte
\stopwhatever
\input ward
\stopbuffer
\starttext
\section{With indentnext=yes}
\setupwhatever[indentnext=yes]
\getbuffer
\section{with indentnext=no}
\setupwhatever[indentnext=no]
\getbuffer
\section{with indentnext=auto}
\setupwhatever[indentnext=auto]
\getbuffer
\stoptext
I use a \begingroup inside \start_whatever to keep the definitions local
(otherwise \setupwhatever[#1][#2] will change the global setup). This
means that I have to use \dorecheckindentation \endgroup. As a result,
when I use `indentnext=auto`, the check for \par fails (see the third case
in the above example).
How can I fix this?
Thanks,
Aditya
[1]:
https://tex.stackexchange.com/questions/445198/context-break-paragraph-after-t-vim-code-block
___________________________________________________________________________________
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 reply other threads:[~2018-08-10 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 17:41 Aditya Mahajan [this message]
2018-08-10 18:00 ` Wolfgang Schuster
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=nycvar.YAK.7.76.44.1808101334480.25707@ervasbepr.pvz.zptvyy.pn \
--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).