From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: How to let a macro check the previous value of #1 the last time the same macro was called?
Date: Tue, 11 Jan 2022 09:20:54 +0100 [thread overview]
Message-ID: <bd5dfd73-21f0-9731-8b8f-b1c3fe11d7bc@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2201102320030.1381716@nqv-guvaxcnq>
On 1/11/2022 5:22 AM, Aditya Mahajan via ntg-context wrote:
> On Tue, 11 Jan 2022, Henning Hraban Ramm via ntg-context wrote:
>
>> Am 10.01.22 um 20:21 schrieb Wolfgang Schuster:
>>> Henning Hraban Ramm via ntg-context schrieb am 10.01.2022 um 09:52:
>>>> Would it make more sense, or would it be “cleaner” to use a variable?
>>>
>>> You can get rid of the temp variable before the command definition but
>>> now you have to access it with a different method in \mymacro, below is
>>> one way (LMTX only) but \setvariable and \getvariable work as well.
>>>
>>> \define[1]\mymacro
>>> {\iftok{#1}{\getvalue{previousmymacro}}%
>>> same as last time
>>> \else
>>> it is different from last time
>>> \fi
>>> \setvalue{previousmymacro}{#1}}
>>
>> That was the approach that I meant. Thank you.
>>
>> But would you consider one way to be better?
>
> Just for fun: lua code
>
> \startluacode
> local previous = nil
>
> interfaces.implement {
> name = "mymacro",
> public = true,
> arguments = "string",
> actions = function (current)
> if current == previous then
> context("same as last time")
> else
> context("Different!")
> end
> previous = current
> end,
> }
>
> \stopluacode
>
> \starttext
>
> \startlines
> cat: \mymacro{cat}
> cat: \mymacro{cat}
> mouse: \mymacro{mouse}
> mouse: \mymacro{mouse}
> cat: \mymacro{cat}
> \stoplines
>
> \stoptext
keep in mind that what you do is global (probably what one wants here):
\startlines
cat: \mymacro{cat}
cat: \mymacro{cat}
{mouse: \mymacro{mouse}}
{mouse: \mymacro{mouse}}
cat: \mymacro{cat}
\stoplines
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-01-11 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1050338993.1893942.1641737797345.ref@mail.yahoo.com>
2022-01-09 14:16 ` Joel via ntg-context
2022-01-09 15:03 ` Wolfgang Schuster via ntg-context
2022-01-10 8:52 ` Henning Hraban Ramm via ntg-context
2022-01-10 19:21 ` Wolfgang Schuster via ntg-context
2022-01-10 23:15 ` Henning Hraban Ramm via ntg-context
2022-01-11 4:22 ` Aditya Mahajan via ntg-context
2022-01-11 8:20 ` Hans Hagen via ntg-context [this message]
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=bd5dfd73-21f0-9731-8b8f-b1c3fe11d7bc@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).