From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: \nomarking feature request
Date: Tue, 29 Nov 2005 13:30:03 +0100 [thread overview]
Message-ID: <438C49CB.5030603@elvenkind.com> (raw)
In-Reply-To: <438C31F7.3070305@wxs.nl>
Hans Hagen wrote:
> Taco Hoekwater wrote:
>
>> Hi Hans,
>>
>> Currently \nomarking expand into (essentially) \unknown.
>> Is it possible to make that configurable? I now have
>>
>> \section{title\nomarking{\footnote{note}}}
>> \marking[section]{title}
>>
>> and that is rather ugly (or is there a better way?)
>
>
> it is, kind of; copied from source:
>
> %\def\nomarking##1{\unknown\ }%
> \def\nomarking{\splitsequence{\getvalue{\??mk#1\c!limittext}}}%
Yes I saw that, but changing the language parameter has
side-effects :-)
My vote goes to removing the note markers altogether, btw.
Footnote symbols just do not belong inside \mark-ed stuff.
Cheers, Taco
next prev parent reply other threads:[~2005-11-29 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 9:31 Taco Hoekwater
2005-11-29 10:48 ` Hans Hagen
2005-11-29 12:30 ` Taco Hoekwater [this message]
2005-11-29 13:18 ` 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=438C49CB.5030603@elvenkind.com \
--to=taco@elvenkind.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).