From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: is there a reason not to fix this bug?
Date: Sat, 10 Mar 2012 21:57:29 +0100 [thread overview]
Message-ID: <4F5BC039.2060808@web.de> (raw)
Dear community,
Wolfgang kindly suggested this fix (that works also with beta from today):
strc-lst.mkvi:
\def\strc_lists_place_indeed#tag#list#settings%
{\begingroup
\edef\currentlist{#tag}%
\setupcurrentlist[#settings]%
\the\everystructurelist
% \doif{\listparameter\c!coupling}\v!on{\startlistreferences{#tag}}%
\doplacestructurelist % maybe inline
{#list}%
{\listparameter\c!criterium}%
{\listparameter\c!number}%
{\listparameter\c!extras}%
{\listparameter\c!order}%
% \stoplistreferences
+ \par
\endgroup
\strc_lists_set_mode}
to fix the following bug with beta (first item on content
list is indented, but the second isn't):
\setuplist[chapter][alternative=d,margin=2em]
\starttext
\completecontent
\part{Part}
\chapter{Chapter}
a
\part{Part}
\chapter{Chapter}
b
\stoptext
I'm probably missing something, but this was reported two betas ago and
I reported this again on the previous beta.
I don't know whether this bug might not be fixed due to other reasons or
it was simply forgotten.
Many thanks for your awesome work,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2012-03-10 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 20:57 Pablo Rodríguez [this message]
2012-03-12 7:58 ` Hans Hagen
2012-03-18 16:22 ` Pablo Rodríguez
2012-03-12 7:59 ` Hans Hagen
2012-03-12 12:09 ` Wolfgang Schuster
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=4F5BC039.2060808@web.de \
--to=oinos@web.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).