I've been writing down all those minor irritations that happen to me that individually don't really have much in the way of an effect (and all have trivial workarounds). So I thought I'd just chuck the lot at you, not really expecting a fix for most of them (they are minor irritations, really), but just to be rid of them.
So here it is ...
Automatic new lines & indent
Example-Codeblock:
PowerShell Code
Double-click the code block to select all.{ Write-Host "haha" }
now imagine expanding this uniline scriptblock into a multiline scriptblock ...
PowerShell Code
Double-click the code block to select all.2 Scenarios: (Pressing Enter with cursor on "|")
1.: { Write-Host "haha"| }
2.: { Write-Host "haha" |}
PowerShell Code
Double-click the code block to select all.Result 1:
{
Write-Host "haha"
}
PowerShell Code
Double-click the code block to select all.Result 2:
{
Write-Host "haha"
}
In Scenario 1, the closing curly brace will be wrongly indented.Lagging Text-Entry during extended operation
When PSS 2014 has been running for quite some time (usually 6+ Hours), it occasionally slows down significantly, even though system resource consumption is negligible.
Several seconds lag between typing and written text are not uncommon when this occurs (and no other program is affected).
Fixed by restarting PSS 2014.
The size of the currently opened file doesn't appear to matter, however the entire project is 60000+ lines of code (most files not opened, even in background), in case that matters.
Module Projects:
When creating a new module project, I need to manually add the lines to the psm1 file that will load all .ps1 files (so that its Export-ModuleMember * does something).
Have CBH maintain indentation while editing
While editing the CBH, the editor maintains a linear indentation line as would be appropriate outside the CBH block. For example, inside a function it will have one indentation. However in the CBH all element headers have 2 indentations and all content has three (following my own default indentation anyway).
Example without manually changing indentation:
PowerShell Code
Double-click the code block to select all.function Get-Test
{
<#
.SYNOPSIS
ABCDEFG
.DESCRIPTION
HIJKLMNOP
Example after manually setting indentation:
PowerShell Code
Double-click the code block to select all.function Get-Test
{
<#
.SYNOPSIS
ABCDEFG
.DESCRIPTION
HIJKLMNOP
(While I'm at it: Automatic CBH generation will generate it completely without indentation).Param Block and indentation
New lines in a param block will not be indented until after pressing enter again (slightly irritating, no real impact).
Primal Sense: Parameter Aliases don't vanish
When typing a function or command, it will not offer parameters in primal sense that were already added. However, primal sense will offer its aliases.
Primal Sense: Escaped strings
If I place a $() inside a string, I can add code whose ToString() output will be part of the string. Primal Sense would be nice.
Primal Sense: Strings in parameters
If I write a string as an argument for a parameter, and that string contains a "-", it will start primal sense for the Parameters of the function.
Reset Indent for enclosed strings
Example of how it is:
PowerShell Code
Double-click the code block to select all.$string = @" | Default indent is here "@Example of how I'd like it:
PowerShell Code
Double-click the code block to select all.$string = @" | Default indent is here "@And that's it.
Lots of minor things with little impact and please don't interpret this as a complaint (it'd be major nit-picking, especially after the awesome job you guys did fixing stuff and implementing my requests recently). Just thought I'd mention it so I can discard it from the back of my brain (the next time I encounter it, I can in good consciousness ignore it as I've already reported it. Stupid brain
)Cheers,
Bosparan
