Oh crap. Yes, I got them confused. I use both systems heavily. Sorry! I agree that this should be disabled. :)
On Sun, Jul 19, 2009 at 5:15 PM, björn<bjorn.winck...@gmail.com> wrote: > > 2009/7/20 Matt Tolton: >> >>> - I found a way to disable Cocoa's key binding system (via a private >>> API) so any custom bindings in >>> ~/Library/KeyBindings/DefaultKeyBinding.dict will be ignored. Without >>> disabling key bindings it is way too easy to shoot yourself in the >>> foot and you should use Vim's functionality to define custom key >>> bindings anyway. >> >> Does this have to happen? I have a global remapping for 'Select Next >> Tab' and 'Select Previous Tab' menu items, and right now it works >> beautifully with MacVim. > > I think we are talking about two different things. I assume you made > your remapping in the "Keyboard & Mouse" System Preferences? That > still works. I like this feature...check out my post about it in > combination with Services: > > http://b4winckler.wordpress.com/2009/07/16/macvim-services/ > > A bit of self-promotion for my newly started blog there, but I think > more people on this list may find that interesting. :-) > > I'm talking about this: > > http://devworld.apple.com/documentation/Cocoa/Conceptual/EventOverview/TextDefaultsBindings/TextDefaultsBindings.html > > That is, Mac OS X's system which lets you bind key combinatioins to > Objective-C selectors via a plist file. This never worked very well > with MacVim (and caused at least one Issue report in the past). This > is what I have disabled now. > > Björn > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
