From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Rik Kabel via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: directsetup vs setups
Date: Mon, 15 Nov 2021 10:38:52 +0100 [thread overview]
Message-ID: <c3886125-3ca7-009e-d380-545c729c3dff@xs4all.nl> (raw)
In-Reply-To: <9314580b-537f-a406-0bab-4db53c71d8bf@rik.users.panix.com>
On 11/15/2021 6:24 AM, Rik Kabel via ntg-context wrote:
> Hello list,
>
> Can anyone provide a description of, or a point to a description of, the
> differences between setups= and directsetup= for including setups? I
> searched the list archive and the documents and found nothing. (That may
> indicate my level of search foo, but nonetheless I am in need of help
> with this.)
\setup : takes a list ({...} or [...])
\directsetup: supports gridsnapping, only one setup
\fastsetup : the fastest, only one setup
concerning performance, i wonder if you'll notice it
\starttext
\startsetups test
\stopsetups
\testfeatureonce{100000}{\setup {test}} \elapsedtime \par
\testfeatureonce{100000}{\setup [test]} \elapsedtime \par
\testfeatureonce{100000}{\directsetup{test}} \elapsedtime \par
\testfeatureonce{100000}{\fastsetup {test}} \elapsedtime \par
\stoptext
because often what's done in the setup is taking the time, just test
\startsetups test
{\bf}
\stopsetups
you can volunteer to wikify it
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-11-15 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 5:24 Rik Kabel via ntg-context
2021-11-15 8:21 ` Denis Maier via ntg-context
2021-11-15 9:38 ` Hans Hagen via ntg-context [this message]
2021-11-15 18:06 ` Rik Kabel via ntg-context
2021-11-15 18:54 ` Wolfgang Schuster via ntg-context
[not found] ` <c4306f2b-3555-cb6f-787b-fafb98fe2c79@rik.users.panix.com>
2021-11-15 22:48 ` Wolfgang Schuster via ntg-context
2021-11-15 21:33 ` Hans Hagen via ntg-context
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=c3886125-3ca7-009e-d380-545c729c3dff@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).