- MacSpeech
- Fetch Softworks
- Mark/Space, Inc.
- Web Crossing
- Readers Like You!
- CS Odessa
- VMware
- Microsoft
- Circus Ponies
- Bare Bones Software
We're at Macworld Expo 2009 in San Francisco with the latest news about the show. Check back often this week for updates!
- Phil Schiller Delivers Lackluster Keynote
- iPhoto '09 Adds Faces and Places
- iMovie '09 Seems to Fix Everything from iMovie '08
- GarageBand '09 Adds Music Lessons
- iWork Turns '09
- Apple Moves to Unprotected Music, Tiered Prices
- Apple Pioneers New Battery Tech with 17-inch MacBook Pro
- Jobs Clears the Air on Health Issue
- Welcome to Macintosh Movie to Screen at Macworld Expo
- MacHEADS Movie to Premiere at Macworld Expo
- TidBITS Events at Macworld SF 2009
Opening a Folder from the Dock
Sick of the dock on Mac OS X Leopard not being able to open folders with a simple click, like sanity demands and like it used to be in Tiger? You can, of course click it, and then click again on Open in Finder, but that's twice as many clicks as it used to be. (And while you're at it, Control-click the folder, and choose both Display as Folder and View Content as List from the contextual menu. Once you have the content displaying as a list, there's an Open command right there, but that requires Control-clicking and choosing a menu item.) The closest you can get to opening a docked folder with a single click is Command-click, which opens its enclosing folder. However, if you instead put a file from the docked folder in the Dock, and Command-click that file, you'll see the folder you want. Of course, if you forget to press Command when clicking, you'll open the file, which may be even more annoying.
Visit Eolake's Blog
Submitted by Eolake Stobblehouse
Recent TidBITS Talk Discussions
- iWork.com and MobileMe? (1 message)
- Safari Stalling on Opening PDF files (6 messages)
- A contrarian view of Macworld Expo's utility (3 messages)
- Secure Certificate Hack Doesn't Imperil Users (15 messages)
Published in TidBITS 903. Subscribe today to receive TidBITS in email every Monday.
- Apple Releases Minor MacBook and MacBook Pro Upgrades
- iTunes 7.5 and QuickTime 7.3 Released
- OSX.RSPlug.A Trojan Horse Targets Mac OS X
- Install Applications with iPhone 1.1.1 Software
- O2 Clarifies UK iPhone Data Limits
- Gmail's New IMAP Support a Boon to Mac and iPhone Users
- DealBITS Drawing: Win a Copy of TextExpander 2
- CARS Discovers Our Secret Agenda
- GrandPerspective and WhatSize Identify Disk Pigs
- Apple to Allow Virtualization of Leopard
- Leopard Firewall Takes One Step Forward, Three Steps Back
- Hot Topics in TidBITS Talk/05-Nov-07
Explaining Our Recent Server Woes
My apologies to anyone who has run into problems accessing the TidBITS and Take Control Web sites over the last few days. We've been experiencing some very weird errors, some of which have caused downtime, and in an attempt to isolate the cause, I've had to reboot the server numerous times and work with the extremely clued-in technicians at digital.forest to run hardware tests. Most notably, the machine was busy running memtest for most of Sunday night. The good news is that the RAM showed no problems across five passes (close to 12 hours of testing) so it can be eliminated as a possible cause; the bad news is that we're still struggling to figure out what might be happening.
We've tried to minimize the effect of this testing through four tricks:
- Since most TidBITS-related article traffic is actually served by Glenn's Web server, which identifies itself as db.tidbits.com, we repointed the DNS settings at easyDNS (which we recommend highly for being easy to use and reliable) for www.tidbits.com to db.tidbits.com. That way, anyone visiting our home page wouldn't see anything out of the ordinary. However, that worked for only the www.tidbits.com home page; other pages further down in the hierarchy just returned an error.
- For TidBITS Talk, the Check for Updates links in our ebooks, and other things that use emperor.tidbits.com, we again repointed DNS at Glenn's machine, and he set it so any emperor.tidbits.com request was served a page explaining the situation. Not ideal, but better than a generic error.
- For Take Control, where we didn't want to lock out potential ebook customers, we repointed DNS at Glenn's machine and set it up so any www.takecontrolbooks.com request loaded a custom page that looked much like the normal Take Control home page and made it easy for people to buy our Leopard titles via eSellerate. For other books, I linked to the version of our catalog on the eSellerate site. To judge from the number of orders that came in during the downtime, this approach worked fine.
- Since all of our incoming mail goes through Postini (now owned by Google, though we haven't seen any changes for better or worse since the acquisition) before arriving at our server, I tweaked Postini's settings so it sends email to the IP number of our server, rather than the domain name. That way, when I took our server down, Postini just held onto the mail (since it couldn't contact our server at its IP address) until I brought the server back online. Had I not made that change, Postini would have tried to deliver to Glenn's machine (when it was responding to emperor.tidbits.com). Since Glenn's machine doesn't accept mail for tidbits.com addresses, it would have rejected the messages.
Alas, we're still unsure as to the cause of the problems, but we have more things to try, all while attempting to minimize downtime. The server has great connectivity at digital.forest, and the technicians are helpful, but it's still difficult to troubleshoot a remote production server that's constantly modifying a 2.5 GB database file. I certainly hope we can fix things without anyone noticing, but if you do have trouble connecting, now you know why. For more detail, check my Twitter page, since I tend to post updates about what's going on even while the machine (and thus my email) is down.
It's time to speak up with MacSpeech Dictate! Get the all-newMacSpeech Dictate with spelling and phrase training. Speech
Recognition so good, about the only thing it can't do is
speak for you. Find out more at <http://www.macspeech.com/>