Text Edit
Latest
Get Save As back on Mountain Lion's File menu easily and without hacks
You can make the "Save As..." menu item more visible and easier to use simply by giving it a different keyboard shortcut. In 10.7 (Lion), Apple removed the 'Save As' menu item and replaced it with "Duplicate" which did not work the same way. Apple relented in 10.8 (Mountain Lion) by returning "Save As..." but they hid it as an optional menu item which would only be shown when you held down the Option key while looking at the "File" menu. (There is also a keyboard shortcut for "Save As..." in 10.8, but it is not very convenient: Command + Shift + Option + S.) Apple did such a good job hiding "Save As..." that many smart and knowledgeable Mac users still don't know that 'Save As...' exists in Mountain Lion. Fortunately for us, there is a very easy way to make "Save As..." more visible: just change its keyboard shortcut. I'm going to show you two different ways that you can do that (you only need to choose one). Option 1. Terminal.app If you are comfortable using Terminal.app, you can add a different keyboard shortcut this with one simple line. First, quit all your apps except Finder and Terminal. Then paste this command (as one line) into Terminal.app (and press Return): That's it! Launch TextEdit and open the 'File' menu and you should see "Save As..." back in its rightful spot with its original Command + Shift + S shortcut, as shown in the image above. Aside: After you enter the 'defaults write' command, you will not see any confirmation that it was entered correctly. Terminal.app is a little terse sometimes. If you want to verify it from the command-line, enter this: defaults read -globalDomain NSUserKeyEquivalents and look for "Save As..." = "@$s"; in the output. Option 2. System Preferences.app If you would rather not use Terminal, it's still very easy to add the keyboard shortcut. Launch the System Preferences.app, then open the "Keyboard" preference pane. At the top you will see "Keyboard" and "Keyboard Shortcuts" – click "Keyboard Shortcuts" (labeled '1' below). Then in the list on the left side, click "Application Shortcuts" (labeled '2' below). Then click the "+" button (labeled '3' below): Once you press that "+" button, a small window will appear asking you to enter the title of the menu item and the keyboard shortcut that you want to use. Enter "Save As..." in the "Menu Title:" field, and then press the keyboard shortcut that you want to use. In the example below I pressed Command + Shift + S: Note: It used to be true that you had to enter an actual ellipsis (which you can get by pressing Option + ; on a US-English keyboard). However, when I tested this in Mac OS X 10.8.2, it worked with three consecutive periods. Bonus Tip: Hide the "Duplicate" menu item. In my original article I suggested that you also enter a keyboard shortcut for "Duplicate" and while you can do that if you wish, you do not need to do that. However, if you would like to hide the Duplicate menu item, you can do that. There are two steps: first, remap "Save As..." to Command + Shift + S (as shown above). Then the 'trick' is to remap "Duplicate" to Command + Shift + Option + S. What you will have done is swap the keyboard shortcuts for "Duplicate" and "Save As..." which means that OS X will make "Duplicate" the optional command. If you open the "File" menu and hold down "Option" the "Save As..." command will change to "Duplicate" (Thanks to TUAW reader 'rbascuas' for pointing this out in response to the original article!) Important Addendum: "Keep changes in original document" As we reported in August 2012, the "Save As..." command in early versions of 10.8 had an unexpected and likely unwanted side effect in Mountain Lion: it would save the changes in the new document (created by "Save As...") but would also save the changes to the original document. However, Apple realized that users might not want that behavior, so in Mac OS X 10.8.2 they added an option "Keep changes in original document" which you can see here: Option A: If you want to save the changes you've made in the document and then save the document with a different name, then make sure that the box is checked. Option B: If you want your original document to stay as it was when you last saved it and create a new document based on the modified content of that document, then make sure that box is not checked. If you do not see the 'Keep changes in original document' box, then the application is probably going to give you the "Option B" behavior, but if you are not sure, I would suggest choosing Cancel in the "Save" dialog, then copy and paste the contents of the document into a new file, and save the new file. I know that's several extra-and-less-convenient steps, but if you are worried about preserving the original document, better safe than sorry. You could also save the file, duplicate it in Finder, and rename the new instance. Open old file and revert to previous save using 'Versions'. Frankly,I wish that Apple had just left the "Save As..." command alone, but for some reason they didn't ask my opinion. That said, I'm glad that they brought it back in Mountain Lion. I would have paid $20 for that feature alone. Note: This article was re-written and republished on 2013–02–21. The original process still works, but I wanted to update it to reflect some additional information. Read the previous version at web.archive.org.
Turning off the fog effect
Here's a neat tip from Amiyuy of the WoW Ladies Livejournal group. Personally, I don't mind the "fog" effect that sometimes pops up in game -- I experienced it most recently while doing OS the other day, though it pops up on the haunted Borean Tundra coast and a few other places ingame as well. But a few people don't get along with it too well; like the drunken blur effect, it can be somewhat overwhelming for those with a weak stomach.Fortunately, there's a way to turn both of those off -- you just have to dive into the config.wtf file in your World of Warcraft installation's WTF folder (open it up with Notepad on Windows or TextEdit on Mac, though be careful in there, and save a copy before you do it: if you accidentally edit anything else, it could cause problems on your game), add SET ffx "0" to the end of the file, save and close it, and then you shouldn't see that fog effect any more.
Unsung Snow Leopard feature: multiple-language spell checker
OS X has had a system-wide, built-in spell checker for a while now, but until Snow Leopard, it could only check the spelling of whatever your default language was. But what if you needed to prepare a document in another language, say for a college Spanish assignment? In that case, you'd end up with a document with pretty much every single word underlined in red, with no reliable way to spell check it. But now, OS X offers simultaneous spell checking not only in four different varieties of English, but also in Spanish, French, German, Italian, and six other European languages. You can mix and match these languages in a single document, and the built-in spell checker will intelligently adapt to whichever language it thinks you've switched to. Pages from iWork '07 doesn't seem to benefit from this new feature, nor does the 2008 version of Word, but it works just fine in Safari and TextEdit. With TextEdit you get an added feature: once it figures out what language you're typing in, autocorrect will work for that language just as well as it does for English. So, for example, when you write in Spanish, the computer's dictionary knows it has to look for words in Spanish. Or, if you'll forgive mi español descompuesto, Entonces, por ejemplo, cuando tú escribes en español, el diccionario de la computadora sabe que tiene mirar por palabras en español. That last sentence would normally have red underlines under nearly every word, but using TextEdit in Snow Leopard the spell checker adapted to Spanish spelling as soon as I finished typing "entonces." It also auto-corrected espanol to español, which is much easier than having to type option-n, n to get the tilde above the n. The adaptation seems to happen on a paragraph-by-paragraph basis. In other words, the spell checker doesn't seem to be intelligent enough to recognize when you switch languages in mid-paragraph, much less mid-sentence. The spell checker will do its best to figure out the primary language of the paragraph; for example, if you type a few words in English but the rest of the paragraph is in Spanish, the English words will show up as misspelled. There's some potential for confusion if you switch back and forth between languages within paragraphs, but between paragraphs there's no apparent issues. This would have come in really handy a couple of years ago; after opening some old Spanish assignments I had, I found some of my compositions riddled with minor errors (mostly misplaced accent marks) that the spell checker in Leopard or Tiger never would have caught. ¡Viva la Mac! View the video below for a brief glimpse of the new spell check behavior in action:
Close brackets and braces easily with AutoPairs
If you're the type that spends the day staring at a display and typing code, we'd bet you'd appreciate any utility that will make the process easier. Check out AutoPairs. It's a Mac OS X preference pane that closes your brackets, braces and quotes for you. Type a left bracket, for instance, and a right bracket and left arrow appear. Pretty spiffy, especially when you consider that BBEdit doesn't do this out of the box.Note that, since AutoPairs is a preference pane plug-in, it won't work under Rosetta, though the developer promises that a universal version is in the works. AutoPairs requires Panther or better and is free.[Via ...on a long piece of string]
