From: Hans van der Meer <hansm@science.uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: getbuffer now fails
Date: Sun, 23 Mar 2008 12:36:47 +0100 [thread overview]
Message-ID: <9AA45BC6-36B5-403C-867C-28769E95214D@science.uva.nl> (raw)
I had this code working (it was in an article I submitted for NTG-MAPS
a while ago, july 2007). Now this same code gives an error on getbuffer.
What happened to getbuffer? Is it possible a \fi has disappeared in
the getbuffer code between now and last july? Is there a quick patch
because now I get stuck on work that has to be finished.
The error message from TeX:
! Incomplete \ifx; all text was ignored after line 6.
<inserted text>
\fi
<to be read again>
\relax
\dodoreadfile ...d \relax \fi \dodoreadfileindeed
\relax \the
\everyafterrea...
\mkdobuffer #1->\beginrestorecatcodes #1
\endrestorecatcodes
\dodobuffer ...dcsname \else #2\fi }\mkdobuffer #1
\popmacro
\currentbuffer
\dodogetbuffer ...}\dobuffer {16}{#2}\mkgetbuffer
\getvalue {\??bu
#1\c!after }
...
l.111 \question[number=1][buffer]{\getbuffer}
The relevant part of the code, not working is the call to \@exmbuffer:
...
\doifelse{#2}{\v!buffer}%
{\def\filename{buffer}\def\thefile{#3}\let\@@exminput\@exmbuffer}%
{.....}%
\@@exminput\thefile
\endgroup}
% reading the file better outside the doif
\def\@exminput#1{\input#1\relax}
\def\@exmbuffer#1{#1}
Help is appreciated.
Hans van der Meer
___________________________________________________________________________________
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2008-03-23 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 11:36 Hans van der Meer [this message]
2008-03-23 14:41 ` Wolfgang Schuster
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=9AA45BC6-36B5-403C-867C-28769E95214D@science.uva.nl \
--to=hansm@science.uva.nl \
--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).