Re: KISS'ed shell

>>> http://win-bash.sourceforge.net/
>> Or MSYS, from https://sourceforge.net/projects/mingw
>
> Personally I like 4NT, at http://www.jpsoft.com/4ntdes.htm
> but then again I've been using it since NT 3.51

I used to use 4DOS, from the same stable, until I discovered DJGPP.
No contest really; the shareware price JP Software ask for 4DOS/4NT
simply cannot be justified, when you compare features with the full
Unix shell--GNU bash--provided for free, (as in beer), with DJGPP.

Now, on my Woe32 box, I use MSYS:

  $ bash --version
  GNU bash, version 3.1.0(3)-release (i686-pc-msys)
  Copyright (C) 2005 Free Software Foundation, Inc.

and, since I liked the way 4DOS command history worked, I customise
the readline key bindings for this bash shell, so it behaves just the
same way, (and then some, because it also keeps the standard readline
incremental history search).

> I just wrote a batch file that did this:
>   copy *.pst "ftp://myoutsource.provider.org/tobeuploaded/"

And I'll bet you used JP's extended batch command language, so you
cannot use it on any box which lacks 4NT; not a big deal maybe, but
it does have a portability impact.

> but I bet you were looking for a 'Unix' like shell.

I think that's what the OP wanted, and it's what the first two links
will give him.  Neither is perfect, but IMO either outshines 4NT.

BTW, I was unaware of win-bash, until Mathias mentioned it.  I just had
a very quick look, and have some grave reservations:

  Microsoft Windows 2000 [Version 5.00.2195]
  (C) Copyright 1985-2000 Microsoft Corp.

  D:\opt\packages> win-bash -i --login
  win-bash: --: bad option

Huh?  If this is supposed to be GNU bash, why does it not respect this
standard invocation syntax for a login shell?  Never mind...

  D:\opt\packages> win-bash -i
  bash$

at least it will run as an interactive shell, albeit without login
features,  but...

  bash$ ./win-bash --version
  .\win-bash.exe: --: bad option

this is bad; what version of bash is this then?  Where is the standard,
(and required), GNU copyright notification?

  bash$ echo $BASH_VERSION
  win-bash_0.6.1(0)

Oh, oh.  That's not a formal GNU version number; what level of standard
bash feature support am I to expect, if I can't identify its parentage?

  bash$ ./win-bash --help
  .\win-bash.exe: --: bad option

seems it isn't going to tell me :-(

Regards,
Keith.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV