Instead of checking specifically that it’s in the TODO state, check that it’s in
any one of the first states (like TODO, or READ). If this is the case, switch it
from the current state to whatever the settings define as being the next
state (usually WIP or READING).
A lot of the time when capturing some task my cursor is at a random location and
it doesn’t actually mean what I’m looking at is at all related to what I’m
writing.
I think this will make me occasionally miss certain connections, but usually
will provide less noise.
Instead of using ‘auto-fill-mode’, start using ‘org-indent-mode’ and
‘visual-line-mode’. It looks the same, but without using any newlines and
indentation. It works well if combined with other tools like Orgzly which don’t
do any kind of indentation on their own.
The value of the variable ‘org-agenda-todo-ignore-scheduled’ causes it to ignore
any scheduled items that aren’t scheduled for today or in the past,
‘org-agenda-tags-todo-honor-ignore-options’ makes the value of
‘org-agenda-todo-ignore-scheduled’ also apply to tag searches. Since I’ve
replaced my global todo list with a tag search, this is preferable.
I’m using the date as a kind-of header, calling ‘fill-paragraph’ doesn’t
understand that the date isn’t part of the paragraph. It also looks a little
cleaner in my opinion.
If there are 2 files name "Program.cs" open, for example, the simple
‘(get-buffer "Program.cs")’ won’t work. ‘find-file-noselect’ can work if we pass
in the full file path using the ‘%F’ format placeholder.
The dependencies are also in the package files themselves and are the actual
source of truth. The way I’ve reorganized the stages should mean that this isn’t
necessary anymore.
It's always bothered me that a description list in org-mode might be
indented quite a bit if the terms aren't long enough. With this change
they'll always indent the same way, using 5 spaces.
In order to support my tablet which seems to have a lower maximum integer
value (I guess it’s 32-bit? I’m surprised) and can’t handle the version numbers
I was using before. It would turn them into floating point numbers, which adds a
~.0~, this made it impossible to install any package.
Any installations I have will need to reinstall all their oni packages so that
the new version number is picked up, since the new version number will be lower
than the old one.
