Recent Changes

2019-07-08

• 21:02 UTC (new) 2019-07-08 Pausing an Emacs keyboard macro . . . . Marcin Borkowski – As I promised last week, I’d like to describe something I probably knew a long time ago, but completely forgot about. You can pause an Emacs keyboard macro during its execution. But wait, there’s more!

2019-07-01

• 18:31 UTC (new) 2019-07-01 Syntax-aware navigation, keyboard macros, sleeping Emacs and interactive functions . . . . Marcin Borkowski – A few days ago I had an interesting Emacs-related problem. I wanted to record and use a keyboard macro which would find a certain TeX one-parameter macro (say, \todo) and comment it out. The tricky part was that it was not at all guaranteed that this macro would be on a line on its own, so “finding the string \todo, going to the beginning of the line and inserting a percent character” won’t work.

2019-06-24

• 04:56 UTC (new) 2019-06-24 org-agenda-todo-ignore-timestamp vs org-agenda-todo-ignore-with-date . . . . Marcin Borkowski – Org Agenda is a legendary feature. One of its selling points is customizability (as is usual in Emacs in general). This, however, comes at a price: agenda generating is slow, even though it is reportedly heavily optimized. (At the worst moment, my agenda took about half a minute to generate. A naive benchmark convinced me that the reason was a rather large Org file, weighing almost a megabyte and containing several thousand headlines (a.k.a. capture.org). No surprise, and a good candidate for optimizing (most of its entries do not really need to be even considered for agenda, so those which do can be moved to another file, and this one can be excluded from agenda generation). But today, I’d like to talk about something else – two of the many options governing agenda generation, namely org-agenda-todo-ignore-with-date and org-agenda-todo-ignore-timestamp.

2019-06-15

• 18:21 UTC (new) 2019-06-15 Debugging Node.js programs in a Vagrant virtual machine . . . . Marcin Borkowski – One of the very nice things in a programmer’s toolbox is a debugger. Coming from Emacs, I am accustommed to Edebug, which allows to step through the code, install breakpoints (conditional ones as well as unconditional ones), watch variables etc. Programming in JavaScript is (or at least should be) no different. Indeed, both Firefox and Chromium have a debugger in their DevTools (although Chromium’s one seems a tad more confusing). This is all good when I’m debugging front-end code, but I often work on some backend code in Node.js. Fortunately, it can be debugged, too.

More...