From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: custom itemize
Date: Fri, 04 Aug 2006 16:55:47 +0200 [thread overview]
Message-ID: <44D35FF3.7040405@elvenkind.com> (raw)
In-Reply-To: <44D35655.5030808@nibua-r.org>
Renaud AUBIN wrote:
>
> Hi all,
>
> Some times ago, Taco helps me to define a custom itemize:
> \setbox0=\hbox{--~}
> \def\indenteddash#1{\hskip\parindent--~}
> \definesymbol[indentdash][\indenteddash]
> \setupitemize[each][indentdash,packed,joinedup,intext][indentnext=yes,width=\dimexpr
> \parindent + \wd0 \relax]
> Now, I would a new custom itemize with numbered items:
>
> 1. first paragraph ..
> .... with a lot of text (multiline),
> 2. second paragraph ..
> .... with a lot of text (multiline).
>
> How to do that ?
\setbox0=\hbox{0.~}
\def\indenteddash#1{\hskip\parindent #1.~}
\defineconversion[indentdash][\indenteddash]
\setup... % as before
Taco
next prev parent reply other threads:[~2006-08-04 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 14:14 Renaud AUBIN
2006-08-04 14:55 ` Taco Hoekwater [this message]
2006-08-04 15:48 ` Renaud AUBIN
2006-08-07 17:16 ` 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=44D35FF3.7040405@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).