ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: The odd semantics of \begincsname
Date: Sat, 17 Aug 2019 19:19:48 +1200	[thread overview]
Message-ID: <3c6496fd-2dc7-4bd9-1c72-74eaa5b7ae02@gmail.com> (raw)

Dear list,

According to the LuaTeX documentation:

    “The \begincsname primitive is like \csname but doesn’t create a
    relaxed equivalent when there is no such name.”

I thought it would be possible to use this fact to skip the \relax-ed
definition when \def-ining a new control sequence, but the following MWE
fails with \inaccessible:

    \expandafter\gdef\csname yes\endcsname{}
    \expandafter\gdef\begincsname no\endcsname{}
    \bye

Is this a bug or is this behaviour intended?  Could this be fixed by
making manufacture_csname aware whether it is in a def_cmd context or
not?

Cheers, Henri

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

             reply	other threads:[~2019-08-17  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-17  7:19 Henri Menke [this message]
2019-08-17  8:48 ` Hans Hagen
2019-08-17  8:56   ` Henri Menke
2019-08-17 10:15     ` Hans Hagen

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=3c6496fd-2dc7-4bd9-1c72-74eaa5b7ae02@gmail.com \
    --to=henrimenke@gmail.com \
    --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).