From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: Alan BRASLAU <alan.braslau@cea.fr>
Cc: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Peter Münster" <pmlists@free.fr>
Subject: Re: nomarking function in MKIV
Date: Thu, 01 Jul 2010 10:30:36 +0200 [thread overview]
Message-ID: <4C2C522C.8030506@googlemail.com> (raw)
In-Reply-To: <201007011016.04168.alan.braslau@cea.fr>
Am 01.07.10 10:16, schrieb Alan BRASLAU:
> On Thursday 01 July 2010 00:35:44 Wolfgang Schuster wrote:
>
>> Am 30.06.10 10:19, schrieb Alan BRASLAU:
>>
>>> Additionally,
>>> \chapter [title={First chapter},list={First}]
>>> does not work. Logically this should work just as \startchapter.
>>>
>> This won't happen
>>
> So it is not a good idea?
> Or just complicated to implement, currently?
>
It's possible but Hans answer is he will not implement this. Since he
also removed
the paragraph delimited versions of the header commands (\chapter
...\par) your
chances for extensions are very low.
>> but what you can do is to write a macro which accepts
>> different values for
>> headers/footers, the running text and the toc (i know the entries in the
>> toc and text are wrong).
>>
> There is an entire class of users who will not get involved
> writing macros, for whom \unprotect \protect is unknown.
> I know that this is certainly *not* your case.
>
What i tried to show with my example this what's possible to get around
with the limitations but my code does not work and won't work with the
help of Hans because it needs hocks in the list macros (there is currently
no automated way to tell whether you're in a list or not).
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-07-01 8:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 16:14 John Devereux
2010-06-29 17:33 ` Peter Münster
2010-06-29 21:03 ` John Devereux
2010-06-30 8:19 ` Alan BRASLAU
2010-06-30 9:03 ` Peter Münster
2010-06-30 10:03 ` nomarking function in MKIV (selector) Alan BRASLAU
2010-06-30 22:35 ` nomarking function in MKIV Wolfgang Schuster
2010-07-01 8:16 ` Alan BRASLAU
2010-07-01 8:30 ` Wolfgang Schuster [this message]
2010-07-01 9:23 ` Peter Münster
2010-07-01 9:44 ` Alan BRASLAU
2010-07-01 9:55 ` luigi scarso
2010-07-01 10:00 ` Thomas A. Schmitz
2010-07-01 10:23 ` luigi scarso
2010-07-01 18:59 ` Alan BRASLAU
2010-07-02 8:18 ` Thomas A. Schmitz
2010-07-02 9:18 ` luigi scarso
2010-07-02 11:07 ` Alan BRASLAU
2010-07-01 10:11 ` Henning Hraban Ramm
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=4C2C522C.8030506@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=pmlists@free.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).