With TM2, it doesn't seem to honor my KeyBindings like 1.5 did, specifically, my emacs-like settings.
For instance, ^v and meta-v do not pageup/down as is specified in my DefaultKeyBinding.dict file. Another, ^k will delete the text on the line, but ^k on an empty line will not remove that line (this is particularly annoying because the only way to remove a line is select and delete it). Furthermore, I used to use ^w and ^y for yanking and putting text, but these don't seem to work any longer.
Anyone else seeing behavior like this? Is there something I am missing? I haven't changed my DefaultKeyBindings, and the behavior is fine in other Cocoa apps and TM1.5.
For now, I will assume it is just an alpha bug...
Thanks, Brian
I'm seeing the same-- and would also be interested in having these keybindings work-- they're so ingrained in my brain that I'm having trouble using the alpha (though I should add that I love many things about it).
On 18 December 2011 01:51, Brian Powell powellb@gmail.com wrote:
With TM2, it doesn't seem to honor my KeyBindings like 1.5 did, specifically, my emacs-like settings.
For instance, ^v and meta-v do not pageup/down as is specified in my DefaultKeyBinding.dict file. Another, ^k will delete the text on the line, but ^k on an empty line will not remove that line (this is particularly annoying because the only way to remove a line is select and delete it). Furthermore, I used to use ^w and ^y for yanking and putting text, but these don't seem to work any longer.
Anyone else seeing behavior like this? Is there something I am missing? I haven't changed my DefaultKeyBindings, and the behavior is fine in other Cocoa apps and TM1.5.
For now, I will assume it is just an alpha bug...
Thanks, Brian
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
For those who miss PageDown/Up in TM2 here's simple workaround to put into ~/Library/KeyBindings/DefaultKeyBinding.dict Instead of:
"\UF72C" = "pageUp:"; "\UF72D" = "pageDown:";
Which triggers "pageUp/Down:" selectors that do not respond in TM2, put:
"\UF72C" = ("moveUp:", ..., "moveUp:"); "\UF72D" = ("moveDown:", ..., "moveDown:");
Where ... means = put it as many times as many lines you want to jump on page up/down.
Have a nice Xmas,
On Dec 23, 2011, at 10:23 AM, Adam Strzelecki wrote:
For those who miss PageDown/Up in TM2
There have been several posts about the Page Up/Down keys not working in TextMate 2, but they have always worked for me. I press Fn-Up/Down on my laptop and the page goes up/down. Am I missing something?
Trevor
There have been several posts about the Page Up/Down keys not working in TextMate 2, but they have always worked for me. I press Fn-Up/Down on my laptop and the page goes up/down. Am I missing something?
Yeah, but if you try to do Opt+Page Up/Down which is supposed to move page together with caret or Shift+Page Up/Down which is supposed to extend selection by whole page it doesn't work in TM2, while it works perfectly well in TM1, and also in Xcode, TextEdit, etc.
Also some users (including me) has mapped regular (non Opt-ed) Page Up/Downs using DefaultKeybindings.dict to move caret as if Opt was pressed, some others mapped Emacs style keys. While it works perfectly well in TM1 it doesn't work in TM2.
All because selectors these actions are mapped to pageUp: pageDown: pageUpAndModifySelection: pageDownAndModifySelection: selectors (OSX class standard calls) which are defined for TextMate editor but have no effect upon a call (NYI I guess), in contrary to TM1 where these selectors move cared (or caret with selection) by one line.
Altogether these are pretty useful keys when you work with long files and you use keyboard only, that's why this workaround.
Regards,
-
A J -
Adam Strzelecki -
Brian Powell -
Trevor Harmon