From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: ToC Problem
Date: Sun, 05 Feb 2006 12:45:01 +0100 [thread overview]
Message-ID: <43E5E53D.9040301@elvenkind.com> (raw)
In-Reply-To: <e65d34bf0602041630g736a14f4i@mail.gmail.com>
Elliot Clifton wrote:
> The list will render correctly but not the ToC. I could use the list
> rather than the combined list, but I want get combined list working as I
> have yet to have any success with them whem using my own heads.
>
> Any ideas what I'm doing wrong?
It works for me. But your definition of success may be different
from mine, so I suggest posting a minimal file exhibiting the error.
Taco
next prev parent reply other threads:[~2006-02-05 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 0:30 Elliot Clifton
2006-02-05 11:45 ` Taco Hoekwater [this message]
2006-02-05 23:04 ToC problem Elliot Clifton
2006-02-06 10:18 ` Taco Hoekwater
2006-02-06 14:08 Elliot Clifton
2006-02-06 15:16 ` Taco Hoekwater
2006-02-06 18:10 Elliot Clifton
2006-02-11 16:49 Elliot Clifton
2006-02-12 10:42 ` Taco Hoekwater
2006-02-12 11:26 Elliot Clifton
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=43E5E53D.9040301@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).