PowerShell Studio Feature RequestsFeature requests, product enhancement ideas, and other product-specific suggestions.
Please finally allow us to change the Keyboard Shortcuts
Jehoschua, Jan. 18, 2019Under Review
For an IDE, the usability is one of the most important features. The Sapien PowerShell Studio has great features, but the Keyboard Shortcuts are very annoying - especially very often used commands like Ctrl + Alt + P, G - it's already a pain to type it ;-)...
Please finally allow us to modify Keyboard Shortcuts - or even better: allow us to select the default keyboard mapping and share own mappings in a Team.
Such basic features are important: We already have users wich replaced Sapien PowerShell Studio by Visual Studio Code - just because of it's daily much better usability and the 'Visual Studio Keymapping' is installed in some seconds.
For me as the CIO, it's annoying to support more than one IDE for one programming language and Sapien has advantages compared to VS Code, therefore I still prefer PowerShell Studio.
But Sapien ignores simple but important feature requests very persistently, therefore we're close to stopping using PowerShell Studio.
Which feature requests you're ignoring persistently?
For example to automatically highlight the selected word. And - of course - not only in the source code, but in comments, too. We're waiting since years for it and assigning Ctrl + w to a similar (but less useful / incomplete :-() function, is annoying, because, since ~20 years, Ctrl + w is a very common hotkey to close the current file.
Comment by Alexander Riedel, Jan. 18, 2019
Hi Jehoshua. Thank you for yor input.
Comment by Alexander Riedel, Jan. 19, 2019
Just to keep you in the loop here, Ctrl+W has been used as closing the active tab since IE got tabbed browsing. I'd be very hesitant to attach an actual time frame to its use. The original Windows standard key to close the current window is and always has been Ctrl+F4. While is true that a good number of applications use Ctrl+W to close the current window, Visual Studio, which is what we use as a reference for keyboard shortcuts when in doubt, uses Ctrl+W to select the current word, just as we do in PowerShell Studio and PrimalScript.
We are indeed very hesitant to modify the keyboard layout our customers have been used to for decades, so I am going with no on changing the default definition of Ctrl+W.
You are however correct that there should be a way for customers to modify the hotkeys to their liking, so we will work on that and leave this feature request open to that end.
Comment by davidc, Feb. 5, 2019
In regards to highlighting text, please refer to the v5.6.158 service release article: