ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: setupitemize confusion
Date: Thu, 27 Jul 2006 07:54:04 +0200	[thread overview]
Message-ID: <EFE9E0A9-E8A2-463F-8D89-0E52E88BB325@st.estfiles.de> (raw)
In-Reply-To: <Pine.WNT.4.63.0607270131300.3664@nqvgln>


Am 27.07.2006 um 07:32 schrieb Aditya Mahajan:

> On Wed, 26 Jul 2006, Steffen Wolfrum wrote:
>
>> Hi,
>>
>> both paragraph should be indented 12 pt. But there are different:
>>
>> \starttext
>>
>> \startitemize[width=12pt]
>> \sym{\endash}\input tufte
>> \stopitemize
>>
>> \setupitemize[width=12pt]
>> \sym{\endash}\input tufte
>>
>> \stoptext
>>
>>
>> How do I make the second the same as the first?
>
> Shouldn't you wrap the second one with \startstop itemize?
>
> \setupitemize[width=12pt]
> \startitemize
> \sym{\endash}\input tufte
> \stopitemize
>
> Aditya



Well, I hope not!

As far as I understood the manual (cont-eni) one can use \item and  
\sym also without the start-stop environment: in cases where it is  
just needed as one entry (not a list).
This works, somehow. But is there no setup possible?

I need it in a bibliography: the normal entries "author, title etc.  
maybe two lines" are hangindented with \hangafter=1\hangindent=12pt.
But when a author has two or more titles it is written "- title etc.  
maybe two lines". And here the "- " must be the same space as the  
hangindent (12pt), as one can imagine easily.
That's why I used a \item res. \sym for this. And a start/stop each  
would make the code quite chaotic.

But maybe there is even another solution for this construction, even  
better?

Steffen

  reply	other threads:[~2006-07-27  5:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 21:58 Steffen Wolfrum
2006-07-27  5:32 ` Aditya Mahajan
2006-07-27  5:54   ` Steffen Wolfrum [this message]
2006-07-27  6:05     ` Aditya Mahajan
2006-07-27  6:17       ` Steffen Wolfrum
2006-07-27  6:57         ` Renaud AUBIN
2006-07-27  7:43           ` Taco Hoekwater
2006-07-27  7:50             ` Renaud AUBIN
2006-07-27  7:11         ` Renaud AUBIN
2006-07-27  7:50           ` Steffen Wolfrum
2006-07-27  8:36             ` Taco Hoekwater
2006-07-27  8:58               ` Steffen Wolfrum

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=EFE9E0A9-E8A2-463F-8D89-0E52E88BB325@st.estfiles.de \
    --to=context@st.estfiles.de \
    --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).