mojca.miklavec.lists at gmail.com
Thu Aug 3 00:14:20 CEST 2006
On 8/2/06, Taco Hoekwater wrote:
> David Arnold wrote:
> > Taco,
> > Is this also true about:
> > http://www.pragma-ade.com/context/install/mswincontext.zip
> Same batch file, so yes.
> It would be possible to convert the batch file into a perl or ruby
> scripts plus a one-line batch that starts the interpreter + script,
> but not being on windows except in very abnormal cases
... and even in that abnormal cases Taco somehow manages to get
Windows 98 installed instead of XP ;)
> I am personally not very likely to do that.
Some time ago I was experimenting with ruby a bit: I tried to set some
environmental variables, so that MikTeX could gain some functionality
(MikTeX doesn't use that batch file and consequently "texexec --make
--all", "ctxtools --update", ... don't work because scripts don't know
where to place the files).
But the problem was that changes to environmental variables were seen
only locally, so it didn't make any sense at all. Do you indeed have
any ideas how to set environmental variables inside of a ruby script,
so that they would be seen from outside? Because that would solve a
whole lot of problems in MikTeX.
Saying that, something else came to my mind. Has anyone tried running
ConTeXt on MikTeX on Windows 98? That one doesn't need any batch
files. I don't know what will happen to files longer than 8
characters, but the rest might work.
More information about the ntg-context