Michael Klement

There are two distinct severities to consider: * The _intrinsic_ severity of an error - what it is by design. * The _effective_ severity - if it was _promoted to...

As an aside: > It's not a terminating error anymore, it doesn't even show up in the error stream. Currently, the error produced by ` $e = try { 1/0...

@BrucePay: You're talking about the _effective_ severity - as ultimately surfaced, which is distinct from the _intrinsic_ severity - as originally emitted (see my [earlier comment](https://github.com/PowerShell/PowerShell/issues/4781#issuecomment-329585446)). Each piece of information...

Wow - that is very unfortunate. The workaround for now is to double-quote the argument (`cmd /c echo "a,x=$x"`). The problem isn't Windows-specific; Unix repro: `/bin/echo a,$HOME` and even `/bin/echo...

Good point; this basically affects all preference variables that aren't _predefined_ - see #3644. #3483 is related: Even those preference variables that are predefined and type-constrained in the _global_ scope...

I like the idea; a few comments: * `-From` and `-To` is probably a better pairing, though perhaps, given that `-Pattern` is already `[string[]]` typed, a `-Between` switch is enough...

@p0W3RH311, I don't think we want to refashion `Select-String` into an `awk`-like utility, which is both much more open-ended in its purpose while offering convenient features for splitting _each line_...

@iSazonov, could you please label this for the appropriate WG? Thanks.

From the coulda-woulda-shoulda department: In an ideal world, PowerShell would _consistently_ default to _ordered_ hash tables (dictionaries) (`[System.Collections.Specialized.OrderedDictionary]`), both with respect to `@{ ... }` literals and with what cmdlets...

@markekraus: Thanks for the background info. Yes, as I've said the terminating error arguably makes more sense, but the issue is that the behavior has _changed_ - namely in the...