From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: defs, variables and dimensions (was: passing variables/data between context and lua)
Date: Sat, 28 Sep 2019 08:53:09 +0200 [thread overview]
Message-ID: <7B1B8E3F-AB6E-4CE1-8FF2-0FBFD806A653@fiee.net> (raw)
In-Reply-To: <4c95d00f-b9fc-1595-eb62-ebe75e55439f@gmail.com>
> Am 2019-09-27 um 14:58 schrieb Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
>
>> \define\question{44}
> \defineexpandable\question{44}
Would it make sense to use a counter or some other TeX construct?
Is it better to use \setvariable(s) for simple values than any \def?
Should I use a \newdimen for every custom measure that I want to use with \dimexpr, e.g.
\def\MyWidth{10mm}
or better
\newdimen\MyWidth
\MyWidth=10mm
?
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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:[~2019-09-28 6:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 4:59 passing variables/data between context and lua Martin Althoff
2019-09-27 8:41 ` mf
2019-09-27 12:58 ` Wolfgang Schuster
2019-09-28 6:53 ` Henning Hraban Ramm [this message]
2019-09-28 17:51 ` defs, variables and dimensions Wolfgang Schuster
2019-09-30 2:51 ` defs, variables and dimensions (was: passing variables/data between context and lua) Martin Althoff
2019-09-29 11:51 ` passing variables/data between context and lua Martin Althoff
2019-10-06 5:11 ` Rudolf Bahr
2019-10-06 20:44 ` Wolfgang Schuster
2019-10-08 7:21 ` Rudolf Bahr
2019-10-08 12:55 ` Aditya Mahajan
2019-10-08 16:22 ` Rudolf Bahr
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=7B1B8E3F-AB6E-4CE1-8FF2-0FBFD806A653@fiee.net \
--to=texml@fiee.net \
--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).