if reintroduce them means reintroduce them hardcoded as before, then I���m complete against it and I WILL NOT integrate such solution. 
I���m sorry for being so strong here, but previous implementation was lame and we need to get rid of them. 

Now, I understand people are used to use those bindings and also some others (no idea which ones because I never used them��� for me ocompletion is good enough��� but those are tastes). So I would be very happy to integrate a generic way to define keybindings and outputs (which is already there, with keymapping, but I mean an editor or something), and I would be very happy to integrate a default configuration (which of course, will include #ifTrue:/##ifFalse:)

Esteban



On 08 Aug 2015, at 12:45, Peter Uhn��k <i.uhnak@gmail.com> wrote:

I would also appreciate if it was readded, as I've been using it regularly.

Peter

On Sat, Aug 8, 2015 at 12:21 PM, ThomasHeniart <heniart.thomas@gmail.com> wrote:
I think it could be nice to keep this shortcut :)


On 08/08/2015 12:12, Franck Warlouzet wrote:
Hi,

Yes it was not on purpose. It is not implemented in Rubric, but I can do it if there is a need of it (which seems to be the case).

Franck

Date: Sat, 8 Aug 2015 12:09:22 +0200
From: i.uhnak@gmail.com
To: pharo-dev@lists.pharo.org
Subject: [Pharo-dev] ifTrue ifFalse shortcuts

Hi,

was removal of ifTrue/ifFalse shortcuts on purpose, or by accident?
(maybe was caused by switch to Rubric?)

Peter