If you’re one of the many dual-display Mac users plagued by Apple’s annoying disappearing cursor, the easiest way to get your cursor back is to drag a window from the working display to the no-cursor display, (If the display that is working correctly doesn’t have a window open, right-click the desktop and choose ‘get info’ which will open a small info window.)
You don’t have to drop the window onto the other desktop, simply drag it over, then drag it back. For some reason dragging something restores the cursor.
IF THAT DOESN’T WORK: The problme also seems to go away if you sleep the displays (keyboard shortcut Control + Shift + Eject) then hit a key to wake them back up.
Suppose you’d like to use your Mac to send a couple hundred* customized emails once in a while, importing the recipient’s email + name + other data from a CSV file.
You’d think it would be a piece of cake.
Turns out, Apple Mail is worthless in this respect. Open Office has a built-in mail merge feature but it is poorly documented and horribly designed and works even worse. There is a Mac app called MailMergeApp, but it’s useless if you need to merge data from anything other than your Address Book.
Here’s how to do it using free software, and get it working in a few minutes:
1) Install the Thunderbird email client, at least for the purposes of sending merged-emails. (You don’t have to throw away your favorite email client.) We installed Thunderbird and configured it to use a dedicated outbound email address*.
2) In Thunderbird, open
Tools > Addons and find and install the “Mail Merge” addon.
3) Follow the detailed step-by-step instructions on the Mail Merge webpage.
We particularly like the “send later” feature which creates each email and puts it in your Outbox, so you can make sure it all looks good before you do
File > Send unsent messages
* Note, if you’re sending from a non-bulk-sender account (such as a typical Gmail or Godaddy email address), just keep in mind you probably have a maximum of 250-500 emails you can send per day.
This example assumes your pre-existing heroku account will be heroku.work and you are adding a new account heroku.personal.
It also describes how to move an app from one to the other, for example, if you have hit your 25-app max and are creating a new account and want to move some of your side projects and experimental apps out of your main account.
Did a quick benchmark last week to find the optimal way to configure Rspec on our projects that use Postgres and DatabaseCleaner
It seems that (unlike when controller methods are invoked via browser) if you do two consecutive get’s with rspec, instance variables are not cleared with each get, so data crossover is possible.
One of the many benefits of test driven development is the ability to catch somewhat subtle bugs like this during development…
The ActiveRecord find_each method is a great way to loop through large numbers of records. However, find_each will silently discard any order() criteria. Seems to me like a bug in find_each. However it was nice to find it in our rspec tests that verified certain things would be processed in a certain order.
Douche, acne remedy, toothpaste, deodorant (underarm and fridge and smelly shoes), water spots on furniture, corroded battery terminals, fire extinguisher, ant repellant, nail holes in a wall. Only a few of the reasons I hereby nominate Baking Soda as the “Duct Tape of Home Hygiene”.
The heroku-accounts plugin makes it a lot easier to have multiple heroku accounts (work, personal, consulting, etc) on the same machine… this quick how-to guide assumes your pre-existing heroku account will be heroku.work and you are adding a new account heroku.personal.
If you’re using RSpec and FactoryGirl to automate testing for your Rails app, you probably know that when creating a factory for a model that has association you can simply specify the factory of the associated model. For example, suppose your Contact model has associations with Phone and Store models:
Although we are running Lion on all our dev machines, we had an issue where a project using RMagick suddenly stopped working in dev mode, giving the error
Incompatible library version: RMagick2.bundle requires version 10.0.0 or later, but libltdl.7.dylib provides version 9.0.0