From: "Wolfgang Werners-Lucchini" <wwl@musensturm.de>
To: ntg-context@ntg.nl
Subject: Re: first steps
Date: Tue, 08 Apr 2008 23:31:46 +0200 [thread overview]
Message-ID: <47FC0062.24710.33BE687@wwl.musensturm.de> (raw)
In-Reply-To: <mailman.1.1207648802.28836.ntg-context@ntg.nl>
On 8 Apr 2008 at 12:00, ntg-context-request@ntg.nl wrote:
> > I am using scite with the following command:
> > texmfstart texexec --autopdf --luatex tst3.tex
>
> I simply have no idea. I do not understand why windows
> would object to closing a file that doesn't exist (not even
> how it could be possible for an opened file to not exist).
>
> It could be a simple matter of a missing file that somehow
> luatex fails to check for during opening so it is not discovered
> until it attempts to close the file, but even if that is true,
> I have no idea how to debug anything on windows.
>
> It could also be a (more complicated) problem triggered by
> disk synchronisation issues in Windows itself. We have been
> bitten by those before (what is your windows flavour?)
Windows 2000
> In either case, someone else has to come up with tests and/or
> fix attempts. The only advice I can give is to reinstall
> context using the new minimals and see if that helps any.
>
> http://wiki.contextgarden.net/ConTeXt_Minimals
This is a fresh installation. I installed it using
'context-setup-mswin.zip'.
After some trials, I found that the example compiles ok without the
TWO \eogonek commands. There were TWO fclose attempts in the logs,
too.
Can this be a hint?
Wolfgang
___________________________________________________________________________________
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 parent reply other threads:[~2008-04-08 21:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1207648802.28836.ntg-context@ntg.nl>
2008-04-08 21:31 ` Wolfgang Werners-Lucchini [this message]
[not found] <mailman.1.1207821601.10731.ntg-context@ntg.nl>
2008-04-10 16:14 ` Wolfgang Werners-Lucchini
[not found] <mailman.4552.1207729500.4340.ntg-context@ntg.nl>
2008-04-09 10:55 ` Wolfgang Werners-Lucchini
2008-04-09 14:54 ` Taco Hoekwater
[not found] <mailman.4454.1207592564.4340.ntg-context@ntg.nl>
2008-04-07 21:34 ` Wolfgang Werners-Lucchini
2008-04-08 7:42 ` Taco Hoekwater
2008-04-07 14:41 Wolfgang Werners-Lucchini
2008-04-07 15:19 ` Taco Hoekwater
2008-04-08 21:51 ` Mojca Miklavec
2008-04-09 7:48 ` Taco Hoekwater
2008-04-09 9:47 ` Mojca Miklavec
2008-04-09 9:52 ` Mojca Miklavec
2008-04-09 10:17 ` Taco Hoekwater
2008-04-09 10:30 ` Mojca Miklavec
2008-04-09 15:51 ` Hans Hagen
2008-04-09 15:57 ` Taco Hoekwater
2008-04-09 16:34 ` Hans Hagen
2008-04-09 17:11 ` Taco Hoekwater
2008-04-09 17:59 ` Hans Hagen
2008-04-09 19:05 ` Hans van der Meer
2008-04-09 19:53 ` Taco Hoekwater
2008-04-09 23:15 ` Hans Hagen
2008-04-09 17:42 ` Hans Hagen
2008-04-09 20:00 ` Taco Hoekwater
2008-04-09 20:36 ` Mojca Miklavec
2008-04-09 23:08 ` 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=47FC0062.24710.33BE687@wwl.musensturm.de \
--to=wwl@musensturm.de \
--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).