The Typo3 bundle (installed via Preferenes → Bundles) binds Cmd-T to “Get TypoScript Setup”.
I have long ago removed this keybindig, resulting in a delta bundle in ~/Application Support/Avian/Bundles/TYPO3.tmbundle (see https://gist.github.com/noniq/5186969 – these are the only 2 files in this bundle).
Since a9397, this does not work anymore: Cmd-T again calls „Get TypoScript Setup“, even though the bundle editor shows “Key Equivalent:” shown as empty.
Binding the action to any other key works as expected. If I then delete the keybinding, again Cmd-T seems bound to this action (without being shown in the bundle editor).
Apart from this bug, I wonder why the Typo3 bundle binds Cmd-T at all. Should I prepare a pull request removing/changing this binding?
Regards, stefan
On 18 Mar 2013, at 14:09, Stefan Daschek wrote:
Since a9397, this does not work anymore: Cmd-T again calls „Get TypoScript Setup“, even though the bundle editor shows “Key Equivalent:” shown as empty.
This is the same issue as discussed in the ‘a9397 + CTags’ thread.
Latest nightly build fixes it.
Apart from this bug, I wonder why the Typo3 bundle binds Cmd-T at all. Should I prepare a pull request removing/changing this binding?
Please do, no bundle should bind to ⌘T.
Am 18.03.13 14:51, schrieb Allan Odgaard:
Apart from this bug, I wonder why the Typo3 bundle binds Cmd-T at all. Should I prepare a pull request removing/changing this binding?
Please do, no bundle should bind to ⌘T.
Interestingly enough, this binding seems not to be present in the original TYPO3 bundle (https://github.com/andyh/TYPO3.tmbundle):
After uninstalling the TYPO3 bundle via Preferences and installing a local clone in ~/Application Support/Avian/Bundles, Cmd-T is not overridden. Deinstalling the local clone and reinstalling the managed TYPO3 bundle via Preferences again binds Cmd-T to “Get TypoScript Setup”.
Regards, Stefan
-
Allan Odgaard -
Stefan Daschek