-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Since upgrading to Leopard, I've had one very annoying problem. I cannot get textmate to open a file when it has no extension and has not been explicitly set to be opened by textmate yet. I've read the blog on Leopard issues, and while this is similar to the quickview issue, I think this is a new perspective.
In particular, I work with a lot of svn or svk checkouts, set up as a project in the drawer. One of the filenames of a most important part of the project is amavisd-maia. no extension, as is common for a lot of unix programs. It's actually a perl file, but textmate (OSX probably, but textmate follows the suggestion) insists on calling it an executable and running it. Worse, it does so silently with no user feedback at all... it took me forever to find out that it was executing it without a terminal.
The only way to make it work is to open the info view in finder, and change the program to open it with, but it only works on the one file. If I wipe the project and check out a new copy, it does the wrong thing again. As near as I can tell, there is no way to tell OSX how to treat no-extension files.
I understand you want textmate to do the right thing when opening an image or something, but why can't there be a setting to force something to open in the editor? An option in the right click menu, "open in editor"? A modifier when clicking?
David Morton Maia Mailguard http://www.maiamailguard.com mortonda@dgrmm.net
On Apr 1, 2008, at 9:44 PM, David Morton wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Since upgrading to Leopard, I've had one very annoying problem. I cannot get textmate to open a file when it has no extension and has not been explicitly set to be opened by textmate yet.
Really? You can't get it to open? Or you can't get it to open by double-clicking it in the Finder? I'll assume the latter. Here are some alternatives:
* Drag the file to TextMate's Dock icon. (That's what I usually do.) * Right-click and use the "Open With" menu * If you're a Quicksilver user, you could grab the file with ⌘⎋ and "Open with…" ⇥ TextMate * File → Open, from within TextMate (duh) * I believe there was an "Open in TextMate" Finder toolbar button you could add, but I'm not sure where you can find it or if it works under Leopard
Having all no-extension files open in TextMate on double-click is wrong in my opinion and I was glad to find that the Leopard upgrade "broke" TextMate's attempt to take them over (because now I don't have to edit TM's Info.plist to remove the behavior with every upgrade). The problem is, under Tiger, no-extension files would lose their identity. Instead of being identified as a "Unix Executable File" with the appropriate icon, the files would be of unknown type with a generic icon. Lame.
Last I heard from Allan on this, there are three people like me who think the behavior was wrong and annoying, and 4 trillion people like you who don't care and just want to double-click stuff. So, you can feel good about being in the majority, but it looks like Apple has taken the ability to do inappropriate things with file types out of the hands of developers, so you might be out of luck.
--- Rob McBroom http://www.skurfer.com/
On 4 Apr 2008, at 18:47, Rob McBroom wrote:
[...] the Leopard upgrade "broke" TextMate's attempt to take them over
[...] it looks like Apple has taken the ability to do inappropriate things with file types out of the hands of developers, so you might be out of luck.
TextMate declares that it can handle public.data, there is nothing inappropriate about that, nor is it an attempt to take over all your file types, it’s to tell the system that TextMate _can_ handle all your file types (this information is not only used for double-clicks in Finder, it is also used e.g. when dragging a file on top of an application icon to decide whether or not a drop should be allowed).
The problem is that the file type system in OS X is extension based, and while this system is fully configurable (by the user) for files with extension, finding the application to open for files _without_ an extension is based on a heuristic which got changed in Leopard.
On Apr 5, 2008, at 4:35 PM, Allan Odgaard wrote:
TextMate declares that it can handle public.data, there is nothing inappropriate about that, nor is it an attempt to take over all your file types, it’s to tell the system that TextMate _can_ handle all your file types
You're right. The problem was not what TextMate was telling the system, but how that information was being interpreted. You probably explained that in the past and I forgot. Sorry. Anyway, I prefer the Leopard behavior. :)
--- Rob McBroom http://www.skurfer.com/
Have the same problem here.. 8/ find in project doesn't look into those files, clicking on file name in drawer, does nothing, very annoying.
Please fix this, it's really frustrating.
Thank you and have a great day! will
Really? You can't get it to open? Or you can't get it to open by double-clicking it in the Finder? I'll assume the latter. Here are some alternatives:
- Drag the file to TextMate's Dock icon. (That's what I usually do.)
- Right-click and use the "Open With" menu
- If you're a Quicksilver user, you could grab the file with ⌘⎋
and "Open with…" ⇥ TextMate
- File → Open, from within TextMate (duh)
- I believe there was an "Open in TextMate" Finder toolbar button
you could add, but I'm not sure where you can find it or if it works under Leopard
-
Allan Odgaard -
David Morton -
Rob McBroom -
Will Arp