Vista - clr the editor?

Hmmm? clr not supported?

Also discovered a bug when entering...

c:\>cmd clr

Leaves the PowerShell open but no commands will run. The exit command has to
be submitted twice.

What you need is 'clear-host'. An alias 'clear' is defined for this. If you
want to type 'clr' then put

set-alias clr clear-host

in your $profile.

On my system 'cmd clr' runs a cmd.exe shell and leaves it at the cmd.exe
prompt (it doesn't clear the contents of the powershell window, which seems
reasonable). If I type 'exit' once I am back in powershell. So I am not
seeing a bug here.

"9-11 Was An Inside Job" wrote:

> Hmmm? clr not supported?
>
> Also discovered a bug when entering...
>
> c:\>cmd clr
>
> Leaves the PowerShell open but no commands will run. The exit command has to
> be submitted twice.
>
>
>

Hello,

Thanks for your comments. The behavior of typing clr is unexpected so it
certainly seemed like a type of bug or unhandled exception at the very
least.

I spent the early part of the evening reading the Word documents that have
been distributed as documentation. There certainly seems to be a need (and
opportunity) for tools and reference works built using HTTP to help work
through the syntax and grammar eh? One idea that came to mind was a method
to contextually load the MSDN documentation from within the shell.

The $profile (which I still haven't read yet) is the place to start though
and IMO should be the first chapter in the documentation so thanks for
bringing this to my attention.

One last note, have you noticed F7 does not support the use of Tab which
will take the last commands out of the buffer and put a selected command
onto the command line for modification if and when needed before using Enter
to submit?

"forestial" <forestial@discussions.microsoft.com> wrote in message
news:3D8A2E00-68BF-4283-A89D-6E25F9CE13A8@microsoft.com...
> What you need is 'clear-host'. An alias 'clear' is defined for this. If
> you
> want to type 'clr' then put
>
> set-alias clr clear-host
>
> in your $profile.
>
> On my system 'cmd clr' runs a cmd.exe shell and leaves it at the cmd.exe
> prompt (it doesn't clear the contents of the powershell window, which
> seems
> reasonable). If I type 'exit' once I am back in powershell. So I am
> not
> seeing a bug here.
>
> "9-11 Was An Inside Job" wrote:
>
>> Hmmm? clr not supported?
>>
>> Also discovered a bug when entering...
>>
>> c:\>cmd clr
>>
>> Leaves the PowerShell open but no commands will run. The exit command has
>> to
>> be submitted twice.
>>
>>
>>

Skip it... Just tried hacking it and discovered using F7 can be followed by
F9 which presents a dialog asking for the list item number of the command
wanted to be placed on the command line...


"forestial" <forestial@discussions.microsoft.com> wrote in message
news:3D8A2E00-68BF-4283-A89D-6E25F9CE13A8@microsoft.com...
> What you need is 'clear-host'. An alias 'clear' is defined for this. If
> you
> want to type 'clr' then put
>
> set-alias clr clear-host
>
> in your $profile.
>
> On my system 'cmd clr' runs a cmd.exe shell and leaves it at the cmd.exe
> prompt (it doesn't clear the contents of the powershell window, which
> seems
> reasonable). If I type 'exit' once I am back in powershell. So I am
> not
> seeing a bug here.
>
> "9-11 Was An Inside Job" wrote:
>
>> Hmmm? clr not supported?
>>
>> Also discovered a bug when entering...
>>
>> c:\>cmd clr
>>
>> Leaves the PowerShell open but no commands will run. The exit command has
>> to
>> be submitted twice.
>>
>>
>>

"cls" works, too, although I know that it's hard to change habits. As the
previous poster said, just create an alias in your profile for any familiar
commands.

When you type "cmd", you exit Windows PowerShell and host a cmd.exe session
in the PowerShell window.

Unfortunately, cmd.exe doesn't support clr either.

To return to Windows PowerShell, type "exit".




--
June Blender [MSFT]
Windows PowerShell Documentation
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.



"9-11 Was An Inside Job" wrote:

> Hmmm? clr not supported?
>
> Also discovered a bug when entering...
>
> c:\>cmd clr
>
> Leaves the PowerShell open but no commands will run. The exit command has to
> be submitted twice.
>
>
>