From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: another surprising change (line break in TOC)
Date: Wed, 18 Jan 2012 09:37:23 +0100 [thread overview]
Message-ID: <4F1684C3.1040604@wxs.nl> (raw)
In-Reply-To: <CAG5iGsBw5V8eB7MW+LATYYzSKeK-+NBLdNydkkMnEd38JdCWmQ@mail.gmail.com>
On 18-1-2012 08:30, luigi scarso wrote:
> On Wed, Jan 18, 2012 at 7:25 AM, Steffen Wolfrum<context@st.estfiles.de>wrote:
>
>>
>> Am 17.01.2012 um 23:41 schrieb Wolfgang Schuster:
>>
>
>
>>> You should try to make your code more readable.
>>>
>>> \definelistplacement[MyListItemIT][none]#1#2#3%
>>> {\maxaligned\bgroup
>>> \rlap{\it#1}%
>>>
>> \framed[frame=off,align=middle,location=bottom,width=broad,foregroundstyle=\TOCstyleBF]{#2}%
>>> \llap{\tf#3}%
>>> \egroup}
>>
>>
>> I did not know "\maxaligned"
>>
>> even me --- it's normal, it's hard to be in sync with all the changes of
> the source. I suspect that it's an internal macro, can even change.
> Wolfgang often uses internal macro, gaining speed but loosing compatibility.
> As general rule (another...) in my stylesheets I try to use TeX macros and
> ConTeXt switches (i.e. key=val) especially if they are related to long term
> projects.
Actually, Wolfgang seldom uses internal macros. Macros like \maxaligned
are helpers that are used to build regular commands, so they're part of
the infrastructure and Wolfgang knows the context internals amazingly
well. There are some obscure helpers that might dissappear but most are
there for a reason and will stay. So, we have:
commands: offcial interface
helpers : more low level, no key/values etc
hidden : not meant to be used unless on your own risk
Btw, \rlap and \llap are quite standard in a tex system.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-01-18 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 14:21 Steffen Wolfrum
2012-01-16 14:29 ` Wolfgang Schuster
2012-01-16 14:39 ` Steffen Wolfrum
2012-01-16 16:18 ` Hans Hagen
2012-01-17 10:37 ` Steffen Wolfrum
2012-01-17 11:19 ` luigi scarso
2012-01-17 12:14 ` Steffen Wolfrum
2012-01-17 22:41 ` Wolfgang Schuster
2012-01-18 6:25 ` Steffen Wolfrum
2012-01-18 7:30 ` luigi scarso
2012-01-18 7:39 ` luigi scarso
2012-01-18 7:45 ` Wolfgang Schuster
2012-01-18 8:37 ` Hans Hagen [this message]
2012-01-18 8:56 ` luigi scarso
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=4F1684C3.1040604@wxs.nl \
--to=pragma@wxs.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).