From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/568 Path: main.gmane.org!not-for-mail From: "Gilbert van den Dobbelsteen" Newsgroups: gmane.comp.tex.context Subject: Re: figuur masker is niet te vinden Date: Mon, 21 Jun 1999 17:58:20 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <001701bebbfe$e2cb1580$0c01a8c1@worf.login-bv.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035391420 25146 80.91.224.250 (23 Oct 2002 16:43:40 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:43:40 +0000 (UTC) Cc: Original-To: "Wybo Dekker" Xref: main.gmane.org gmane.comp.tex.context:568 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:568 >> texexec --pdf yourfile >> >> or include the line: >> >> \setupoutput[pdftex] >> > >Fine, both worked, thank you. >But why did'nt I have to do that during the course? Probably the first line of you .tex document contained something like this: % interface=nl output=pdf texexec scans your .tex file, looking for clues about what kind of file it is (it auto-magically sees that the file uses English context if it contains \startext instead of \starttekst). I noticed however that the auto recognition doesn't always work, but I should first upgrade to the latest texexec before sending complaints. Not all options can be given in the first line. Lookup the texexec script and check for yourself what it is doing. Note: The problem with my texexec is that it can only do tex-files that are there, meaning: I cannot compile a tex file which is not in the current directory, but in $TEXINPUTS. I don't see this as a problem, I usually create a symlink or so. Gilbert.