Re: MinGW port - initial work uploaded

[Andy Parkins <andyparkins@gmail.com>]

On Tuesday 2007 January 23 15:20, Johannes Schindelin wrote:

> MinGW and cygwin differ in one very important point: cygwin needs an extra
> dll, MinGW does not.
>
> However, the development environment is still console-based, with a bash
> so you can run configure and simple bash scripts. It is definitely more
> catering to Unix types than Windows types.
>
> So yes, there is a bash, and there is a less, and there is perl.

Those are just tools for MinGW though aren't they?  They aren't needed to run 
the final executable object?  MinGW just spits out a native windows .exe - 
i.e. plain windows.  There is no reason to suppose that joe-random-developer 
will have bash, less and perl, even if they do have git.  Which was kind of 
the point I was making - there is no pager to rely on in Windows, so why not 
just drop it.  Okay, so MinGW comes with some nice UNIXy tools, but MinGW is 
the compiler, not the environment.

Am I still misunderstanding?  I'm looking out for the time when

C:\SomePath> git commit -a

will work (I know - it's a long way off yet).  Not for me; I don't care about 
Windows in the slightest; but some of my colleagues use it, and I'd like to 
spread the git-religion as far as I can.

> > That sounds better than I remember.  You'll have talked me into
> > migrating to Windows soon :-)
>
> I don't understand. The command "less" is the default pager of git, so you
> are prone to have used it already.

Of course I have; I was trying (failing) to be amusing.  :-)

Whenever I'm forced to use Windows, it's lack of the most basic of command 
line tools drives me insane, so you saying that less is easily available with 
good pipe support would ease my insanity slightly if were ever to go back to 
the dark place.


Andy

-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com