From: Berend de Boer <berend@pobox.com>
Cc: ntg-context@ntg.nl
Subject: Re: Unexpected side effects when using \cap in custom headings
Date: Tue, 14 Nov 2000 16:05:12 +0100 [thread overview]
Message-ID: <3A1154A8.3BDCBE32@pobox.com> (raw)
In-Reply-To: <3.0.6.32.20001114145043.013f0780@pop.wxs.nl>
Hans Hagen wrote:
> The problem is that #2 is more than just the text, it's a bunch of terrible
> things. [try \showargument{#2}]
Yep, can't you filter that out? It would be easiest of #2 contained only
the text without any styles/colors and whatsoever.
> Seems like you need a hook to the text.
I first thought that the textcommand option might be the one. But it
doesn't like command being defined or so.
Groetjes,
Berend. (-:
next prev parent reply other threads:[~2000-11-14 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 12:19 Berend de Boer
2000-11-14 13:50 ` Hans Hagen
2000-11-14 15:05 ` Berend de Boer [this message]
2000-11-14 15:51 ` 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=3A1154A8.3BDCBE32@pobox.com \
--to=berend@pobox.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).