ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Tan Hwee Huat" <mattanhh@nus.edu.sg>
Subject: Problem with \dosetupsystem
Date: Wed, 30 Jul 2003 09:38:55 +0800	[thread overview]
Message-ID: <1F95A56D79AE96438C11C3E37F20ECBE15545A@MBXSRV06.stf.nus.edu.sg> (raw)

Hi all, I am new to ConTeXt, and am learning to use it with the version in the  fpTeX 0.6 distribution.
On the office PC, I have no problem with using texexec for trying out various small context files.
But on the home PC, use of texexec on the file trymeta.tex with  the command-line
 
texexec trymeta
 
always leads to a halt in \dosetupsystem with the following error message:
 
....................................
system         : trymeta.top loaded
(./trymeta.top)
Runaway argument?
\c!gebied ={\setupsystem [inputfile=trymeta.tex] \protect
! File ended while scanning use of \dosetupsystem.
<inserted text>
                \par
<to be read again>
                   \relax
\dodoreadfile ...normalinput \readfilename \relax
                                                  \the \everyafterreadfile
<everyjob> ...file \openutilities \loadoptionfile
                                                  \checknotes \initializeMPg...
l.1
    \starttext
?
==================================================================================
 
But the strange thing is if I execute the command in with another drive as the current drive, and preceed the filename trymeta with the correct drive letter, it will work to completion. For example, if the tyrmeta.tex is on drive C, and I change drive to drive D (using the command d:), and type
 
texexec c:\trymeta
 
the command will complete with the production of the dvi file.
 
Any reason for this strange behaviour? Thank you in advance for any advice.
 
Hwee Huat

             reply	other threads:[~2003-07-30  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  1:38 Tan Hwee Huat [this message]
2003-07-30  9:05 ` Patrick Gundlach

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=1F95A56D79AE96438C11C3E37F20ECBE15545A@MBXSRV06.stf.nus.edu.sg \
    --to=mattanhh@nus.edu.sg \
    --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).