On Wed, Oct 7, 2009 at 3:04 AM, Allan Odgaard mailinglist@textmate.org wrote:
On 6 Oct 2009, at 21:29, Ken Scott wrote:
I didn't think I was starting a new thread. I have a problem in the exact area that the original message was discussing.
Regardless, the _only_ change in my system was the update to Snow Leopard. Since then, the Enter key to trigger the Commit button does not function, and in the summary area itself, the arrow keys and number keys do not function. I haven't done anything with key bindings or anything else listed in the help page referred to.
So the keys work in TextMate but not commit window?
The keys work just fine in TextMate.
The summary area is a standard (system) text field. Try the keys in TextEdit.
And also work just fine in TextEdit.
Also tty press your numlock key a few times to reset potential bad state info.
Are there other suggestions as to what may be happening? Is anyone else experiencing this issue with the Subversion Commit window?
http://wiki.macromates.com/Troubleshooting/101
Note though that the commit window is an external program brought up, so it does not make sense to reset TextMate preferences or similar, since TextMate is not involved. But do try create new account.
I will try creating a new account and see what happens. I'll report back.
Ken Scott
On Sat, Oct 3, 2009 at 12:28 PM, Allan Odgaard <mailinglist@textmate.org
wrote: On 30 Sep 2009, at 18:06, Ken Scott wrote:
Since installing Snow Leopard and updating to the latest TextMate, none of the keys to the right of the main part of the keyboard (forward delete, arrow keys, num pad, Enter key) work in the Commit window.
Do I need to adjust something to get these to work again?
Don’t just reply to some random letter to start a new thread.
As for your missing keys, this is not a known problem and normally missing keys are caused by “outside” problems, see http://wiki.macromates.com/Troubleshooting/KeyBindings for some troubleshooting suggestions.
On Thu, Sep 17, 2009 at 6:33 AM, Filip Tepper filip@tepper.pl wrote:
On Sep 17, 2009, at 2:28 PM, Allan Odgaard wrote:
So far all issues reported with (ruby) commands have been caused by using a custom built ruby.
What the exact issue is with (some) custom built rubys, we still do not know. So best to ensure that /usr/bin/ruby is used.
Thanks for the hint, I'm using REE indeed.
A quick workaround for that issue just popped in after your e- mail - setting TM_RUBY variable to /usr/bin/ruby in Properties / Advanced / Shell Variables tab fixes the issue.
-- Filip Tepper