From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE,URIBL_SBL_A
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 15659 invoked from network); 12 Jun 2023 10:33:26 -0000
Received: from zapf.ntg.nl (5.39.185.232)
  by inbox.vuxu.org with ESMTPUTF8; 12 Jun 2023 10:33:26 -0000
Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id C92F37176;
	Mon, 12 Jun 2023 12:32:54 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7zhvvc4xNH9E; Mon, 12 Jun 2023 12:32:52 +0200 (CEST)
Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 6C5E97149;
	Mon, 12 Jun 2023 12:32:52 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id BC9A67149
 for <ntg-context@ntg.nl>; Mon, 12 Jun 2023 12:32:44 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id xt2GUVIjNGUK for <ntg-context@ntg.nl>;
 Mon, 12 Jun 2023 12:32:43 +0200 (CEST)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=212.54.42.168;
 helo=smtpq5.tb.mail.iss.as9143.net; envelope-from=havdmeer@ziggo.nl;
 receiver=<UNKNOWN> 
Received: from smtpq5.tb.mail.iss.as9143.net (smtpq5.tb.mail.iss.as9143.net
 [212.54.42.168])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 36FD1BC4
 for <ntg-context@ntg.nl>; Mon, 12 Jun 2023 12:32:42 +0200 (CEST)
Received: from [212.54.42.105] (helo=smtp1.tb.mail.iss.as9143.net)
 by smtpq5.tb.mail.iss.as9143.net with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1)
 (envelope-from <havdmeer@ziggo.nl>) id 1q8eqn-0006Rg-Ex
 for ntg-context@ntg.nl; Mon, 12 Jun 2023 12:32:41 +0200
Received: from smtpclient.apple ([84.104.102.59])
 by smtp1.tb.mail.iss.as9143.net with ESMTPA
 id 8eqnqUf6ceuBG8eqnqltZ8; Mon, 12 Jun 2023 12:32:41 +0200
X-Env-Mailfrom: havdmeer@ziggo.nl
X-Env-Rcptto: ntg-context@ntg.nl
X-SourceIP: 84.104.102.59
X-CNFS-Analysis: v=2.4 cv=UL8bXgTy c=1 sm=1 tr=0 ts=6486f449 cx=a_exe
 a=r8aFSP8g8qyxuwAfcqn69g==:117 a=r8aFSP8g8qyxuwAfcqn69g==:17 a=MiNTnEJAAAAA:8
 a=OfmJFCjNzLKFInllJw8A:9 a=QEXdDO2ut3YA:10 a=FgjXctDTJX5xX-80nvcA:9
 a=AwG8-HLNVCdcHzHD:21 a=_W_S_7VecoQA:10 a=LmrbSfiT3hecnSZifb5M:22
X-Authenticated-Sender: havdmeer@ziggo.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ziggo.nl;
 s=202002corplgsmtpnl; t=1686565961;
 bh=qTdFppQMdSnRHHBvHZMnOXeNOeRB5O49776g7HbuUDo=;
 h=From:Subject:Date:References:To:In-Reply-To;
 b=XyrAAtpasO7xJGVQAxOaoUQrJ4kR9JGOSo8ptmqocZBvODn3dYYU4+rnvQDmO0ELd
 8mQaaYxG0O9WneQKsjufE3o9xKmJqkDiIbCM2ZGthAe3oP5FlkDVvCBs1sk2D7fG2/
 N6+K3Vx577uHZC2JjXcYlZOKw5nNLJ7/x0RbQ88ijc5ey4xvmSbJSW9KaL3bskYRYn
 UzrGaB/PQZ4Au8XwrrJZU6BqSp7Rzq7Mb+nNB8yUbQ4+kVBHjao3NIa5FeTS9urDl1
 HCvedWNAxi9Xr9p+p2ZdBrbPLrNSPrXhj2zAUgGCt+wDtLhTRsJFUP8EbPmXCDR+a7
 iGZAbZd0PrWNw==
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Date: Mon, 12 Jun 2023 12:32:31 +0200
References: <80A4DB81-41CB-4D3D-9A53-09A4DED5E665@ziggo.nl>
 <09bf23d1-0e29-005b-ad2b-75bc836d299a@freedom.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
In-Reply-To: <09bf23d1-0e29-005b-ad2b-75bc836d299a@freedom.nl>
Message-Id: <52D03A0F-C7EE-4AD3-8372-646CEDAD8AEE@ziggo.nl>
X-Mailer: Apple Mail (2.3731.600.7)
X-CMAE-Envelope: MS4xfLFV7UJBmsrYsjTbZikpcf3axP3+gNVzFPeJSMifmHGpbH/NVBXK+5uTsjLrc6CpCNhmLhr0mQwIbpqis/bHgrqIqD00r7adSE/1uox9olB26pE+KuJ3
 KGP0EW7PWRY5pUOYq8l6rylUNxICIQzphm0p7r8TCuIjKiULcaC1YJb3J6ElrlfTsRqBk2Bdj7hCyQ==
Subject: Re: [NTG-context] letfrozen?
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.38
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
From: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans van der Meer <havdmeer@ziggo.nl>
Content-Type: multipart/mixed; boundary="===============2124330294581363688=="
Errors-To: ntg-context-bounces@ntg.nl
Sender: "ntg-context" <ntg-context-bounces@ntg.nl>


--===============2124330294581363688==
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_E8C88A42-ED65-4F13-9647-8537BF207D1C"


--Apple-Mail=_E8C88A42-ED65-4F13-9647-8537BF207D1C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 12 Jun 2023, at 11:12, Hans Hagen via ntg-context =
<ntg-context@ntg.nl> wrote:
>=20
> On 6/12/2023 10:57 AM, Hans van der Meer via ntg-context wrote:
>> The manual LMTX-primitives on page 21 tells me:
>> 	You can explicitly freeze an unfrozen macro.
>> 	...
>> 	A redefinition will now give: You can't redefine a frozen macro.
>> But is this true? The following code seems to contradict this:
>> \def\HOME{myhome}
>> \writestatus{1}{\meaning\HOME}
>> \letfrozen\HOME
>> \writestatus{2}{\meaning\HOME}
>> \def\HOME{other home}
>> \writestatus{3}{\meaning\HOME}
>> =EF=BF=BC
>> Is this mechanism broken? It looks so useful to prevent accidental =
redefinition!
>=20
> here i run with
>=20
> \enabledirectives[overloadmode=3Derror]
>=20
> (you can do that in cont-sys.mkxl)
>=20
> \enabledirectives[overloadmode=3Dwarning]
> Hans
>=20

Pity. Now I get on loading the tex file:
"csname overload > fatal error, protection level 4, control sequence =
'nbsp', properties 'immutable', file 't-hvdm-text.tex', line 63

while I had hoped that frozen would give me something like:
illegal attempt to redefine \HOME

Byproduct (not unwanted) the above illegal redefinition to be solved :-)

May I ask why obviously the frozen-mechanism seems (yet?) unimplemented?

dr. Hans van der Meer


--Apple-Mail=_E8C88A42-ED65-4F13-9647-8537BF207D1C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: =
after-white-space;"><div><blockquote type=3D"cite"><div>On 12 Jun 2023, =
at 11:12, Hans Hagen via ntg-context &lt;ntg-context@ntg.nl&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div><div>On =
6/12/2023 10:57 AM, Hans van der Meer via ntg-context =
wrote:<br><blockquote type=3D"cite">The manual LMTX-primitives on page =
21 tells me:<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>You can explicitly freeze an unfrozen macro.<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>...<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>A redefinition will now give: You can't redefine a frozen =
macro.<br>But is this true? The following code seems to contradict =
this:<br>\def\HOME{myhome}<br>\writestatus{1}{\meaning\HOME}<br>\letfrozen=
\HOME<br>\writestatus{2}{\meaning\HOME}<br>\def\HOME{other =
home}<br>\writestatus{3}{\meaning\HOME}<br>=EF=BF=BC<br>Is this =
mechanism broken? It looks so useful to prevent accidental =
redefinition!<br></blockquote><br>here i run =
with<br><br>\enabledirectives[overloadmode=3Derror]<br><br>(you can do =
that in =
cont-sys.mkxl)<br><br>\enabledirectives[overloadmode=3Dwarning]<br> =
Hans<br><br></div></div></blockquote><br></div>Pity. Now I get on =
loading the tex file:<div><div>"csname overload &gt; fatal error, =
protection level 4, control sequence 'nbsp', properties 'immutable', =
file 't-hvdm-text.tex', line 63</div><div><br><div>while I had hoped =
that frozen would give me something like:</div></div></div><div>illegal =
attempt to redefine \HOME</div><div><br></div><div>Byproduct (not =
unwanted) the above illegal redefinition to be solved =
:-)</div><div><br></div><div>May I ask why obviously the =
frozen-mechanism seems (yet?) =
unimplemented?</div><div><br></div><div><div>dr. Hans van der =
Meer<br></div><div><br></div><div><blockquote =
type=3D"cite"></blockquote></div></div></body></html>=

--Apple-Mail=_E8C88A42-ED65-4F13-9647-8537BF207D1C--

--===============2124330294581363688==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2124330294581363688==--