From: Aditya Mahajan <adityam@umich.edu>
Subject: Bug in ctxtools --documentation
Date: Mon, 31 Jul 2006 03:17:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0607310300410.1696@nqvgln> (raw)
Hi Hans,
ctxtools.rb says that %D is the documetation marker. However, while
matching it uses
when /^[%\#]D/io then
Doesn't /i stand for ignorecase, which means that %d is also matched?
Is this a bug or a feature?
Try generating documentation of core-fnt.tex for an interesting
manifestation of this. You have
%def\uppercased#1{{\forceunexpanded\xdef\@@globalcrap{\uppercase{#1}}}\@@globalcrap}
%def\lowercased#1{{\forceunexpanded\xdef\@@globalcrap{\lowercase{#1}}}\@@globalcrap}
%d gets matched, %de gets deleted and the following is written in
core-fnt.ted
\startdocumentation
f\uppercased#1{{\forceunexpanded\xdef\@@globalcrap{\uppercase{#1}}}\@@globalcrap}
f\lowercased#1{{\forceunexpanded\xdef\@@globalcrap{\lowercase{#1}}}\@@globalcrap}
\stopdocumentation
when context processes this it complains
! Illegal parameter number in definition of \@@expanded.
<to be read again>
}
\uppercased ... \xdef \@@expanded {\uppercase {#1}
}}\@@expanded
l.251 f\uppercased#
1{{\forceunexpanded\xdef\@@globalcrap{\uppercase{#1}}}\@@...
?
! You can't use `macro parameter character #' in horizontal mode.
<recently read> ##
\@@expanded ->\uppercase {##}
l.251 f\uppercased#
1{{\forceunexpanded\xdef\@@globalcrap{\uppercase{#1}}}\@@...
Aditya
next reply other threads:[~2006-07-31 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 7:17 Aditya Mahajan [this message]
2006-07-31 7:46 ` 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=Pine.WNT.4.63.0607310300410.1696@nqvgln \
--to=adityam@umich.edu \
--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).