From: John Culleton <john@wexfordpress.com>
Cc: ntg-context@ntg.nl
Subject: Re: A fresh approach to learning Context.
Date: Sun, 3 Mar 2002 13:44:58 -0500 [thread overview]
Message-ID: <02030313445801.13938@publish> (raw)
In-Reply-To: <5.1.0.14.1.20020302140029.02c21580@server-1>
> >with pdftex causes an error message in Context thus:
> >
> >! Use of \def doesn't match its definition.
> >l.79 \def\hpenalty
> > {\ifvmode\leavevmode\fi \penalty}%
> >
>> it seems that somehow the primitiev \def has been defined,
>
> add the line \show\def before line 79 and see what happened, move
> this line up till the primitive def shows up.
>
> Hans
Following this advice I found a strange piece of code in
eplain that causes the problem. Then I went to xeplain (eplain
annotated) and found an explanation of the code.
Here is the xeplain.tex code and explanation:
------------------------------
%
% In order to do anything with ^^L inside a macro, it must
% be made non-\outer.
%
\def^^L{\par}%
---------------------
If I comment out this line then Context offers no error message
as indicated above. I have no idea what the code does. It is the
first instance I have seen of a \def that was not immediately
followed with a command name beginning with a backslash.
I will teke this issue to the eplain mailing list.
--
John Culleton, john@wexfordpress.com
Able Indexers and Typesetters
http://wexfordpress.com
<------------------------------------>
next prev parent reply other threads:[~2002-03-03 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 23:20 John Culleton
2002-03-02 13:01 ` Hans Hagen
2002-03-03 18:44 ` John Culleton [this message]
2002-03-03 21:27 ` 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=02030313445801.13938@publish \
--to=john@wexfordpress.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).