From: "Alan Stone" <software.list.1es9s@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: goto(box) and setuplist questions
Date: Wed, 6 Aug 2008 12:16:49 +0200 [thread overview]
Message-ID: <326847810808060316h640a76c4ra7c60489fa63c7a3@mail.gmail.com> (raw)
In-Reply-To: <115224fb0808060145q728bcde5od601ca08c316047d@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1334 bytes --]
On Wed, Aug 6, 2008 at 10:45 AM, Wolfgang Schuster <
schuster.wolfgang@googlemail.com> wrote:
> It works.
Ahaa! Now it does. I misunderstood. Thanks.
> What's the reason for this Wolfgang ? From what I understood
> > from the main manual, it logically should be distance=(x>0)pt.
>
> 'width' is the width of the box for the number and 'distance' is the
> distance between the numberbox and the text.
Indeed, so normally you should be setting distance=(x>0)pt instead of
the width trickery. Hence my question.
> The result is something like:
>
> \hbox to 1em{1\hfil}\hskip 0pt{chapter title ...}
> ^^ ^^
> width distance
Sorry, TeX is currently still like Klingon to me. Thanks anyway.
Hans wrote:
>> - maxwidth ?
>
>just try it on long entries .. it prevents too long lines
>
>this is a very long entry
>this is a very ...
Ok I see. Now, in \placecontent or \setuplist, which parameter
allows to influence where long lines are cut off in two (or more) ?
Like...
(number) This long long
chapter title (pagenumber)
vs.
(number) This long
long chapter title (pagenumber)
Using the brute force tactic I tried setting width and textwith which didn't
work.
It could be textcommand. If so what does \command#1 mean ( see main
manual pg 150 ) ?
Best,
Alan
[-- Attachment #1.2: Type: text/html, Size: 2416 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-08-06 10:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 11:06 Alan Stone
2008-08-04 12:23 ` Hans Hagen
2008-08-04 14:44 ` Alan Stone
2008-08-04 14:52 ` Wolfgang Schuster
2008-08-04 20:57 ` Alan Stone
2008-08-05 8:29 ` Wolfgang Schuster
2008-08-05 11:07 ` Alan Stone
2008-08-05 11:16 ` Wolfgang Schuster
2008-08-06 7:12 ` Alan Stone
2008-08-06 8:45 ` Wolfgang Schuster
2008-08-06 10:16 ` Alan Stone [this message]
2008-08-06 13:26 ` Wolfgang Schuster
2008-08-06 14:15 ` Alan Stone
2008-08-06 14:59 ` Wolfgang Schuster
2008-08-06 16:07 ` Alan Stone
2008-08-06 18:45 ` Alan Stone
2008-08-07 6:26 ` Wolfgang Schuster
2008-08-07 7:48 ` Wolfgang Schuster
2008-08-07 6:24 ` Wolfgang Schuster
2008-08-06 15:03 ` Wolfgang Schuster
2008-08-06 15:13 ` Alan Stone
2008-08-06 10:25 ` Alan Stone
2008-08-06 11:03 ` Wolfgang Schuster
2008-08-06 12:09 ` Alan Stone
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=326847810808060316h640a76c4ra7c60489fa63c7a3@mail.gmail.com \
--to=software.list.1es9s@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).