In reply to @inkbottle:matrix.org
What I should do about it is unclear: I like to follow guidelines and I'm not much for made up tweaks in the wild.

I simply have the following in my ~/.mailcap

text/html; qutebrowser-call.sh %s
text/*; xdg-open "%s"
application/*; xdg-open "%s"
video/*; xdg-open "%s"
image/*; xdg-open "%s"

In reply to @inkbottle:matrix.org
Thanks, I might just follow your lead

I want to try org-habit but am put off by the fact that I need state logging for DONE to make the little chart thingies… ☹️

Btw, for my habits I always include this:

:LOGGING:  DEFER(!) DONE(!) CANCELED(!)

So that it does the logging, but doesn't ask for a note to go along with it.

In reply to @jwwiegley:matrix.org

Btw, for my habits I always include this:

:LOGGING:  DEFER(!) DONE(!) CANCELED(!)

So that it does the logging, but doesn't ask for a note to go along with it.

In reply to @jwwiegley:matrix.org
It’s a property of the habit.

What is a good way to delete a bunch of element types from an Org buffer? Assuming that element-types-to-delete looks like this: (property-drawer src-block ...), I'm doing the following:

(let (parse-overlays)
  (org-element-map (org-element-parse-buffer 'element nil t) element-types-to-delete
    (lambda (node)
      (let ((ov (make-overlay (org-element-begin node)
                              (org-element-end node))))
        (overlay-put ov 'evaporate t)
        (push ov parse-overlays))))
  (dolist (ov parse-overlays)
    (delete-region (overlay-start ov)
                   (overlay-end ov))))

But it's causing Emacs to hitch and generates a lot of garbage. I can use markers instead of overlays but that doesn't help much. I have to use some kind of persistent marking and a two step (mark/delete) process since otherwise the parse-tree will be invalid once I delete the first encountered element.

element-types-to-delete can have any subset of elements from org-element-all-elements.