Casey Crockett
My feedback
-
2 votesCasey Crockett
supported this idea
·
An error occurred while saving the comment -
13 votesCasey Crockett
supported this idea
·
-
40 votes
Hi Bartek,
You’re right in that this is annoying. We will likely change the behavior as a bugfix. If anyone really, really likes the old behavior, we may decide to add an option to re-enable it.
Thoughts everyone?
Joey
Casey Crockett
supported this idea
·
-
48 votes
We’re not sure how much work this might be, but we’ll look into it.
Thanks,
JoeyCasey Crockett
supported this idea
·
-
56 votes
Hi Stephane,
I assume you mean the same behavior as when the ISE crashes and recovers your session? I would also love to see this. We’ll post back here if/when it gets implemented.
Thanks,
JoeyCasey Crockett
supported this idea
·
-
58 votes
We may evaluate this is a potential future add-on under the new ISE Preview model. Read more about the ISE Preview here: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
Casey Crockett
supported this idea
·
-
57 votes
This is a very difficult thing to implement, it could potentially break many of the add-ons, and could introduce some very confusing UI elements.
That said, we’re interested to get more ideas from you for how something like this might work. Feel free to post your comments below.
Thanks,
JoeyAn error occurred while saving the comment Casey Crockett
commented
Maybe I'm not understanding an underlying issue here. Why not open a second ISE for the second monitor?
And, I find it helpful to run a couple non-ISE Powershell consoles for one-off command runs and command and help lookups, but I don't see the benefit of separating the ISE console. I thought the benefit of the ISE was having the editor and console together.
It seems to be more about the -Include and -Exclude options and how they are working with the collection of items.
Assuming there are directories, *.txt files, *.pdf files, and *.zip files in the current directory, the below command is returning nothing.
Get-ChildItem -File -Exclude "*.zip", "*.pdf"
If I take out the -File option, I get items returned with the exclude working, but directories are also included.
It only seems to work as intended, as Douglas mentioned, if I directly specify the path with a wildcard like the below command.
Get-ChildItem -Path "some directory\*" -File -Exclude "*.zip", "*.pdf"
For me, the -Include option works the same wether I have the -File option or not. The below command returns nothing assuming the same current directory as above.
Get-ChildItem -include "*.txt", "*.zip"
Nothing is returned until I add the wildcard path. That is not very handy or intuitive.
I'm on Win10 and $PSVersionTable output is below.
Name Value
---- -----
PSVersion 5.1.14393.1198
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.1198
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1