zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: "Zefram" <zefram@tao.co.uk>,
	jherbert@wizvax.net, zsh-workers@math.gatech.edu
Subject: Re: zsh_on_dos
Date: Thu, 10 Sep 1998 08:05:34 -0700	[thread overview]
Message-ID: <980910080534.ZM3081@candle.brasslantern.com> (raw)
In-Reply-To: <199809101001.LAA09765@diamond.tao.co.uk>

On Sep 10, 11:01am, Zefram wrote:
} Subject: Re: zsh_on_dos
}
} What this doesn't tell you is that you'll also need a port of ls, and
} all the other Unix utilities.

Check out http://www.cygnus.com/misc/gnu-win32/.  I took a stab at building
3.0.5 using the Cygwin32 compatibility library, and had no serious problems.
The only difficulty is that gnu-win32 does NOT come with curses, termcap or
terminfo libraries, so you have to obtain and build one on your own before
compiling zsh.  It does come with an /etc/termcap, but the entry in there
for the console apparently has some problems.

I vaguely recall that it used to be possible to build zsh without reference
to termcap by leaving out zle.  That doesn't seem to be possible anymore;
termcap references have crept into several parts of the code.

Anyway, besides the above, there's also a collection of unix utilities for
NT called the NT Resource Kit, which I believe (not certain) you get from
Microsoft; and at least one other free or shareware set of tools that I've
seen, but I've forgotten the reference.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1998-09-10 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-10  2:51 zsh_on_dos jherbert
1998-09-10 10:01 ` zsh_on_dos Zefram
1998-09-10 15:05   ` Bart Schaefer [this message]
1998-09-10 18:26 zsh_on_dos Eric De Mund

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=980910080534.ZM3081@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=jherbert@wizvax.net \
    --cc=zefram@tao.co.uk \
    --cc=zsh-workers@math.gatech.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).