quicksilver/Quicksilver — pull request #1207 by pjrobertson (2012-11-13 11:03:09+00:00)
Title: Don't attempt to re-format existing command objects. Fixes #555. Fixes #722

Who'd have thought it would be such an easy fix.

I'm not sure why we were attempting to re-creating an existing QSCommand object (in QSHistoryController.m:L49) and doing so incorrectly!

Looks like afb1023c6904b52197a9f4afed9936a3ee4fd566 added the `objectValue` method (not sure what it does, @tiennou ?)
and … good old Code Cleanup 2b08e42b6562ebc68b2ae2a84739d1114234db0d is as far back as I can go for QSHistoryController.m, but looks like that didn't actually change anything.

A few other tidy ups:

* Don't know why`(id)` was used in QSHistoryController for `- (void)addCommand:(QSCommand *)command`. It's always a `QSCommand` so I've changed this
* If the 'last command' proxy was run, there's no point adding this command (or it's resolved command) to the catalog, the 'last command' will always be the 'last command' until a different command is run. Confusing? ;-)