Re: [Mingw-users] mShell: mSys spawning system

[Keith M. <kei...@to...>]

Chris Sutcliffe wrote, quoting Greg Chicares:
[concerning design goals for Julien Lecomte's mShell project]
>> An mdi interface would be very handy.

Sure would.  If you can sidestep all the rxvt pty issues, Julien,
and make it work like KDE's Konsole, this will be a real winner!

>> It would be nice if this program could wrap different shells.
>> I use MSYS bash for './configure && make', zsh for everyday
>> work, and ash to make sure scripts are reasonably portable.

Yeah.  Just like in any terminal session on *nix, it should be
capable of running any shell -- even cmd.exe, for masochists :)
But, even if it did initially spawn MSYS' bash, and provided it
does offer a complete term infrastructure, an

  exec  /path/to/my/favourite/shell

should surely get you what you want; the choice of shell should
always be independent of the terminal in which it runs.  In a
real KDE Konsole, on GNU/Linux, I get bash by default, (because
I configured it that way), but I can always switch to pdksh, ash,
csh, tcsh, zsh, etc. at any time, just by exec'ing whichever one
I choose.  (And, in a moment of sheer insanity, I've just done an
`exec cmd.exe' in an MSYS rxvt -- works exactly as I expected).

> It would also be cool if you could specify the term (be it rxvt
> or cmd).

Isn't the whole point of this that it is independent of both rxvt
and Win32 console?  AIUI, Julien's app will provide the terminal
infrastructure in which you run the shell, and applications, of
your choice.  You wouldn't choose between rxvt and cmd, (I think
you really mean Win32 console, Chris), because *neither* has any
relevance -- mShell *is* the term.  Please remember that, whether
you choose to run it in rxvt, on in Win32 console, you still run
the same MSYS shell, and *neither* rxvt nor Win32 console is that
shell.

Regards,
Keith.