With current hacks involving `org-agenda-files`, one cannot use org agenda
commands like clock in or change the entry's state to done, etc.
Specifically, the mangled behavior observed at #4901. This commit fixes those
problems around `org-agenda` buffer specific commands.
For more details, please refer to https://github.com/hlissner/doom-emacs/issues/4759#issuecomment-822100632.
Due to case shenanigans, ob-C.el's feature name is ob-C, not ob-c,
preventing folks from using 'c' (lowercase) as a language name for org
babel blocks.
This fixes a class of issues where doom-first-file-hook would fire even
for files not opened interactively (e.g. via org-agenda reading agenda
files or helpful scraping definitions from source files).
In instances like these, hooks like find-file-hook or pre-command-hook
are set to nil to speed up this process and reduce noise, but many
packages add to these hooks when they are loaded; these are lost when
their lexical values fall out of scope, leading to odd errors (like the
one in #4759).
Fixes#4759 (again)
First brought up in hlissner/doom-emacs@9f08db8
When a capture target didn't have an *.org file extension OR its buffer
was displayed before it was renamed to CAPTURE-* (e.g. while a capture
template prompts for input) the popup handler fails to capture the new
window, displaying it in other-window, rather than a popup.
An optimization that minimizes how much work is done when grabbing org
agenda files in the background prevented side-effects in
doom-first-file-hook. This had the indirect effect of preventing
save-place-mode from adding its hook to find-file-hook IF org-agenda was
the first thing you ran at startup.
* Add org-agenda-priority keybindings to org config
Summary: This diff adds evil-esque keybindings for the org-agenda-priority
functions. These functions allow the org subtree priority to be set from
the agenda view.
* Correct org priority keybinds
These keys were meant to be on <localleader> p, but were mistakenly
bound on <localleader> s p.
Also mirrors these keybinds to org-agenda-mode-map.
* Use non-agenda org-priority commands
Also make casing in which-key labels more consistent.
Co-authored-by: Henrik Lissner <accounts@v0.io>
Refactors advice to disable ob-async when exporting org documents or
when the :session parameter is present (ob-async does not support it).
Execution is degraded to synchronous execution and a warning logged.
I understand that what you tried to accomplish via CSright was; however, it doesn't make any difference from Cright, and so for other navigation keys -- h,j,k,l.
I fixed this discrepancy.
+ Adds LOOP and IDEA to primary todo keywords.
+ Adds OKAY, YES, and NO sequence.
+ Specially fontifies NO and KILL with special "cancelled" face to
indicate an aborted/rejected task.
+ Specially fontifies PROJ to set it apart.
WIP:
- Add fixme for evil-org remaps
Misc changes:
- Remove notmuch-search binding
(Unmap the bare "s" keymap from notmuch)
- Remap [] evil-org bindings to ()
- Fix org-capture not finalizing with C-c
- Remap evilem-map
- Add more triggers to minibuffer rotations
- Unmap C-c and C-r from evil-org
Meta:
- Specify bepo layout in maintainer status
- Add basic troubleshooting
In the remapping functions:
- Add operator maps
- Remap C- and M- bindings in normal mode
Respect evil-org-movement-bindings:
This allow non-qwerty users to keep the correct bindings. The additional
let-binding is done to force evaluation of the concatenations and avoid
`void-variable concat` when the map! gets evaluated
Avoid double rotation on magit maps
- Reorder properly magit-mode-map like done on notmuch
(evil-collection PR#428)
The use case: if a user has their org directory stored in a synced
location (e.g. dropbox), this file is the same on all machines and is
almost always conflicted.
This change enables users to override this in the :init section of their
config (or otherwise before org loading) and that the
+org-init-org-directory-h hook will detect an override.
A doom-load-theme-hook hook fixes the background of latex previews, but
by the time org is loaded, this hook will have long since triggered,
giving it no change to update its background, so we must run it at least
once, immediately.
