Double-clicking on .txt files does nothing for me. Well, the icon does it's little "zoom out of the screen towards you" animation like it's going to do something, but TextEdit doesn't actually launch.
TextEdit is the associated application for .txt files. I've set it by going into the "Get Info" panel (command-I) for a .text file, selecting "
(
Read more... )
Comments 12
I dunno, that worked for me a couple times.
Reply
Reply
They recommend giving this a shot:
http://www.macosxhints.com/article.php?story=20031215144430486
Reply
Anyway, the idea on that page was a no-go -- the command worked fine, but the problem is still there. Thanks for the suggestion, though!
Reply
If the various new features from the marketing feature weren't doing it for you I can merely list a few more techie bullet points:
* We made a bunch of the UI less ugly, particularly the Library and Settings.
* The virtualization core has an added year of maturity.
* We fixed a ton of bugs in Unity.
* Each new OS X version and new piece of Apple hardware manages to break us in weird little ways so I wouldn't be surprised if you had some strange issues trying to run 1.1.x on 10.5.6.
Sorry to hear that didn't work. What happens if you run "open filename.txt" from terminal?
Reply
Ok, so my LaunchServices friends have some more extreme measures to try in that case... they say:
1. Delete /Library/Caches/com.apple.LaunchServices-*.csstore
2. Delete ~/Library/Preferences/com.apple.LaunchServices.plist and com.apple.LaunchServices.QuarantineEvents (if it exists).
3. Restart the computer, empty the trash.
4. Run the command:
Tiger: /System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -f -domain local -domain system -domain user
Leopard: /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -f -all local,system,user
Reply
Leave a comment