Hi,
Don't know what I've done or how it happenend, but I have inexplicably lost the ability to save a file using Command-S on the keyboard. Saving a file from the menu works fine.
I've tested the Command-S in other applications, and it works as expected so I'm reasonably sure it's not a dead or malfunctioning key on my keyboard.
I had hoped the recent update might restore the Command-S function, but no joy.
Suggestions for how to get the Command-S function back?
Thanks
Joe
On Apr 3, 2006, at 6:10 PM, J. De Salvo wrote:
Hi,
Don't know what I've done or how it happenend, but I have inexplicably lost the ability to save a file using Command-S on the keyboard. Saving a file from the menu works fine. Suggestions for how to get the Command-S function back?
I seem to recall this coming up on the list recently, but couldn't find anything. I would guess that maybe Command-S has been accidentally bound to some bundle command/macro? Run the command Textmate->Show Keyboard Shortcuts and see if Command-S appears somewhere there. Then you'll need to change that command's shortcut.
You can always move com.macromates.textmate.plist to another location, and/or move the local modifications to the bundles in ~/ Library/Application Support/TextMate and see if that fixes things.
Thanks
Joe
Haris
Haris,
On 4/3/06 you or someone claiming to be you wrote:
On Apr 3, 2006, at 6:10 PM, J. De Salvo wrote:
Hi,
Don't know what I've done or how it happenend, but I have
inexplicably
lost the ability to save a file using Command-S on the keyboard.
I would guess that maybe Command-S has been accidentally bound to some bundle command/macro? Run the command Textmate->Show Keyboard Shortcuts and see if Command-S appears somewhere there. Then you'll need to change that command's shortcut.
Thanks for the prompt reply. Your suspicions were right on. Somehow, likely user error, the Command-S had become bound with an 'Untitled' command in the XHTML bundle.
Deleted that command--it looked as if I was experimenting with the backup-before-making-a-save command that I had read about on the wiki.
All is well now. Thanks again.
Joe
On Apr 3, 2006, at 7:36 PM, J. De Salvo wrote:
Thanks for the prompt reply. Your suspicions were right on. Somehow, likely user error, the Command-S had become bound with an 'Untitled' command in the XHTML bundle.
Glad to hear that it works fine now
Allan: Slight UI suggestion, since I have been bitten from it many times, and I am guessing I am not the only one. Imagine the following situation: I have just created a new command and associated a shortcut to it. When I do that, the focus correctly moves to the scope field. Then I decide I did not want a shortcut and press the x on the key equivalent field to delete the current shortcut. In that case, the focus remains on the key equivalent field, and any keypress at this point will create a shortcut, resulting in very funny and weird phenomena, since people are very likely to use some TextMate command at this point. You can't even close the bundle editor with cmd-w at this point. (Once, quite naturally, cmd-backtick got tied this way, since I tried to change windows after removing the key equivalent. It took me a while to figure out what was going on :) )
I am guessing the use case you have in mind is that people would delete the current key equivalent in order to place a new one. But in fact they can place the new one without deleting the old keyequiv, so in my opinion it would be more natural to move focus to the next field when the x is being pressed, which is consistent with the behavior when a key equivalent is in fact selected. Just my 5 cents.
Haris
On Apr 3, 2006, at 4:53 PM, Charilaos Skiadas wrote:
Run the command Textmate->Show Keyboard Shortcuts and see if Command-S appears somewhere there. Then you'll need to change that command's shortcut.
When I do this (Automation > Run Command > TextMate > Show Keyboard Shortcuts) I get a list of ONLY html shortcuts. How do I see what ALL the keyboard shortcuts for all the bundles are?
(I haven't lost command + s, but I HAVE lost control + escape!)
eo
On 4/4/2006, at 6:37, Eric O'Brien wrote:
On Apr 3, 2006, at 4:53 PM, Charilaos Skiadas wrote:
Run the command Textmate->Show Keyboard Shortcuts and see if Command-S appears somewhere there. Then you'll need to change that command's shortcut.
When I do this (Automation > Run Command > TextMate > Show Keyboard Shortcuts) I get a list of ONLY html shortcuts. How do I see what ALL the keyboard shortcuts for all the bundles are?
Could it be, that you have disabled all but the HTML bundle in the bundle editor?
(I haven't lost command + s, but I HAVE lost control + escape!)
A quick way to test TM with default bundles is to quit TM, rename ~/ Library/Application Support/TextMate and launch it again. That will show if it is a misconfiguration in the bundles.
On Apr 4, 2006, at 12:54 AM, Allan Odgaard wrote:
On 4/4/2006, at 6:37, Eric O'Brien wrote:
On Apr 3, 2006, at 4:53 PM, Charilaos Skiadas wrote:
Run the command Textmate->Show Keyboard Shortcuts and see if Command-S appears somewhere there. Then you'll need to change that command's shortcut.
When I do this (Automation > Run Command > TextMate > Show Keyboard Shortcuts) I get a list of ONLY html shortcuts. How do I see what ALL the keyboard shortcuts for all the bundles are?
Could it be, that you have disabled all but the HTML bundle in the bundle editor?
If you mean unchecked in Bundle Editor > Filter List... no, they are all checked
(I haven't lost command + s, but I HAVE lost control + escape!)
A quick way to test TM with default bundles is to quit TM, rename ~/ Library/Application Support/TextMate and launch it again. That will show if it is a misconfiguration in the bundles.
I renamed this folder and relaunched TextMate. (A new folder was not created.) Now when I run Show Keyboard Shortcuts, is empty, except for the popups. The "Jump" popups contain only a single choice: "Bundles:"
eo
On 4/4/2006, at 21:52, Eric O'Brien wrote:
I renamed this folder and relaunched TextMate. (A new folder was not created.) Now when I run Show Keyboard Shortcuts, is empty, except for the popups. The "Jump" popups contain only a single choice: "Bundles:"
It might be, that it’s finding the wrong TextMate executable. Could you try pasting the following 7 lines in Terminal, and see if it outputs the proper path to TextMate?
gcc -x objective-c -framework Cocoa <<EOF - && ./a.out #import <Cocoa/Cocoa.h> main () { NSAutoreleasePool* pool = [NSAutoreleasePool new]; puts([[[NSWorkspace sharedWorkspace] fullPathForApplication:@"TextMate"] UTF8String]); } EOF
If not, you probably want to reset your launch services database:
/System/Library/Frameworks/ApplicationServices.framework/ Frameworks/LaunchServices.framework/Support/lsregister -kill -r / System/Library/CoreServices /Applications /Developer/Applications
The result of running your bit of code was
(null)
I noticed inside it the fragment fullPathForApplication:@"TextMate"
and remembered that I had RENAMED my version of TextMate to "TextMate 1.5." Surprise! (or not) after I changed the application's name back to simply "TextMate" Running the Show Keyboard Shortcuts Command creates many pages of output.
I realize now that the only shortcuts I was seeing earlier were from bundles I had added or modified (that is, those that were in ~/ Library/Application Support/TextMate/).
Well, that fixes one mystery... two to go (currently).
Thanks!
On Apr 4, 2006, at 4:30 PM, Allan Odgaard wrote:
On 4/4/2006, at 21:52, Eric O'Brien wrote:
I renamed this folder and relaunched TextMate. (A new folder was not created.) Now when I run Show Keyboard Shortcuts, is empty, except for the popups. The "Jump" popups contain only a single choice: "Bundles:"
It might be, that it’s finding the wrong TextMate executable. Could you try pasting the following 7 lines in Terminal, and see if it outputs the proper path to TextMate?
gcc -x objective-c -framework Cocoa <<EOF - && ./a.out #import <Cocoa/Cocoa.h> main () { NSAutoreleasePool* pool = [NSAutoreleasePool new]; puts([[[NSWorkspace sharedWorkspace] fullPathForApplication:@"TextMate"] UTF8String]); } EOF
If not, you probably want to reset your launch services database:
/System/Library/Frameworks/ApplicationServices.framework/ Frameworks/LaunchServices.framework/Support/lsregister -kill -r / System/Library/CoreServices /Applications /Developer/Applications
On 5/4/2006, at 2:34, Eric O'Brien wrote:
I noticed inside it the fragment fullPathForApplication:@"TextMate"
and remembered that I had RENAMED my version of TextMate to "TextMate 1.5." Surprise! (or not) after I changed the application's name back to simply "TextMate" Running the Show Keyboard Shortcuts Command creates many pages of output.
Ah -- actually, the code shouldn’t ask for TextMate by application name (but instead by bundle identifier). I will fix that.
So there's a way to avoid this problem. Excellent! Gee, it IS a Macintosh... I should be able to name my apps whatever I want, eh? ;)
eo
On Apr 4, 2006, at 5:50 PM, Allan Odgaard wrote:
On 5/4/2006, at 2:34, Eric O'Brien wrote:
I noticed inside it the fragment fullPathForApplication:@"TextMate"
and remembered that I had RENAMED my version of TextMate to "TextMate 1.5." Surprise! (or not) after I changed the application's name back to simply "TextMate" Running the Show Keyboard Shortcuts Command creates many pages of output.
Ah -- actually, the code shouldn’t ask for TextMate by application name (but instead by bundle identifier). I will fix that.
-
Allan Odgaard -
Charilaos Skiadas -
Eric O'Brien -
J. De Salvo