ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: \jobname and \doifelse
Date: Sun, 6 Nov 2022 11:21:54 +0100	[thread overview]
Message-ID: <35b152e9-44ed-cacc-8e81-811eb91b347f@xs4all.nl> (raw)
In-Reply-To: <258d3649-658c-10b1-baa3-0985c900fafa@gmx.es>

On 11/5/2022 4:30 PM, Pablo Rodriguez via ntg-context wrote:
> 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?
> 
> I’m on Linux64 (if this may be relevant).
More relevan tis that you'r on TeX where catcodes matter
(here letter vs other)

   \doifelse{\inputfilebarename}{oeps}
     {yes}{no}

   \doifelse{\detokenize\expandafter{\jobname}}{\detokenize{oeps}}
     {yes}{no}


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 / 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
___________________________________________________________________________________

  parent reply	other threads:[~2022-11-06 10:21 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
2022-11-06 13:11   ` Pablo Rodriguez via ntg-context
2022-11-06 10:21 ` Hans Hagen via ntg-context [this message]
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=35b152e9-44ed-cacc-8e81-811eb91b347f@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).