I was bothered by the fact that I could not easily change the state of a message within a conversation from 'unread' to 'read.' That is when one clicks on a thread in the middle pane of mail, one can read all incoming messages in a conversation, but this does not change the state of all the messages. You actually have to click on each individual message.
So playing around, I discovered that hitting the Right-arrow key unrolls the entire list of incoming messages in a conversation right in the middle column immediately under the cluster list item. It is now only a matter of navigation with the arrow key to read, and hence, change the state of message, and then come back to the original conversation cluster item. You can then close the list by hitting the Left-arrow key.
[crarko adds: This seems like a pretty handy shortcut.]
Sadly, Apple's decided to not include the popular Front Row with OS X Lion.
When Lion was released, it was found that you could install Front Row on Lion and it worked fine. That is, until Apple released iTunes 10.4, which changed the iTunes library format, so even if you installed Front Row, it couldn't see your iTunes content.
Here is how you can get Front Row working on Lion with the latest iTunes:
Install Front Row Enabler for Lion -- you can find a package installation at the very bottom of this link, under Attachments. You'll need to reboot after installing.
Make sure 'Share my library on my local network' is turned on in iTunes preferences.
To try this out once, run dns-sd as described in this post, using the command:
dns-sd -P "Local iTunes" _daap._tcp local 3689 localhost.local. 127.0.0.1 "Arbitrary"
Or to make this permanent, you can create a file in ~/Library/LaunchAgents called something like net.iharder.shareitunes.plist. The contents of that file should be the following:
If you use TextEdit as a scratchpad for typing in notes, and frequently close it without saving them, you wish to avoid Lion's longer wait to open a save dialog (which you don't always want) than the previous 'Do you want to save?' dialog.
While even an empty document (you typed something, then deleted it) will prompt for saving, a document with no undo history won't. I've found it's quicker on my system to use Command+Z to undo everything I've typed, then Command+W to close the window, than Command+W to close followed by a wait until I can dismiss the save dialog.
[crarko adds: That Save dialog does take a unusually long time to pop up. I'll make a guess this is because the system is doing its housekeeping for Autosave and Versions. Anyway, the method in the hint was definitely quicker when I tried it.]
Last week I was asked how it could be that a German Photoshop CS5 from one day to another 'forgot' the German language and only shows English menus and dialog boxes.
I thought this couldn't be -- maybe the German resource had vanished or the order of the languages in the System Preferences was wrong.
But the German localization files in Contents » Resources were there, and the German language was the first language in System Preferences so I did some research on the issue.
Photoshop CS5 needs a file named tw10428.dat in a subfolder named Locales » de_DE » Support Files of its application directory.
If you install a new scanner or camera there might be dialog box that asks if the TWAIN driver should be updated/replaced. In some cases this results in moving this .dat-File to the Trash and Photoshop forgets its multilingual capability. Check before you empty the Trash. In my case it was also possible to copy the .dat-file from another Photoshop CS5 installation.
This problem only occurs with CS5 as far as I can tell (my Photoshop CS3 doesn't have any Locales Folder in the application's directory, and I don't own CS4 to test it there) and as far as some forum posts and the actual problem tell me this only occurs in case of doing a TWAIN driver installation/update.
I imagine this might also occur with localizations other than German.
[crarko adds: I haven't tested this one. In some of their programs Adobe has offered a Repair installation option, and if CS5 has that it might also work.]
Ever since I wrote this hint, I was still looking for more and better ways to add attachments to Thunderbird. For one it has always annoyed me that the 'Mail PDF' function in the PDF part of the print dialog only works with Mail.app, even when Thunderbird has been set as default app for handling mail. The solution to this annoyance didn't occur to me until very recently.
In any app, for example Preview, open a document.
In the menu bar go to File » Print.
In the PDF part of the print dialog go to 'Edit Menu ...' (bottom line, last option in the menu).
A floating window appears: hit the + sign (bottom left).
Select Thunderbird from your applications folder (or any other app that will handle PDF files in some way) and hit Open in the Chooser Window
Now hit OK in the floating window
From the print dialog you can now send PDF versions of any document directly to Thunderbird as an attachment.
One caveat: Thunderbird does not show the disk space required for the PDF, it does that only after sending the file or after saving the file as a draft (save as draft, close, reopen).
The other day, I had to logout and log back in to Gmail on my Mac. This was the first time I did this in Safari running on Lion.
When I clicked to login, Safari popped up a little dialog asking if I'd like to 'use Mail, iCal, and iChat' with my Gmail account. You can choose to add or not add. Choosing to add sends you to System Preferences where you can set this up for the system.
I haven't been able to test it with other email systems (i.e. Yahoo), but the implementation is pretty cool. Quick and easy way to setup Gmail in Lion.
[crarko adds: Thank you, iOS. Seriously, it is good to have all this stuff in one place, and that Safari is aware of it. Please note in the comments if you find any 3rd-party software taking advantage of this feature. I think that's my main reason for publishing this.]
Apple's Mail flags descriptive text can be edited.
If Red, Orange or Yellow do not reflect your flags usage you can change it. Once a message has been flagged, say, in yellow, you can click on the word 'Yellow' after opening the 'Flagged' folder in the Mailboxes list on the left. You can now edit the text.
[crarko adds: It looks like the Flagged folders are basically Smart Folders, and you can rename them however you like.]
This hint describes a way to completely, once and for all, disable all Resume features (that is, 'Reopen windows when logging back in' and Saved Application States) once and for all.
Disable Saved Application States
OS X Lion offers a checkbox to disable saved application states. However, many applications do not seem to care about that checkbox (e.g. Terminal). The easiest way to prevent applications from writing away saved states is exactly that: don't let them write to the saved application states folder.
To do this, first open up Terminal. Issue the following command to remove any saved application states you might have:
rm -r '~/Library/Saved Application State/*'
Now, prevent anything from writing it's state away ever again:
chmod -R a-w '~/Library/Saved Application State'
You may use the chmod command on individual application's folders inside the Saved Application State folder to prevent a single application from writing its state away.
Likewise, to re-enable saving states, use the same command but make the change 'a+w' instead of 'a-w':
chmod -R a+w '~/Library/Saved Application State'
Disable 'Reopen windows when logging back in'
To permanently disable 'Reopen windows when logging back in,' you can use the following command:
This will effectively disable 'Reopen windows when logging back in,' though the checkbox will still be ticked. However, this switch resets itself every time on reboot. To prevent this from happening, again we remove write permissions on the file containing the option:
This should do it. But there's where OS X gets nasty. When it can't write to this file, it will try to put the write permissions back itself. The solution is to change the owner to root, effectively preventing anyone (but root) from changing permissions on the file:
[crarko adds: Definitely do this at your own risk. About the only thing most of us might ever care to do would be preventing some individual application from saving its state, as is mentioned near the end of part 1 one of the hint. If you try this I'd suggest testing it with a dummy account first. Note that all the permission changes are only made to files in the user account Library.]