From: "śrīrāma via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl, Damien Thiriet <damien@thiriet.web4me.fr>
Cc: śrīrāma <citturs@gmail.com>
Subject: Re: right item marks for associative questions? (śrīrāma)
Date: Sat, 16 Apr 2022 18:58:43 +0530 [thread overview]
Message-ID: <2636048.mvXUDI8C0e@sreeramtplt> (raw)
In-Reply-To: <YlqwN87iC990SsHo@valencay.home>
On 4/16/22 5:31 PM Damien Thiriet via ntg-context wrote:
> Could you explain the whereabouts of calling to context.(start|stop)()?
> Some expansion stuff?
I must admit that I am not a (LuaMetaT)eXpert. My limited understanding is
that it might be due to expansion and the behaviour of (start|stop)item, or
equivalently (start|stop)itemgroupitem. It does not seem to group like (most?)
other groups. (see strc-itm.mklx)
For instance if we switch to bold without grouping inside \(start|stop)item it
cascades through.
\startitemize[circle]
\startitem \bf First \stopitem
\startitem Second \stopitem
\startitem Third \stopitem
\startitem Fourth \stopitem
\stopitemize
In fact, you could just put the lefttoright call inside context.(bgroup|
egroup): see p. 196 of the cld manual. (start...stop are anyway ConTeXt'ized
versions of those).
Best,
Sreeram
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-04-16 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 12:01 Damien Thiriet via ntg-context
2022-04-16 13:28 ` śrīrāma via ntg-context [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=2636048.mvXUDI8C0e@sreeramtplt \
--to=ntg-context@ntg.nl \
--cc=citturs@gmail.com \
--cc=damien@thiriet.web4me.fr \
/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).