A recent hint mentioned that all keystrokes in Snow Leopard get sent to the remote computer when Screen Sharing. This means that Command-Tab and other keystrokes get sent along, and there isn't a keyboard method for returning control to your Mac. Instead, you must move the mouse out of the shared window and click on a local window.
Sometimes, though, you might want to keep the mouse in a particular location in the remote computer. In particular, when I'm helping my mom remotely, I don't want my mouse movements to make the mouse on her screen move.
The solution? Push the power button on your computer. The "Are you sure you want to shut down your computer now?" dialog appears, and the mouse focuses on your local computer. Move the mouse outside the shared window, and then hit the Escape key, or just use Command-Tab to get to a different local window. (Be very careful not to hit the Return key, or you'll shut down your computer!). The shared computer mouse stays right where it was, and you're back to local control.
This little hint is hidden away in a video tip (ExposÚ Basics) on Apple's ExposÚ page, but strangely, isn't covered in the built-in ExposÚ help.
While in ExposÚ's All Windows mode (F3 or F9), pressing Command-1 will sort the windows alphabetically based on window name; pressing Command-2 will sort them by application name. Doing the same in ExposÚ's Application Windows mode will sort the windows alphabetically (obviously, sorting by application won't work in this mode).
[robg adds: Command-1 works as described in the video, but I'm uncertain as to how things are being arranged with Command-2 -- it doesn't seem to be alphabetical by program name on my Mac. I pressed Command-2, and wound up with this sort order (going left-to-right, three apps per row): Path Finder, Preview, Activity Monitor, Firefox, Terminal, System Preferences. I couldn't reconcile this order to either the order of the apps in the Dock, nor their order in the Command-Tab switcher. Anyone have any insight into the Command-2 sort order, or is my machine just behaving oddly?]
In order for Snow Leopard's new auto-correction feature to work, you need to have both "Correct spelling automatically" and "Check spelling while typing" enabled under Edit » Spelling and Grammar. I searched in the OS help files and online, and I couldn't find any documentation that actually stated this. In fact, TextEdit's Help says:
To have TextEdit automatically correct spelling errors, do one of the following:
To automatically correct spelling in the current document, choose Edit > "Spelling and Grammar" > Correct Spelling Automatically.
To automatically correct spelling in new documents, choose TextEdit > Preferences, click New Document, and select "Correct spelling automatically."
Logically, this hint is pretty obvious: the system won't auto-correct if it's not checking while typing. However, allowing "Correct spelling automatically" to be checked and then having nothing happen is confusing behavior for users. It seems to me that a better behavior would be to have the option grayed out unless "Check spelling while typing" is checked.
There seems to be a bug in 10.6 (including 10.6.1) that I stumbled on when I ran out of disk space.
The OS popped up the usual Free up disc space and/or force quit some applications warning. After freeing up over a gigabyte of space, and clicking the Resume button, nothing happened -- the app(s) remained paused. I deleted another four gigabytes worth of files on the disk, but to no avail. The only option seemed to be to force quit the apps.
The fix is fairly simple:
Free up some disk space, or close some of the memory hogging apps that aren't paused so you can save your work.
Open up Activity Monitor and find the paused processe(s). Their entries will be red so they are easy to spot, and they'll say (Not Responding) beside their names.
Note the process ID (PID) of the offending application(s);
Open up Terminal.app, and type kill -CONT processid, where processid is the number you noted earlier, then press Return.
This will return your frozen apps to your control, ready to save and quit your work.
[robg adds: I can't confirm the out-of-disk-space-bug, but this hint discusses how to pause and resume apps from Terminal using the kill command.]
Here's how to create your own Print File service, so you can easily print the selected file. Open Automator and choose Service from the initial dialog. In the search box on the left, search for Print Finder Items, then drag that action into the right-hand frame.
At the top of the right-hand frame, set the first drop-down to files or folders, then save your Service as Print File (or whatever you want to call it). You can now print by selecting a file and choosing Service » Print File, and you can optionally assign a keyboard shortcut using the Keyboard Shortcuts tab of the Keyboard System Preferences panel.
[robg adds: I'd suggest setting the second drop-down menu to Finder, as that's where it makes sense to be selecting files for printing. I tested this (by building it myself, not by using the downloaded file), and it works -- note, though, that the file will print immediately, without any confirmation or settings panel, nor with any ability to select which printer will be used.]
I've noticed in 10.6 that when I use ExposÚ in Application Windows mode, it shows me all my windows, not just the ones in the current Space. I always end up clicking on the wrong window and being whisked away to a another Space. To stop that from happening, open Terminal and run these two commands:
$ defaults write com.apple.dock wvous-show-windows-in-other-spaces -bool FALSE
$ killall Dock
From now on, ExposÚs Application Windows mode will only show windows in the current Space.
[robg adds: To reverse this hint, use defaults delete com.apple.dock wvous-show-windows-in-other-spaces and then kill the Dock again.]
I quite often open a bunch of windows in one Space and minimize them, yet have the application open in another Space. This turns into a pain when I go to un-minimize the windows, as they then open in the Space in which they were minimized.
However, if you Command-click a minimized window in the Dock, it opens in the current Space, instead of its originating Space.
[robg adds: Based on my testing, this only seems to work in 10.6, so I've marked it as such.]