From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setupbars
Date: Sun, 8 Jul 2012 21:40:06 +0000 [thread overview]
Message-ID: <AD6EFEBB-A73A-4522-B38C-0BD20D638915@uva.nl> (raw)
In-Reply-To: <8155A316-76DE-469A-92A9-AA427F7E1B22@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1961 bytes --]
Thansk,
I see. \setupbars doesn't give a hit on ConTeXt-wiki, so I couldn't find this.
Still I dare say, it is a pity that [rulethickness=] gets a different meaning here than elsewhere. I would like to ask to reconsider, because I strongly believe in consistency in the API (though I am ready to admit that it is not easy to maintain and confess guilty myself at more than one occasion). That is either change all rulethickness's everywhere to this scheme or otherwise. Or did this already happened and did I miss that? And of course, the easiest solution would be if the code itself could sort out the difference between having been given a fraction or a length.
Hans van der Meer
On 8 jul. 2012, at 22:44, Wolfgang Schuster wrote:
Am 08.07.2012 um 22:24 schrieb Meer, H. van der:
This gives an error:
\starttext
\setupbars[rulethickness=4pt]
\stoptext
! LuaTeX error <main ctx instance>:1: malformed number near '4pt'.
ConTeXt ver: 2012.07.04 23:48 MKIV fmt: 2012.7.6 int: english/english
Elsewhere this is ok, as for example in: \framed[rulethickness=4pt]{}
Strangely in node-rul.mkiv I see: \c!rulethickness=2.5
whereas in pack-rul.mkiv: \c!rulethickness=\linewidth
I am inclined to spot an error here, or at least an inconsistency in the API.
\setupbars[rulethickness=0.5]
\starttext
\setupbars[unit=ex]\underbar{ex}
\setupbars[unit=em]\underbar{em}
\stoptext
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl<mailto: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
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4601 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-07-08 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 20:24 setupbars Meer, H. van der
2012-07-08 20:44 ` setupbars Wolfgang Schuster
2012-07-08 21:40 ` Meer, H. van der [this message]
2012-07-09 7:09 ` setupbars Meer, H. van der
2012-07-09 7:26 ` setupbars Wolfgang Schuster
2012-07-09 7:38 ` setupbars Procházka Lukáš Ing. - Pontex s. r. o.
2012-07-09 15:35 ` setupbars Bill Meahan
2012-07-09 22:16 ` setupbars Hans Hagen
2012-07-10 13:25 ` setupbars Procházka Lukáš Ing. - Pontex s. r. o.
2012-07-10 14:31 ` setupbars Hans Hagen
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=AD6EFEBB-A73A-4522-B38C-0BD20D638915@uva.nl \
--to=h.vandermeer@uva.nl \
--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).