BUG? Read-Host 'xxx' can't read '!xxx'



Try this:

PS> Read-Host 'xxx'

and type !xxx there, i.e.

xxx: !xxx

I get this:

"!xxx" cannot be recognized as a valid Prompt command.
xxx:

and Read-Host still waits for my input.

*) Is it a bug?
*) If it is not a bug, what is that?
*) If it is not a bug, how do I enter a string starting with '!' using
Read-Host?

Note: if I do not use a prompt string at all, everything is 'fine', i.e.

PS> Read-Host
!xxx
!xxx

--
Thanks,
Roman

Don't ask me why :

MowPS>read-host 'xxx'
xxx: !!xxx
!xxx

gr /\/\o\/\/


"Roman Kuzmin" wrote:

> BUG? Read-Host 'xxx' can't read '!xxx'
>
> Try this:
>
> PS> Read-Host 'xxx'
>
> and type !xxx there, i.e.
>
> xxx: !xxx
>
> I get this:
>
> "!xxx" cannot be recognized as a valid Prompt command.
> xxx:
>
> and Read-Host still waits for my input.
>
> *) Is it a bug?
> *) If it is not a bug, what is that?
> *) If it is not a bug, how do I enter a string starting with '!' using
> Read-Host?
>
> Note: if I do not use a prompt string at all, everything is 'fine', i.e.
>
> PS> Read-Host
> !xxx
> !xxx
>
> --
> Thanks,
> Roman

"/\/\o\/\/" wrote:
> Don't ask me why :
> MowPS>read-host 'xxx'
> xxx: !!xxx
> !xxx

Well, at least we know how to live with that now.

--
Thanks,
Roman

"Roman Kuzmin" wrote:

> BUG? Read-Host 'xxx' can't read '!xxx'
>
> Try this:
>
> PS> Read-Host 'xxx'
>
> and type !xxx there, i.e.
>
> xxx: !xxx
>
> I get this:
>
> "!xxx" cannot be recognized as a valid Prompt command.
> xxx:
>
> and Read-Host still waits for my input.
>
> *) Is it a bug?

I'd vote this one.

> *) If it is not a bug, what is that?
> *) If it is not a bug, how do I enter a string starting with '!' using
> Read-Host?
>
> Note: if I do not use a prompt string at all, everything is 'fine', i.e.
>
> PS> Read-Host
> !xxx
> !xxx
>
> --
> Thanks,
> Roman

--
greetings
dreeschkind

Very strange. Please bug this.

--
Jeffrey Snover [MSFT]
Windows PowerShell/Aspen Architect
Microsoft Corporation
This posting is provided "AS IS" with no warranties, no confers rights.
Visit the Windows PowerShell Team blog at:
http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at:
http://www.microsoft.com/technet/scr.../hubs/msh.mspx

"Jeffrey Snover [MSFT]" wrote:
> Very strange. Please bug this.

I constantly can't connect to Connect. Can anybody file this issue?

--
Thanks,
Roman

Feedback-ID 195045 filed at connect.

https://connect.microsoft.com/feedba...5045&SiteID=99

--
greetings
dreeschkind

"Roman Kuzmin" wrote:

> "Jeffrey Snover [MSFT]" wrote:
> > Very strange. Please bug this.
>
> I constantly can't connect to Connect. Can anybody file this issue?
>
> --
> Thanks,
> Roman
>

Any input that starts with an exclamation mark in response to a prompt is
called a 'Prompt command.' It is an infrastructure to allow you to
interesting things like get help on a certain item, etc. I don't have an
example off-hand to show it in action, though.

--
Lee Holmes [MSFT]
Windows PowerShell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.


"dreeschkind" <dreeschkind@discussions.microsoft.com> wrote in message
news:BDF64891-DA29-44C0-A125-6627987C01AD@microsoft.com...
> Feedback-ID 195045 filed at connect.
>
> https://connect.microsoft.com/feedba...5045&SiteID=99
>
> --
> greetings
> dreeschkind
>
> "Roman Kuzmin" wrote:
>
>> "Jeffrey Snover [MSFT]" wrote:
>> > Very strange. Please bug this.
>>
>> I constantly can't connect to Connect. Can anybody file this issue?
>>
>> --
>> Thanks,
>> Roman
>>

"Lee Holmes [MSFT]" wrote:

> Any input that starts with an exclamation mark in response to a prompt is
> called a 'Prompt command.' It is an infrastructure to allow you to
> interesting things like get help on a certain item, etc. I don't have an
> example off-hand to show it in action, though.

This sounds like an interesting feature.
I'd love to read more about targeted use cases or see some examples soon.
Keep up the good work!

--
greetings
dreeschkind

> --
> Lee Holmes [MSFT]
> Windows PowerShell Development
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "dreeschkind" <dreeschkind@discussions.microsoft.com> wrote in message
> news:BDF64891-DA29-44C0-A125-6627987C01AD@microsoft.com...
> > Feedback-ID 195045 filed at connect.
> >
> > https://connect.microsoft.com/feedba...5045&SiteID=99
> >
> > --
> > greetings
> > dreeschkind
> >
> > "Roman Kuzmin" wrote:
> >
> >> "Jeffrey Snover [MSFT]" wrote:
> >> > Very strange. Please bug this.
> >>
> >> I constantly can't connect to Connect. Can anybody file this issue?
> >>
> >> --
> >> Thanks,
> >> Roman
> >>
>
>
>

"Lee Holmes [MSFT]" wrote:
> Any input that starts with an exclamation mark in response to a prompt is
> called a 'Prompt command.' It is an infrastructure to allow you to
> interesting things like get help on a certain item, etc. I don't have an
> example off-hand to show it in action, though.

I find this idea quite confusing. I thought that Read-Host is the only way
now to input something into PowerShell without
escaping/evaluating/wildcarding/etc. Well, it is not. But again, why to use
'!', i.e. a symbol legal for file system paths? File system paths are the
most popular candidates for a user input, aren't they?

It is questionable that a user will find this useful. But I already predict
my duty to teach any user what he/she has to avoid at input. And for many of
them it will not work anyway. I predict unpleasant time consuming issues
related to this 'good'.

--
Thanks,
Roman