ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: metafun: problems, problems & problems again
Date: Tue, 21 Feb 2006 20:01:13 +0100	[thread overview]
Message-ID: <6faad9f00602211101g5ba3f6dbxb42abad582dc9e3a@mail.gmail.com> (raw)
In-Reply-To: <43F97F78.509@wxs.nl>

On 2/20/06, Hans Hagen wrote:
> Mojca Miklavec wrote:
> > But I still get no figures at all under MikTeX and "undefined" labels
> > with the standalone.
> >
> that normally means that no tex subruns take place (or wrong ones)
>
> (maybe the system command is not executed, in the log you can see what
> write 18 does)
>
> you can try (on a mp file):
>
> texexec --mptex somefile.mp
>
> and see what is reported

I traced the problem of getting annoying "\loadfontfilesoncetrue
undefined" messages down to the line 2936 in texexec.pl, sub RunMPX:
   if ( ( $Format eq '' ) || ( $Format =~ /^cont.*/io ) ) {
      RunConTeXtFile( $MpTmp, "tex" );
   } else {
      RunSomeTeXFile( $MpTmp, "tex" );
   }

The first subroutine (RunConTeXtFile) is executed (as it should be),
but it calls TeX instead of "ConTeXt" (format) and I have no idea how
to change this behaviour. That's why all ConTeXt commands are
undefined.

The same is true for tex.rb, line 1442:
   if context then
      ok = RunConTeXtFile(mptex)
   else
      ok = RunSomeTeXFile(mptex)
   end

It goes into the first part of the if sentence, but it nevertheless
runs (plain) tex. Except that in this time it was far from evident for
me where this RunConTeXtFile came from (I didn't see the definition
anywhere except if it calls Perl at that place).

On 2/20/06, Taco Hoekwater wrote:
> Mojca Miklavec wrote:
> > Is there any way to explore why the crash would happen? I get "An
> > unhandled win32 exception occured in pdfetex.exe [2384]", 3164, 812,
> > 1752, 2776, ...
>
> A (likely) candidate is an (software-ignored) attempt to write to
> a file that is still in use by another application. It is quite
> possible that this is the result of an I/O timing error that is in
> itself caused by a misconfigured win32 install (harddisks in ms-dos
> compatility mode, for example, or soundcard that share interrupts
> with the harddisk controller.

Might be. I also heard from some latex people that they had problems
with pdflatex on some disks. It happened to me on two different
computers on two different distros (MikTeX, standalone). Some crashing
went away when I removed \setupoutput[pdf] from cont-sys.tex (but I'm
stil confused since there are two cont-sys files, one .rme and one
.ori. Which one should be used? They are identical, but why would one
want to have the same file at two places?)

Mojca

  parent reply	other threads:[~2006-02-21 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 23:20 Mojca Miklavec
2006-02-20  8:36 ` Hans Hagen
2006-02-20 19:25   ` Mojca Miklavec
2006-02-20 20:05     ` Taco Hoekwater
2006-02-21 19:01   ` Mojca Miklavec [this message]
2006-02-21 21:47     ` Hans Hagen
2006-02-20 11:13 ` Taco Hoekwater

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=6faad9f00602211101g5ba3f6dbxb42abad582dc9e3a@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.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).