Wandering Thoughts archives


Why I am irritated with evince

Evince is in general a nice PDF viewer (technically it supports other formats too), much nicer and far less irritating than Adobe Acrobat. (For a start, evince actually quits when I click on the 'close window' button; Adobe Acrobat presumes that I wanted it to clear the current document.)

The problems come in when I tried to do something besides view a document. (Perhaps evince was jealous that I wasn't satisfied with it.)

First, evince silently aborts printing if I have it print a document and then tell it to quit once it seems to have finished. There is no sign that it is still working on the print request and no warnings. This is teeth grindingly irritating, especially because when a print job goes missing my immediate assumption is that something in the print system ate it.

(There are lots of grues in print systems, especially around here.)

Attention interface designers: if the user can't tell when it's safe to quit and when it's not, you've screwed up.

Once I worked this out, I was lucky enough to do a test print run of only a small section of the 500+ page IBM Tivoli Redbook I was trying to print. It was lucky because it turns out that evince defaults to forced non-duplex printing and thus I only wasted 20 pages instead of 500 odd. The sheer twisted genius of this choice is breathtaking; I can think of few defaults that so carefully calculated to surprise and irritate people and to waste reams and reams of paper.

(What evince should do is to not override the printer's default settings for duplexing and the like. I know it does, because I was printing to a destination that defaults to duplexing.)

I'm not even sure I can set evince to default to (forced) duplex printing; I may just have to remember to set the ticky-box in a non-default tab of the print dialog every time I want to print something.

linux/EvinceIrritation written at 23:01:39; Add Comment

An update on impending changes to access to Solaris patches

To update my earlier reporting, here's the current state, again as reported on the pca news page.

The new Sun access restrictions only apply to Solaris 10 (and anything Sun releases later). For Solaris 9 and earlier, Sun isn't making any changes for patch access; anonymous access via pca continues to work. (I was wondering about that, since I have been too busy to get around to getting a Sun Online Account, yet my patch access was still fine.)

Since all of my machines are Solaris 9 (or earlier) and I have no plans of upgrading to Solaris 10, this is ideal for me.

(While Solaris 10 has a fair amount of nice goodies, I have never done a Solaris OS upgrade, I have no idea how hassle-free it is, and the machines are old enough that we need to think about their future in general.)

solaris/PatchAccessChangesII written at 12:19:59; Add Comment

Page tools: See As Normal.
Login: Password:
Atom Syndication: Recent Pages, Recent Comments.

This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.