Hello. I would like the cursor to follow me when I hit page up and down. I don't want to remember to hit the ctrl key. I have followed these instructions:
http://blog.macromates.com/2005/key-bindings-for-switchers/
But they don't seem to work for Textmate. Other apps (XCode, Textedit ...) behave as expected with the Keybinding set (the cursor nicely follows as the page scrolls), but with Textmate the cursor jumps around unpredictably, sometimes in the wrong direction. Anybody know whats up?
My bindings:
{ /* home */ "\UF729" = "moveToBeginningOfLine:"; "$\UF729" = "moveToBeginningOfLineAndModifySelection:";
/* Cmd-Left */ "@\UF702" = "moveToBeginningOfLine:"; "$@\UF702" = "moveToBeginningOfLineAndModifySelection:";
/* Cmd-Right */ "@\UF703" = "moveToEndOfLine:"; "$@\UF703" = "moveToEndOfLineAndModifySelection:";
/* end */ "\UF72B" = "moveToEndOfLine:"; "$\UF72B" = "moveToEndOfLineAndModifySelection:";
/* page up/down */ "\UF72C" = "pageUp:"; "\UF72D" = "pageDown:"; }
On 30 Jan 2011, at 01:30, Patrick Cullen wrote:
Hello. I would like the cursor to follow me when I hit page up and down. I don't want to remember to hit the ctrl key. I have followed these instructions:
http://blog.macromates.com/2005/key-bindings-for-switchers/
But they don't seem to work for Textmate. Other apps (XCode, Textedit ...) behave as expected with the Keybinding set (the cursor nicely follows as the page scrolls), but with Textmate the cursor jumps around unpredictably, sometimes in the wrong direction. Anybody know whats up?
Do you have smooth scroll enabled in System Preferences → Appearance?
If so, disable it at least for TextMate by quit’ing it and running this in Terminal:
defaults write com.macromates.textmate AppleScrollAnimationEnabled -bool NO
There is a problem with the heuristic Apple uses for this smooth scroll where the target rectangle TextMate asks AppKit to scroll to is “augmented”, leading to this seemingly random behavior.
Thanks, that did the trick. Would it be possible to append this information to the url I referred to in my first email:
http://blog.macromates.com/2005/key-bindings-for-switchers/
It looks like the post is closed for comments ... otherwise I would add a link from there to this answer in the mailing list archive. Maybe help keep other users from pulling there hair out ...
***Digression warning***
This has probably been beaten to death, but I will ask anyway ... The default Mac paging behavior is really hard for me to get used to. It seems to me that the primary use case when you scroll to a new location in an editable document is to "start editing", so it would be logical for the cursor to follow along. Is there some UI interaction pattern / use case that I don't understand? What reason could there be for leaving the cursor behind? And even if there is some scenario where it makes sense, is it more common than scrolling to a new location to start editing?
-P
On Sun, Jan 30, 2011 at 4:01 AM, Allan Odgaard mailinglist@textmate.orgwrote:
On 30 Jan 2011, at 01:30, Patrick Cullen wrote:
Hello. I would like the cursor to follow me when I hit page up and down.
I
don't want to remember to hit the ctrl key. I have followed these instructions:
http://blog.macromates.com/2005/key-bindings-for-switchers/
But they don't seem to work for Textmate. Other apps (XCode, Textedit
...)
behave as expected with the Keybinding set (the cursor nicely follows as
the
page scrolls), but with Textmate the cursor jumps around unpredictably, sometimes in the wrong direction. Anybody know whats up?
Do you have smooth scroll enabled in System Preferences → Appearance?
If so, disable it at least for TextMate by quit’ing it and running this in Terminal:
defaults write com.macromates.textmate AppleScrollAnimationEnabled -bool NO
There is a problem with the heuristic Apple uses for this smooth scroll where the target rectangle TextMate asks AppKit to scroll to is “augmented”, leading to this seemingly random behavior.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Jan 30, 2011, at 16:10, Patrick Cullen wrote:
It seems to me that the primary use case when you scroll to a new location in an editable document is to "start editing", so it would be logical for the cursor to follow along. Is there some UI interaction pattern / use case that I don't understand?
For me, it allows the cursor to serve as a temporary bookmark: if I need to, I can examine another part of the document, then start typing and immediately jump back to what I was working on.
If I need to edit something after paging, I'll probably want to use the mouse anyway to move the cursor, rather than stepping through with the arrow keys to the right line and column.
For me, it allows the cursor to serve as a temporary bookmark: if I need
to, I can examine another part of the document, then start typing and immediately jump back to what I was working on.
Makes sense. But if this is the intended use case, I don't think its well supported by the arrow keys. The arrow key behavior should be consistent with paging and scroll the viewport one line at a time, instead of jumping back to where the cursor is. Seems like there would be times where what you are interested in is between two "pages" so you need to finely scroll to get the relevant section all on the screen at once.
If I need to edit something after paging, I'll probably want to use the
mouse anyway to move the cursor, rather than stepping through with the arrow keys to the right line and column.
Yea, I guess my usage is very different :) I never want to use the mouse. Rather than stepping through one char at time with the arrow keys, I use ctrl-arrow to jump words and home end to move to the beginning end of the line - its usually only a few key strokes to position the cursor.
I hadn't really considered the temporary bookmark functionality, and I think it has its merits (if it were better supported with the arrow keys I might even use). But, I'm hard pressed to come up with enough scenarios outside of programming (eg. refer to method signature, start typing) to justify the lagging cursor as a good global Mac default. I guess I'm starting to rant, so I'll sign off - thanks :)
On Sun, Jan 30, 2011 at 4:58 PM, Kevin Reid kpreid@switchb.org wrote:
On Jan 30, 2011, at 16:10, Patrick Cullen wrote:
It seems to me that the primary use case when you scroll to a new location
in an editable document is to "start editing", so it would be logical for the cursor to follow along. Is there some UI interaction pattern / use case that I don't understand?
For me, it allows the cursor to serve as a temporary bookmark: if I need to, I can examine another part of the document, then start typing and immediately jump back to what I was working on.
If I need to edit something after paging, I'll probably want to use the mouse anyway to move the cursor, rather than stepping through with the arrow keys to the right line and column.
-- Kevin Reid http://switchb.org/kpreid/
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Kevin Reid -
Patrick Cullen