From: Stuart Jansen <sjansen@gurulabs.com>
Subject: Re: Lowercasing section titles
Date: Wed, 15 Jun 2005 10:25:05 -0600 [thread overview]
Message-ID: <1118852705.8830.15.camel@localhost.localdomain> (raw)
In-Reply-To: <42B04E7B.6060208@elvenkind.com>
[-- Attachment #1.1: Type: text/plain, Size: 359 bytes --]
On Wed, 2005-06-15 at 17:51 +0200, Taco Hoekwater wrote:
> % the unexpanded is because we do not want
> % actual \lowercase commands in the contents list
> \unexpanded\def\dodowncase{\lowercase}
Cool, thanks. That's a trick I've seen a few times but still haven't
learned to use properly.
--
Stuart Jansen <sjansen@gurulabs.com>
Guru Labs, L.C.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-06-15 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 21:05 Nikolai Weibull
2005-06-15 15:21 ` Stuart Jansen
2005-06-15 15:51 ` Taco Hoekwater
2005-06-15 16:25 ` Stuart Jansen [this message]
2005-06-15 17:47 ` Nikolai Weibull
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=1118852705.8830.15.camel@localhost.localdomain \
--to=sjansen@gurulabs.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).