Recent Changes

2022-04-17

• 05:09 UTC (new) (history) 2022-04-17 Easter 2022 . . . . mbork – Another difficult time – not only because of COVID-19 (which hopefully seems to finally retreat), but now also war in Ukraine. I honestly cannot imagine what Ukrainian people live through. Though I also think about Russians – often, when someone hurts other people, the aggressor ends up suffering, too… Still, the Good News about Christ living yesterday, and to day, and for ever means that all suffering, however terrible, will come to an end. I pray for all the people suffering because of various reasons – which in fact means all people – and I hope to meet you all in Heaven some day. And even amidst all the suffering and pain we have this one reason for joy greater than all our troubles. Christ lives!

2022-04-11

• 05:38 UTC (new) (history) 2022-04-11 pgrep, or what I do when Vagrant hangs . . . . mbork – I use Virtualbox (via Vagrant) pretty extensively. Unfortunately, sometimes it just hangs. (Two cases when it tends to happen is when I put my laptop to sleep with the VM on or when I try to run too many things on the VM. Not every time, but often enough to be a nuisance – say, maybe once a month. And given that I regularly have uptime on the order of weeks – Emacs uptime, not computer uptime, mind you;-), though in my case it is usually almost the same), I don’t want to reboot the system. Unfortunately, in such situations even vagrant halt --force doesn’t help.
• 05:37 UTC (diff) (history) Comments on 2022-04-04 Warning about trying to setq a non-existent variable . . . . mbork – Well, a function would require me to quote the variable name (unlike {{{setq}}} and unlike my macro).

2022-04-04

• 17:28 UTC (new) (history) 2022-04-04 Warning about trying to setq a non-existent variable . . . . mbork – Some time ago I wrote about how I changed a value of one of Emacs’ internal variables to get the behavior I needed. As I mentioned, I submitted a bug report (apparently, I’m in a minority needing this, and I don’t expect it to be fixed in near future – but that doesn’t bother me much, since I have the workaround in place anyway). There is one thing that does bother me, though. If this bug gets solved at some point in time, and the variable js--declaration-keyword-re disappears (and some other one – without the two dashes – is created in its place), how do I know that?

2022-03-26

• 12:29 UTC (new) (history) 2022-03-26 A nice use-case for pee . . . . mbork – Well, sorry for the click-bait-ish title;-)… Of course I meant this pee. It is similar to tee in that it can “split” the input stream, but while tee directs it to a few files (by default to stdout and to the given ones), pee directs it to pipes. You can give it names of commands and it will run them in succession and feed every one of them its input. (Unlike tee, it doesn’t put it to stdout, so you need an explicit cat to achieve that.) Here is a nice use-case.

More...