ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: New Installation under miktex, not working
Date: Tue, 17 Jan 2006 10:38:37 +0100	[thread overview]
Message-ID: <43CCBB1D.5000004@wxs.nl> (raw)
In-Reply-To: <Pine.WNT.4.63.0601170115420.660@nqvgln>

Aditya Mahajan wrote:

> I had a similar problem. I needed cygwin ruby because there are 
> certain ruby packages (e.g. narray) that I could get to work with 
> cygwin ruby without any hassle but do not work with the ruby one click 
> installer. But cygwin ruby and context do not go together. I was 
> actually following your thread on comp.lang.ruby hoping that someone 
> will come up with a solution, but no suggestion worked. What I finally 
> did was, download and install the one click installer, but removed it 
> from the PATH. So when I am working on other projects, I get the 
> cygwin ruby which works fine. I added a line to setuptex.bat that adds 
> the one-click windows ruby to the front of the path. So when a context 
> program asks for a ruby, it gets the windows version and everything 
> works fine. The only drawback is that I can not use rxvt+bash, and 
> have to use cmd.exe


why the one-click installer, just take the 2-4 meg version compiled with 
the native ms compiler; that's the one i use and it works perfectly (for 
years now)

http://ftp.ruby-lang.org/pub/ruby/binaries/mswin32/

Hans

  reply	other threads:[~2006-01-17  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 19:36 Todd DeVries
2006-01-15 21:12 ` Taco Hoekwater
2006-01-15 23:25   ` Christopher G D Tipper
2006-01-16  8:10 ` Mojca Miklavec
2006-01-16 15:35   ` Aditya Mahajan
2006-01-16 16:02     ` Mojca Miklavec
2006-01-17  6:23       ` Aditya Mahajan
2006-01-17  9:38         ` Hans Hagen [this message]
2006-01-16 17:15     ` Todd DeVries
2006-01-16 18:34     ` Ralph Roberts

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=43CCBB1D.5000004@wxs.nl \
    --to=pragma@wxs.nl \
    --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).