From: Harry <irgksjd@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: toc and macro
Date: Thu, 28 May 2015 23:08:08 +0200 [thread overview]
Message-ID: <556783B8.4070207@gmx.de> (raw)
In-Reply-To: <9017A010-A906-42BE-A407-7D9A482C475E@gmail.com>
What I want to do is something like this:
_______________________
\starttext
\completecontent[criterium=all]
% how i have to do it
\startchapter[colors][Colors]
\startsection,[black][Black]
black is a dark color
\stopsection,
\startsection[white][White]
white is light color
\stopsection
\stopchapter
% how i want it to write (with the same result of the code above)
\startSameCommand[colors][Colors]
\startSameCommand[black][Black]
black is a dark color
\stopSameCommand
\startSameCommand[white][White]
white is light color
\stopSameCommand
\stopSameCommand
\stoptext
_______________________
The \startSameCommand finds itself out (by the nesting of the command)
if its behave
as \startpart or \startchapter or \startsection or \startsubsection or
\startsubsubsection ...
Harry
Am 28.05.2015 um 12:47 schrieb Wolfgang Schuster:
>> Am 27.05.2015 um 20:13 schrieb Harry <irgksjd@gmx.de>:
>>
>> Hi,
>>
>> I hope that this is the right address to post my question. If not I
>> would be glad for a tip.
>>
>> I wanted to do something like this:
>>
>> _______________________
>>
>> \unprotect
>>
>> %This line uncommented leads to an error
>> \def\tit{Oops!}
>>
>> \def\Teil{\dodoubleempty\doTeil}
>> \def\doTeil[#1][#2]#3{%
>> \def\tit{#1}
>> %...
>> \startchapter[title={\tit},reference={#2}]
>> #3
>> \stopchapter
>> %...
>> }
>>
>>
>> \protect
>>
>> \starttext
>>
>> \completecontent
>>
>> \doTeil[Hallo][hallo]{Text Text Text Text Text Text Text}
> Why do you \doTeil and not not \Teil?
>
>> \stoptext
>>
>> _______________________
>>
>> It works if i use #1 direct (like this):
>> \startchapter[title=#1,reference={#2}]
>> But how can I wrap it in the \tit?
>> (wrapping #2 works fine)
>>
>> I wanted to programm \doTeil so, that I can nest it freely (for example
>> with \input) and the table of content uses the hierarchy of the nesting
>> to produce a nice TOC.
> Is there a reason why you can use use \chapter[<reference>][<title>] in your document,
> I can’t see any advantage with your command.
>
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2015-05-28 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 18:13 Harry
2015-05-28 10:47 ` Wolfgang Schuster
2015-05-28 21:08 ` Harry [this message]
2015-05-29 0:38 ` Wolfgang Schuster
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=556783B8.4070207@gmx.de \
--to=irgksjd@gmx.de \
--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).