emacs/bash users beware - dan.kelley

As of version 1.1, beta 16, the control-F badness has gone away. This developer listens to users. Also, there are ways to cancel any key binding that is not favoured.

<p>Another poster has asked if there are other problems with key bindings. I am not an authority but I can give an opinion based on many hours of typing. Certainly, if you want full emacs bindings, don't use textmate. (Then again, why would you think of it, since emacs works well on OSX?) However, if you just use basic things like ctl-F, ctl-A, etc., then this editor doesn't seem to have any clashes. Another way to put this is that I used to scream out loud at the ctl-F behaviour (i.e. I am a touch typist who has little patience for unexpected results), and now I no longer get annoyed at all. That probably indicates that the bindings that are common to various osx text applications work correctly. For example, any keybindings that I've typed in this box using Safari (ctl-K, just a second ago) work fine in TM.

<p>My advice is to test it out.

Reply to This | Parent

Sunday, August 07 2005 @ 12:05 PM PDT

emacs/bash users beware - hombre

For the record, ctrl-a, ctrl-e, ctrl-b, ctrl-f, ctrl-k, and ctrl-y work in 1.1b17 (these are the same ones that seem to work in Cocoa applications in general). ctrl-u and ctrl-w do not work in Cocoa applications generally and in TextMate they do not work in Emacs fashion but are mapped to other functions: ctrl-w selects the current word and ctrl-u makes the current word all uppercase. These are the only Emacs key bindings that I am familiar with, so they are the only ones I tested.

The help file explains that TextMate has its own key bindings defined in path_to_textmate/TextMate.app/Contents/Resources/KeyBindings.dict (many of which are quite useful). These can overridden by the user in ~/Library/Application Support/TextMate/KeyBindings.dict.

Reply to This | Parent

Saturday, November 19 2005 @ 03:52 PM PST