Just use another email...
This was a bug, that also happened in SL. It was due to a stale "FirstDetachAll" flag in the UPD "RezMultipleAttachmentsFromInv" message that used to be of use in old days but causes race conditions when re-wearing the same attachments: since the viewer now cares for detaching attachments first, that flag should now always be false... I also improved the algorithm to make it smarter: attachments that are already worn and present in the new outfit are no more detached/reattached. The fix will be part of next release.
There is no "hop" SLURL in the Cool VL Viewer (this was already replied to
in the past), and http map URLs are automatically interpreted as SLURLs in the viewer (if you click on http://maps.secondlife.com/secondlife/S ... xx/yyy/zzz
in chat history, for example, the viewer opens a landmark info floater which gives access to the world map as well... To get the URL, right click on the landmark in your inventory, choose "Show on map", then when the map is shown, click the "Copy SLURL to clipboard" button. I might improve this in the future, but it's low priority stuff, really...
Just double-click on the object entry in the list to get a beacon pointing to that object with the distance...
The "Area search" is not the place for such an info; for a start, not *all* objects get listed in that floater: only rezzed objects are (which depends on your draw distance, on the interest list in SL, and on your camera FOV). The objects count in the land (on a per-parcel basis) is found in the "About land" floater.
For the land impact of an object, you can use the "Inspect" button of the "Area search" floater and from there, the "Object weights" button of the "Inspect" floater.
Querying for the land impact of each object listed in the Area search floater is an extremely costly process (in term of viewer to server messaging, and vice versa) that could be considered excessive/griefing by some grids staff... I do not plan to implement it. Sorting by distance would be possible, although I do not really see much interest in this... Especially since you can use the Tools -> "Pathfinding linksets" floater, which gives you all these pieces of info while not taxing the server as much as UDP messaging with the features you ask for the "Area search" floater would do (pathfinding queries are done via HTTP and in very few, large messages, instead of a gazillion small UDP messages).
Again, there's the beacon to spot the object, and the inspect floater (and once you got the object in view, just use the pie menu to return it).