From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Can modes be used for content control?
Date: Wed, 17 Nov 2021 12:32:56 +0100 [thread overview]
Message-ID: <21459DDE-4902-4E91-80E5-814B23D8FBCA@fiee.net> (raw)
In-Reply-To: <op.1czew7caejo439@desktop-mt1m160>
> Am 17.11.2021 um 04:06 schrieb Idris Samawi Hamid ادريس سماوي حامد via ntg-context <ntg-context@ntg.nl>:
>
> Unfortunately - as pointed out on the wiki - modes cannot be nested.
Why would you need that?
You know about \startnotmode and that you can use lists of modes?
\startmode[short,long]
Something that appears everywhere.
\stopmode
\startmode[long] % or \startnotmode[short]
Something that’s only in the long version.
\stopmode
There are also language modes (\startmode[*en]) that might be handy with translations.
> Furthermore, each mode is unique and there is apparently no inheritance/continuance.
Can you give an example for a use case?
> What is needed is something like this
>
> \startmode[abridged]
> \input knuth
>
> \startmode[unabridged]
> \startblockquote
> \input ward
> \stopblockquote
> \stopmode
>
> \input zapf
> \stopmode
That looks to me like flawed logic – why should content for the unabridged version appear within the abridged version?
It might be a bit annoying, but you could end the previous mode before starting the next.
And, as mentioned above, you can use \startmode with lists.
HTH
Hraban
___________________________________________________________________________________
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-11-17 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 23:25 Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 0:23 ` Aditya Mahajan via ntg-context
2021-11-17 3:06 ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 11:32 ` Henning Hraban Ramm via ntg-context [this message]
2021-11-17 15:08 ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 15:51 ` Henning Hraban Ramm via ntg-context
2021-11-17 19:52 ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 15:57 ` Taco Hoekwater via ntg-context
2021-11-17 17:56 ` Aditya Mahajan via ntg-context
2021-11-17 18:54 ` Hans Hagen via ntg-context
2021-11-17 19:45 ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 19:36 ` Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2021-11-17 7:59 ` Hans Hagen via ntg-context
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=21459DDE-4902-4E91-80E5-814B23D8FBCA@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).