From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>,
Pablo Rodriguez <oinos@gmx.es>
Subject: Re: \jobname and \doifelse
Date: Sat, 5 Nov 2022 16:55:47 +0100 [thread overview]
Message-ID: <2eb6e285-c29d-d1e0-19f6-92bf8a7efce3@gmail.com> (raw)
In-Reply-To: <258d3649-658c-10b1-baa3-0985c900fafa@gmx.es>
Pablo Rodriguez via ntg-context schrieb am 05.11.2022 um 16:30:
> Dear list,
>
> using current latest (2022.10.22 11:23), I have the following sample:
>
> \starttext
> \doifelse{\jobname}{a}
> {yes}{no}
> \jobname
>
> \startluacode
> if tex.jobname == "a" then
> context("yes")
> else
> context("no")
> end
> \stopluacode
> \stoptext
>
> I get "no" as in TeX and "yes" with Lua, being "a.tex" the source file.
>
> The TeX conditional used to work before.
>
> Am I missing something or have I hit a bug?
Are you sure the check worked in the past?
The content of \jobname has catcode 12 while you "a" you check against
has catcode 11, and even when \jobname result in "a" they are different
because the catcodes differ.
You can see the same result in the example below where the second check
compares two a with different catcodes (11 and 12) while the first check
has the same catcode (11) for both a's.
\starttext
\edef\A{a}
\edef\B{a}
\ifx\A\B
yes
\else
no
\fi
\begingroup
\catcode`a=12
\gdef\B{a}
\endgroup
\ifx\A\B
yes
\else
no
\fi
\stoptext
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-11-05 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 15:30 Pablo Rodriguez via ntg-context
2022-11-05 15:55 ` Wolfgang Schuster via ntg-context [this message]
2022-11-06 13:11 ` Pablo Rodriguez via ntg-context
2022-11-06 10:21 ` Hans Hagen via ntg-context
2022-11-06 13:12 ` Pablo Rodriguez 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=2eb6e285-c29d-d1e0-19f6-92bf8a7efce3@gmail.com \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
--cc=wolfgang.schuster.lists@gmail.com \
/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).