For saving project todos/notes/changelogs in a central
{org-directory}/projects.org file, under {Project
Name}/{Tasks,Notes,Changelog} headings.
If you want to prefix the outline path, you can specific a :parents
property. e.g.
(after! org-capture
(org-capture-put :parents '("Projects")))
or
(dolist (key '("ot" "on" "oc"))
(setf (alist-get key org-capture-templates)
(append (alist-get key org-capture-templates)
'(:parents ("Projects")))))
Also sets :kill-buffer t by default, for all org capture templates.
Keybinds that correct behavior or provide or extend vim functionality
were moved to their respective modules, or to the :editor evil module.
Keybinds in the global space, that are particularly opinionated but
potentially harmful or imposing as a default, or likely for users to
change (like leader keys), are kept in config/default.
Now, inline evaluation will display results in an overlay next to the
cursor, rather than in the minibuffer (unless it gets too big, in which
case it'll use a popup buffer).
- Fixes an issue where evil bindings weren't working in org-mode
- Significantly slims down on unnecessary keybinds
- Remove +org-init-keybinds-for-evil-h hook and reli more on our new
evil-org fork, which has upstreamed some of our changes.
- Documents undocumented functions, remove unnused ones, and reorganize
org's autoload libraries by convention.
- Adds org-fancy-priorities for more elegant (and subtle) priority
display than ugly [#A] tags.
Half-reverts 29f6db6ea. Hadn't realized this setting would remove
the *entire* logbook if you clock out with sub 1m on a task.
Mentioned by @d1egoaz in 29f6db6
Also consolidates all REPLs (opened through the :tools eval module)
under one popup rule, which inhibits ESC from prematurely closing
them (#1944), and cleans up after their buffers *only* if their handlers
weren't specified to :persist, e.g.
(set-repl-handler! 'some-mode #'some-repl-handler :persist t)
Also standardized ESS's REPL commands.
If plantuml-default-exec-mode is 'server, the image is compiled via the
website and downloaded. If it's 'executable it uses the local 'plantuml'
executable (determined by plantuml-executable-path) to compile it. If
it's 'jar it uses the local 'plantuml.jar' (determined by
plantuml-jar-path).
The first two were tested and work, but 'jar did not, until now.
