One would think this situation would be better documented by vendors, instead of relying on obscure incantations. But one would probably be told by Customer Services that this defect is not covered by warranty (if you still have it) and you're out of luck.
I never understood why advertisers insist on giving me "relevant" ads. I find it better if the ads are diverse and all over the place, as I discover new things. The "relevant" ads are usually about stuff I just bought, so useless to me.
I find this site insightful in terms of discovering new things. It could be made into some sort of tumbler for ads. :)
I use "Should I Answer?" for this purpose. I don't have to give them my data in order to know who's calling me most of the time. It could block calls, but I don't use that feature.
How does your setup work with a second monitor that comes and goes?
Use case: I have a laptop that I take everywhere for me, but I plug into a second monitor while at work. I also use multiple desktops, and this pattern is sometimes causing windows to jump to another desktop when disconnecting the monitor.
I'm nitpicking, but is there a reason why you use the numeric signal number in Linux? On my machine "kill -SIGSTOP" works as expected, and I don't remember a time when you couldn't use signal names like that.
I had the ideas used in this project in my head, but I've been putting off the work forever now.
I LOVE YOU FOREVER for using transactions as the central operation rather than double entry accounting, and I love you even more for adding the ability to tag transactions. I can not put off work for a web interface instead, which is a lot less work to put off :)
I haven't tried it yet, but it's now high on my list for when I get home from work.
But it can also be used for evil: cancel a valid stop that someone commanded and hope they don't notice.