Recent Changes

Updates since 2019-04-21 19:47 UTC

1 | 3 | 7 | 30 | 90 days
List all changes Include rollbacks Include minor changes
List later changes RSS RSS with pages RSS with pages and diff





  • 17:04 UTC (new) (history) 2019-08-05 datefudge and agenda testing . . . . Marcin Borkowski Some time ago, a question was asked on the Org-mode mailing list about a specific kind of task in Org agenda. This made me think about debugging one’s agenda settings. I’ve already written about batch agenda, but one problem with agenda testing is that it is inherently stateful, in one of the worst ways – it depends on the notion of now. Debugging time-related stuff is hard. (Well, time-related stuff is hard, after all.) It would be great if you could just manipulate Emacs into thinking that the time is some day in the future (or in the past)… Well, actually, it can be done – and it’s easier than I thought.


  • 18:29 UTC (new) (history) 2019-07-29 Git commands as separate executable files . . . . Marcin Borkowski Today we are going to talk about git commands and how they are implemented. Don’t worry, I won’t get too technical – if only I have not studied Git sources (I do not speak C well enough for that anyway). It is enough for us to read the manpage of the git command itself (which I did, along with some experimentation).


  • 18:43 UTC (new) (history) 2019-07-22 Increasing timeout in nginx . . . . Marcin Borkowski Today’s is a short follow-up to the post about debugging Node.js programs in a Vagrant virtual machine. It turns out that it lacked one important piece. It’s all and good in an artificial environment of an isolated script – but when we debug a real Node.js application, the server will timeout while we are slowly stepping through code.


  • 18:31 UTC (new) (history) 2019-07-15 Batch Org agenda . . . . Marcin Borkowski Org-mode agenda is a notoriously complex system. It is really great from a user’s perspective, but a nightmare for a programmer wanting to tap into its generation. A long time ago I have had an idea for a productivity tool which would compute my “agenda score” (for lack of a better name), where each task not yet done would contribute to a total of some kind of “penalty” points – and more of them depending on how long the task is overdue. However, I am probably too stupid to be able to understand what is going on under the hood of org-agenda, and I started to look for better ways. There do exist some tools which might help with that – org-super-agenda being one of them, but there are probably others. Still, I felt this is not the best way. I decided to drop my idea (at least until I have more time and motivation to get back to it). After some time, however, I came back to org-agenda, this time from another direction.




  • 04:56 UTC (new) (history) 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. 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.


  • 18:21 UTC (new) (history) 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.


  • 16:09 UTC (new) (history) 2019-06-09 Defining custom TikZ fill patterns . . . . Marcin Borkowski Some time ago I had a need to define my own filling pattern in TikZ. It turned out to be quite simple, although I had to learn a few things. While the manual (as usual) does a pretty good job at teaching that, I felt that the explanation was a bit too short in one place, and hence this blog post.





  • 16:37 UTC (new) (history) 2019-05-20 Converting BibTeX files to AMSrefs . . . . Marcin Borkowski It’s been a long time since I’ve written anything TeX-related here. But I’m still working with LaTeX (though less often than I used to), and here is a problem I encountered a few days ago – and a solution. I received a file with BibTeX-encoded bibliography. Obviously, I wanted to convert it to AMSrefs. Being lazy, I started to search for an automated solution – and I was not disappointed at all! It turns out that AMSrefs itself has a feature I needed.


  • 06:27 UTC (new) (history) 2019-05-11 Toggling modeline clock display . . . . Marcin Borkowski As I mentioned a lot of times, I use Org-mode clocking all the time. Among others, I integrated it with two external services, I have a few dedicated keybindings to it in my Org-mode hydra. It’s no wonder that I work hard to make clocking as smooth as possible.


  • 04:15 UTC (new) (history) 2019-05-05 A few Magit tips . . . . Marcin Borkowski A month ago I wrote about merging in Git without actually comitting the changes, and mentioned that you probably can’t do that from within Magit. It turned out that I was wrong – in fact, Magit can do it. More recently, I wrote about another Git tip, which is staging an empty file. Then, Nicolas Petton asked whether it’s possible in Magit, and lo and behold – it is, in a quite intuitive (and documented in the docstring) way I just didn’t think about.


  • 18:34 UTC (new) (history) 2019-04-29 Multiple timestamps in one Org headline . . . . Marcin Borkowski Some time ago I learned that you can put multiple timestamps under one Org-mode headline, and that it is then displayed in multiple places in the agenda. This can actually be quite useful for things happening more than one time, but when repeating timestamps somehow don’t fit (for instance, things happen irregularly or a finite number of times).