From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Beta: bug in \setuphead[chapter]
Date: Tue, 3 Jan 2012 06:41:34 +0100 [thread overview]
Message-ID: <29F3E85B-66B3-49BD-9E79-C6717F454513@gmail.com> (raw)
Dear Hans, dear all,
My best wishes to all the community for this New Year!
With the latest beta, \setuphead[chapter] has a strange behavior: the order of two keys seems to be important…
More precisely
\setuphead
[chapter]
[header=high,
align=middle
]
results in an error (see below), while
\setuphead
[chapter]
[align=middle,
header=high
]
works as expected (I had a tough time to find the bug and this minimal example…).
Minimal example that does not work:
%%% begin bug-setuphead.tex
\setuphead
[chapter]
[header=high,
align=middle
]
\starttext
\chapter{My chapter title}
\input knuth
\stoptext
%%% end bug-setuphead.tex
The error message points to:
\page_layouts_synchronize_element_indeed ...ounds
\else \ifx \previoustextst...
\page_layouts_synchronize_element ...t_indeed {#1}
\fi
<inserted text> ..._element \currentlayoutelement
\fi
\docommand ...=high]\the \everysetuplayoutelement
\next1 #1,->\docommand {#1}
\syst_helpers_do_process_comma_item
\syst_helpers_do_process_comma_list ...rgument #1,
]\relax \global \advance \…
Best regards: OK
___________________________________________________________________________________
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-01-03 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 5:41 Otared Kavian [this message]
2012-01-03 7:38 ` Wolfgang Schuster
2012-01-03 12:58 ` Otared Kavian
2012-01-03 13:05 ` Aditya Mahajan
2012-01-03 13:06 ` Wolfgang Schuster
2012-01-03 13:17 ` Otared Kavian
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=29F3E85B-66B3-49BD-9E79-C6717F454513@gmail.com \
--to=otared@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).