Re: [MSH] MSH Not So Great For Interactive Users
- From: "Bruce Payette [MSFT]" <brucepay@xxxxxxxxxxxxx>
- Date: Mon, 23 Jan 2006 10:14:44 -0800
There are a couple of issues:
In Windows, console apps get command line editing for free when they read
lines in "cooked" mode. With some additional effort, it's possible to add
things like tab-completion using the alternate end-of-line character
provided by the console API. So for relatively modest effort you get an
adequate solution. Unfortunately the incremental jump in effort to move
beyond merely adequate is substantial. Now you have to read in character
mode and implement the entire command line editing subsystem yourself. This
effort got punted from V1 in favour of other features. In the mean time,
take a look at what Jeffrey Thompson has done with jaMSH where he's
integrated the GNU readline stuff into an msh host.
Once you have better basic editing, the next step is to address things like
internationalized character presentation, font handling and Windows
integration with things like selection, cut-and-paste. Here we're pretty
much stuck with what the console provides. There isn't a good way to work
around these issues. To get a proper Windows CUI experience, we need to
write a Windows Monad host. This is on the V2 list in some form or other.
BTW - for those who are fans of the csh-style ! commands, take a look at the
*-history cmdlets. They allow you to do some of the ! style editing. (Note
that this mechanism is completely independent of the console history.)
-bruce
--
Bruce Payette [MSFT]
Microsoft Command Shell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jon Forrest" <forrest@xxxxxxxxxxxxxxx> wrote in message
news:ubFP7hDIGHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
> Thomas Lee wrote:
>
>>> Specifically, MSH should
>>> be at least as good as csh/tcsh at reducing the number
>>> of characters I have to type (I recognize and agree that
>>> these shells are awful for scripting).
>>
>> First, remember that the way MSH is hosted limits MS's flexability. There
>> is some tab completion, but the limitations of the MSH host for V1 leads
>> partly to what you suggest.
>
> Several people have mentioned this, but I don't understand
> what they mean. I can understand that MSH doesn't have the
> kinds of features I was talking about because the developers
> just haven't gotten around to adding them, but I don't
> see any technical obstacles to adding them just because
> MSH is a console application or because of "the way
> MSH is hosted".
>
> Could someone elaborate?
>
> Thanks,
> Jon Forrest
.
- References:
- [MSH] MSH Not So Great For Interactive Users
- From: Jon Forrest
- Re: [MSH] MSH Not So Great For Interactive Users
- From: Jon Forrest
- [MSH] MSH Not So Great For Interactive Users
- Prev by Date: Re: Need help to find all server hard disk inventory
- Next by Date: Re: Is it safe to say that in Monad...
- Previous by thread: Re: [MSH] MSH Not So Great For Interactive Users
- Next by thread: Re: [MSH] MSH Not So Great For Interactive Users
- Index(es):
Relevant Pages
|
Loading