From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Local TOC after each chapter title (was: Re: Need help)
Date: Thu, 19 Jul 2012 10:41:40 +0200 [thread overview]
Message-ID: <20120719104140.75affb22@homerow> (raw)
In-Reply-To: <6F67DBFE-40E8-4924-9BB1-8BF1443BC495@st.estfiles.de>
On 2012-07-19 Steffen Wolfrum <context@st.estfiles.de> wrote:
Hi Steffen
> > Nice, I didn't know that one, yet. Wikified under \setupheads.
>
>
> I searched for "insidesection" on this garden's page ...
>
> http://wiki.contextgarden.net/Command/setuphead
http://wiki.contextgarden.net/Command/setupheads
^^^
Technically the command belongs to \setupheads, not to \setuphead.
However, in practice it is unlikely that one wants to apply
insidesection to all structures, I agree.
> ... but couldn't find it.
It takes a while for the garden to refresh the search index. Now you
can find it by typing “insidesection” in the search box.
Marco
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-07-19 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 13:41 Need help Shiv Shankar Dayal
2012-07-18 14:15 ` Local TOC after each chapter title (was: Re: Need help) Marco
2012-07-18 14:21 ` Wolfgang Schuster
2012-07-18 14:56 ` Marco
2012-07-19 7:26 ` Steffen Wolfrum
2012-07-19 8:41 ` Marco [this message]
2012-07-19 9:53 ` Local TOC after each chapter title Hans Hagen
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=20120719104140.75affb22@homerow \
--to=netuse@lavabit.com \
--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).