From: "Willi Egger" <w.egger@boede.nl>
Subject: Re: compound titles, lists and headers
Date: Fri, 14 Feb 2003 22:21:37 +0100 [thread overview]
Message-ID: <006c01c2d46f$14bc7a70$0100a8c0@vademecum> (raw)
In-Reply-To: <7D3EAC38-4037-11D7-A0B0-0030659899AA@fiee.net>
Hi Hraban,
Weil die Katze das Mausen nicht lassen kann ...
> That works, but it's not what I asked after.
> I need a CRLF *in* the faked chapter name, no blank line between some
> entries.
\def\Eintrag#1{\writetolist[chapter]{%
\framed[{frame=on,align=right,width=0.5\textwidth,height=2.5\bodyfontsize}]{
#1}}}
May be this is not anwering everything. In my test file I was able to
produce a TOC where different length of entries did break into two lines...
Willi
next prev parent reply other threads:[~2003-02-14 21:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 21:05 Henning Hraban Ramm
2003-02-13 21:45 ` Willi Egger
2003-02-14 16:15 ` Henning Hraban Ramm
2003-02-14 21:21 ` Willi Egger [this message]
2003-02-14 22:40 ` Henning Hraban Ramm
2003-02-15 11:23 ` Willi Egger
2003-02-16 23:31 ` Hans Hagen
2003-02-17 21:54 ` Henning Hraban Ramm
2010-09-26 15:54 ` Tomas Bures
2010-09-26 16:06 ` Wolfgang Schuster
2010-09-26 18:39 ` Tomas Bures
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='006c01c2d46f$14bc7a70$0100a8c0@vademecum' \
--to=w.egger@boede.nl \
--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).