From: "Jeff Smith" <ascarel@gmail.com>
Subject: Re: Header number separator
Date: Thu, 9 Nov 2006 11:54:50 -0500 [thread overview]
Message-ID: <2e8813a0611090854i59a71b36uc06372f310a98b9b@mail.gmail.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0611071716170.4048@nqvgln>
On 11/7/06, Aditya Mahajan <adityam@umich.edu> wrote:
> I need this functionality for a project (IEEE conference style), so
> here is hack to get the feature. The referencing also works.
>
> Use with caution, can break existing macros.
Wow, thanks a lot! This works as expected. In what situation can it
break existing macros? I intend to use that extensively but in a
fairly simple document (a thesis... yeah, another one in ConTeXt!). Is
there anything I should _not_ do?
Thanks again for your help! It's always greatly appreciated.
Jeff
next prev parent reply other threads:[~2006-11-09 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 19:43 Jeff Smith
2006-11-07 21:42 ` Aditya Mahajan
2006-11-07 22:22 ` Aditya Mahajan
2006-11-09 16:54 ` Jeff Smith [this message]
2006-11-09 18:39 ` Aditya Mahajan
2006-11-14 11:33 ` Hans Hagen
2006-11-14 16:53 ` Aditya Mahajan
2006-11-14 16:57 ` Hans Hagen
2006-11-15 15:38 ` Hans Hagen
2006-11-16 1:14 ` Aditya Mahajan
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=2e8813a0611090854i59a71b36uc06372f310a98b9b@mail.gmail.com \
--to=ascarel@gmail.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).