I find the inconsistency the worst problem, sometimes cmd-m sometimes cmd-b,m and sometimes both work. I can handle double keys for lesser used items, but some really common code editing things need a single key. I would actually like more shortcuts available for code refactoring like inlining etc - and I have a few others I want to add (which are now possible with a contribution I made to P7 that uses the ast to find the best nodes close to you cursor) like widen selection, jump to next code element etc. (Eg catch up with intelliJ). I guess there are just so many things to clean up, it can be Overwhelming, still, bit by bit. Tim Sent from my iPhone
On 7 Jul 2018, at 19:36, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
Shortcuts have long been a thorn for Pharo, the lack of global state and the fact that are hard coded. Colors and Themes had the same issue and it was the effort Esteban who wanted to bring the dark theme that really changed this. I suspect like Theme these are legacy Squeak stuff that are not easy to fix.
Ideally shortcuts should be fully customisable with preset support accessible from Pharo user settings. This way for example a vim user could implement his own set of keys after his favorite editor. It would be nice if that became a target for Pharo 7 or at least Pharo 8. No Pharo tool should be allowed to manage its own shortcuts , not even third party tools.
On Sat, Jul 7, 2018 at 6:18 PM Norbert Hartl <norbert@hartl.name> wrote:
Am 07.07.2018 um 17:08 schrieb Cyril Ferlicot D. <cyril.ferlicot@gmail.com>:
Le 07/07/2018 à 16:17, Ben Coman a écrit : Any seeming agreement may just have been the nay-sayers falling silent since there seemed little chance of having it changed when it came as a done-deal with Nautilus. Personally I tried to conform to using the double-sequence-shortcuts but could never get over the cumbersome feel of it, to the point where in Nautlius I actually stopped using shortcuts and reverted to using context menus.
I guess lovers of the double-sequence-shortcuts are now in that boat. I'm not sure there was much discussion around Calypso using single-key-shortcuts. But I'm personally very happy with this behaviour change introduced by Nautlius was reverted. I'm glad to using shortcuts in the System Browser again.
For my part I'm not because before I could delete/rename/add a package/class/protocol/method without the mouse but now it became much harder with simple key shortcut since it works only on the focused pane.
But I guess this kind of things depend on everyone.
Maybe it could be good to be able to customize it via settings.
I donât understand anyway why keyboard shortcuts are dependent on a tool. Shouldnât there be an abstraction mapping between action and shortcut?
Norbert
cheers -ben
-- Cyril Ferlicot https://ferlicot.fr