From: wwl@musensturm.de
Subject: Re: some questions
Date: Tue, 15 Aug 2006 11:06:22 +0200 [thread overview]
Message-ID: <44E1AAAE.8127.37C62AA@wwl.musensturm.de> (raw)
In-Reply-To: <mailman.1.1155549602.30697.ntg-context@ntg.nl>
> >> Should'nt \arg{bla} be \type{{bla}}?
>
> I can't give you a satisfying answer for this, but
>
> Should'nt \expandafter\type\expandafter{\arg{bla}} be
> \type{{bla}}?
>
> gives
>
> Should?nt \dohandlemathtokenarg{bla} be {bla}?
>
> (so I guess the answer is probably no)
\arg is one of the verbatim macros, like \type, \typ, \tex
and is describte in 'cont-enp.pdf' on page 101.
The description looks a bit incomplete: (the command encloses the
text with .)
(Can someone, with the right to do that, add this to the list of
typos, please?)
The definition of \arg is in 'core-ver.tex' and copying this
in a separate file works as expected:
\starttext
\unprotect
\def\setgroupedtype
{\let\currenttypingclass\??ty
\initializetype
\catcode`\{=\@@begingroup
\catcode`\}=\@@endgroup}
\unexpanded\def\arg{%
\groupedcommand{\setgroupedtype\leftargument}{\rightargument}}
\protect
\arg{bla}
\stoptext
So there must something be damaged.
Wolfgang
next prev parent reply other threads:[~2006-08-15 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1155549602.30697.ntg-context@ntg.nl>
2006-08-14 17:30 ` Snapping sectionhead wwl
2006-08-14 17:58 ` taco hoekwater
2006-08-14 18:39 ` taco hoekwater
2006-08-15 9:06 ` wwl [this message]
2006-08-15 9:08 ` some questions Taco Hoekwater
2013-01-25 13:49 Some questions Alain Delmotte
2013-01-25 14:47 ` Marco Patzer
2013-01-25 15:00 ` Alan BRASLAU
2013-01-25 19:17 ` Alain Delmotte
2013-01-26 7:18 ` Alan BRASLAU
[not found] <mailman.1.1155463203.3247.ntg-context@ntg.nl>
2006-08-13 21:24 ` some questions wwl
2006-08-13 23:07 ` Peter Rolf
-- strict thread matches above, loose matches on Subject: below --
2006-08-12 21:03 wwl
2006-08-12 22:57 ` Peter Rolf
2006-08-13 13:37 ` Peter Rolf
2000-06-05 7:17 Some questions David Arnold
2000-06-05 10:05 ` 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=44E1AAAE.8127.37C62AA@wwl.musensturm.de \
--to=wwl@musensturm.de \
--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).