Of course you are a command-line guru like me, but once in a while it’s just so much easier to use Midnight Commander. Especially when renaming files or directories, where you can just edit the name windows-style. Well, if your shift key works like it should that is.
I couldn’t bare that it wasn’t, so I did some digging and found out that os x term sends the wrong codes. I found this solution on superuser, but what to do with the other shift keys? I also found this article that looks outdated, but is still pretty cool. I ended up mapping F13 to shift F1, F14 to shift F2, etc. using the X11R6 xterm codes. That’s because in this bug report somebody said that SHIFT F6 should output ^[[17;2~ so that matches the xterm codes.
Eventually I mapped all my SHIFT F-keys (which I don’t use much anyways) like this.
Although we kind of regret we purchased this printer when we switched to MacBook’s, here’s one thing I seem to have ‘solved’. We received an invoice in PDF that could not be printed to our HP printer. We also tried our old HP Laserjet 1320, and a collegue also tried at home. All it printed was garbage high ascii stuff.
I figured it must we a problem with PCL drivers and HP. Maybe a problem of CUPS, or bad os x drivers, who knows?
Then we received a PDF from our Chamber of Commerce, and it said it was digitally signed. So then I realised it could also be a problem with this signature.
I installed Adobe Reader to open the PDF instead of the default Preview app that was already installed. Now I was able to print the Chamber of Commerce document just fine.
So now only the problem of really really slow job processing (or no processing at all) remains. Usually this can be fixed with turning the printer off and on again, but for a device that costs a few hundred euro’s this isn’t what we expected.