Automating the world one-liner at a time…
The fine folks at Shell Tools just released a preview of their upcoming PowerShell Plus interactive shell – a 4 minute trailer to hint at things to come.
In PowerShell V1, working within a decades-old console host is what users find the most frustrating. That frustration doesn’t go unnoticed, and was even expected. As Jeffrey likes to say, “To ship is to choose.” We made a conscious decision to build upon the current console subsystem. We placed priority on engine features, the scripting language, cmdlet and provider framework, and everything else you know and love about PowerShell.
Time spent on a graphical host would have taken away from the time we got to spend making a powerful engine that partners could build upon. And build upon them they have!
If you haven’t seen it yet, PoshConsole is getting a lot of attention, as well: http://www.codeplex.com/PoshConsole
--Lee Holmes [MSFT]Windows PowerShell DevelopmentMicrosoft CorporationThis posting is provided “AS IS” with no warranties, and confers no rights.
To all you folks who are working on one of these, or are writing your own, two words:
I hate having multiple console windows open - tabbing them would save a lot of my screen real-estate. So please - add tab support!
With powershell analyzer. We already have tab support, as in multiple runspaces on tabs in the same application
With Powershell Plus we don't and won't because of a limitation of windows allowing only one true console attached to a process at a time.
However we are taking pains to simulate tab like behaviour.. Where the different instances of the console are seperate processes, but can be managed with hot keys to easily change between instances, and to manage them on the screen easily..
@Lee Holmes: "We placed priority on engine features, the scripting language, cmdlet and provider framework, and everything else you know and love about PowerShell. Time spent on a graphical host would have taken away from the time we got to spend making a powerful engine that partners could build upon."
You made ABSOLUTELY the right choice. Kudos.
While we are on the topic of Powershell consoles: I am trying to get powershell work inside xterm screen on the Unix Subsystem for Windows, but as you know, it doesn't work at all. I have to use the -command - option to get powershell accept input, but then none of the keyboard bindings work nor can I see the prompt.
The problem seems to be that the windows console I/O model is different from the unix tty, and so majority of the console apps do not work well. But considering that powershell is a great asset for people who have previous experience with Unix, I think it would be nice to have it working inside xterm/screen.