From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: ConTeXt on MikTeX broken
Date: Tue, 6 May 2008 16:57:01 +0200 [thread overview]
Message-ID: <6faad9f00805060757h1eb05487j2436bc7d6481bf54@mail.gmail.com> (raw)
In-Reply-To: <22af238a0805060729qd09b71et8ad47d75537d3144@mail.gmail.com>
On Tue, May 6, 2008 at 4:29 PM, George N. White III wrote:
> On Sat, May 3, 2008 at 7:00 AM, Mojca Miklavec
> <mojca.miklavec.lists@gmail.com> wrote:
>
> > some time ago some MikTeX users have complained that ConTeXt doesn't
> > work on MikTeX. It seems to be a problem with MikTeX itself since this
> > workaround seems to solve the problem, at least temporary:
> > ruby "C:\Program Files\MiKTeX
> > 2.7\scripts\context\ruby\texmfstart.rb" texexec
>
> I'm not so quick to blame MiKTeX -- I suspect texmfstart.rb would need
> to provide some path searching tailored to MiKTeX. It seems to rely
> on $0 with a tetex/texlive directory structure where SELFAUTOPARENT
> can be used.
Christian has indeed replied that he uses the binary version of
texmfstart from CTAN (which is a bit older that the one on PRAGMA).
But I still don't understand what can go wrong "in the middle of
nothing", without any major changes. So there is either a problem in
MikTeX or in ConTeXt.
> The only criticism of MiKTeX is that it is silly to distribute
> a broken package, but then it is up to ConTeXt users to report breakage
> and, ideally, supply fixes.
I completely agree. Except that I have no MikTeX any more. And I don't
have the slightest idea what could have caused the problem. I don't
see any serious changes in the texmfstart code that could break the
3-week-old version, while it has worked OK before.
Mea culpa. I should have forced Hans to fix it during BachoTeX ... :)
I will try to misuse some windows computer next week to see if I can
find any bugs (but it's difficult to test since one cannot simply
modify the ruby script as on other platforms).
> > (But apparently there are not many MikTeX users on the list anyway.
> > Else more would have complained.)
>
> Don't complain, just switch to a platform/distro where ConTeXt works
> and use mpm (since few others provide updates with the speed and
> convenience of MiKTeX).
>
> I think MiKTeX should remain focusing on the packages and binaries,
> and rely on upstream to fix broken packages.
I agree. But I have thought that some change in MikTeX might have
occurred in the meantime.
Mojca
___________________________________________________________________________________
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 prev parent reply other threads:[~2008-05-06 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 10:00 Mojca Miklavec
2008-05-06 14:29 ` George N. White III
2008-05-06 14:57 ` Mojca Miklavec [this message]
2008-05-06 16:39 ` George N. White III
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=6faad9f00805060757h1eb05487j2436bc7d6481bf54@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).