Beware “DONE” shifts on repeating events In orgmode you have several ways to make a repeating event. One of the ways is to simply incude an active date under a headline, and include a repeating directive in it like so: <2023-09-18 Mon 12:30-13:30 +1w> This is fine, for example, when noting someone’s class schedule (not my own where I would need notes for each individual class). * TODO Bill's Schedule this semester <2023-09-18 Mon 12:30-13:30 +1w> <2023-09-19 Tue 11:00-16:00 +1w> <2023-09-20 Wed 12:30-13:30 +1w> <2023-09-21 Thu 11:00-15:00 +1w> <2023-09-22 Fri 11:00-16:00 +1w> However, if you ever make these under a TODO item, and then mark it “DONE,” be aware that it shifts the times of every one of these entries by the +1w, not just the one for today that you probably meant.

Asked at https://www.reddit.com/r/emacs/comments/159zj0v/comment/jtodsl9/?utm_source=share&utm_medium=web2x&context=3 My tangle includes writing a bin script, which needs 700 permissions. However, the following doesn’t seem to work; it produces a file with 644 permissons, which cannot be executed. I am trying to follow https://orgmode.org/manual/Extracting-Source-Code.html . What is wrong? #+BEGIN_SRC bash :tangle ~/.local/bin/tsa-ss :tangle-mode o700 Answer: don’t use the shortcut syntax The following worked. I’m not sure why the original did not, though. #+BEGIN_SRC bash :tangle ~/.local/bin/tsa-ss :tangle-mode (identity #o700)

The problem: rebulding packages This was discussed in an issue on straight1 With the notorious orgmode updates and breakages, combined with the amount that I depend upon orgmode, I am trying to just stick with the built in version and not ever build it. As such, my Straight orgmode invocation looks like this: (use-package org :straight (:type built-in) Nonetheless, some packages seem to cause org to “build” and use a straight version.

Org-files are great and have some great features, but there are advantages to micro-files, too Discussion on reddit at https://www.reddit.com/r/emacs/comments/13khozp/orgmode_megafiles_or_many_individual_files/ I am beginning to think that this question is more than just taste; there are actual technical consequences here. The question is, should I switch my journal, blog, and/or note-taking method away from big master files with lots of entries to individual files per entry? I am in the process of switching my passwords from a big GPG-encrypted org-file to using the linux password facility1, and I have just discovered denote2, which likewise leverages the system naming/file-searching facilities to organize a knowledge-base in an emacs-agnostic manner.

embark-org.el file missing This issue is a repeat1 of an old, closed one. because I cannot re-open that issue. I have tried the fixes mentioned there and more, but to no avail. What’s wrong when straight builds the embark package, it omits the embark-org.el file which is present in its embark repository directory. This results in blocking errors as I have things that depend upon functions from embark-org. Directions to reproduce (use-package embark)

Intro My encrypted orgmode file in which I store my sensitive information suddenly could be opened, but not edited. When I attempted to save I received: gpg: D664BA060CCB9D32: skipped: Unusable public key gpg: [stdin]: encryption failed: Unusable public key A search online indicated that it was probably due to my gpg keys expiring. With a quick update to the process in 2022 and a belief in the value of limited duplication, here is the winning strategy:

Problem: I need just one literal underscore in my org-exported blog post I export orgmode to my blogs. However, when I have an underscore (like in a section header) it is interpreted as putting the next thing in a subscript. There are plenty of answers out there for disabling this globaly or for the whole file, but I WANT subscripts sometimes. How do I tell it to leave just a particular _ alone when I export?

Updated: [2021-12-09 Thu] comment clarifying “macros” Intro Time to make a new daily event for the next 90 days, but it shouldn’t have weekends. Most of these steps become muscle memory after getting used to emacs macro power in orgmode files, sql dumps, dired find-and-replace, text formatting, YAML/XML/HTML/JSON/EDN tailoring, etc. It’s the speed and flexibility of this method that shines, allowing for solutions to very specific problems, or just nice custom orgmode agenda entries in this case.

Problem As laid out on reddit1, I arrange my orgmode notes as single files with lots of entries. This works great for me because emacs is more buffer-oriented than directory-oriented, so all the emacs search commands optimize for single-file approaches (eg search all headlines in my tech/blog file for the keyword of that Linux function I’ve forgotten how to use). The single problem I have is footnotes. From the documentation you have two options: inline or in a file-wide section.

For years my workflow has centered in org-agenda and I would go from one clocked item to the next. For instance, I would be clocked into my “Emails” task, which never closes, and then eventually move down in the agenda to “Task B”. Then I hit C-x TAB to clock in. It correctly queries for a comment on the task I’m leaving but no longer clocks me in to the new task as I’d asked.