Previously, links which end in a closing brackets got a non-breaking
space appended via a separate advice to `org-link-make-string`.
However, this did not work well with the other advice that removes
statistics cookies from links, mostly because I messed up the order in
which the advices were applied. To remedy this, the advice to remove
statistics cookies now also adds a non-breaking spaces as described
above.
When a headline ends on a closing bracket, Org adds an escape character
to the link text to distinguish the end of the link from the link
description. This escape character is a zero-width space, which is
counted for Org table alignment as one character, but the link itself is
displayed shorter, because the zero-width character is displayed as a
single pixel by emacs.
To work around this issue until the upstream fix is released, let's add
a final non-breaking space to those link descriptions to avoid the need
for the zero-width escape characters.
I found that opening this output on the right side to be annoying, so
let's switch try the bottom side window instead. This also works with
having an eshell buffer open at the same time, resulting in a nice reuse
of the right space of eshell windows that is usually empty.
With vertico, using the default `yank-pop` is nice enough. Furthermore,
yanking with helm does not update the current candidate selection when
in a minibuffer prompt (like for `find-file` or `org-insert-link`),
sometimes leading to confusion.
With `common-lisp-indent-function`, the indentation of `while` was not
correct – oops.
This change will break some current indentations, though. Stay tuned.
This is to have this extra blank line after refiling.
This reintroduces 76c8717, and reverts f064bf9 and 8ed64b7. The issue
with too many blank lines at some items may reappear.
I access bookmarks far more often than the list of local important
files, so let's skip the usual `C-o` hazzle and have bookmarks right
under point when available.
This is more reasonable than inserting a link to the current location of
point, which can be quite arbitrary (at least in my workflow). When a
link to the item at point is needed, it should be inserted manually.
This change is experimental and might be reverted.
Idea: we don't want to see those items until the deadline warning date
is due anyway. Drawback: those items are not shown even when jumping to
the specific date (or past it), so planning ahread get's a bit more
complicated.
Those cookies are correct when the link is inserted, but subsequently
gets updated (usually to `[0/0]`) when the statistics cookie is updated
in the Org item where the link is placed — removing any meaning from
this cookie. It's thus better to not have it at all, I think.
`org-capture-fill-template` unconditionally adds a final newline to each
template. This caused extra empty lines with the old templates when
nothing is inserted at point (`%?`), because in this case empty lines
before and after point were present, with nothing in between.
Those extra empty lines are gone now, and point is positioned after the
final non-blank character. When extra empty lines are needed, they have
to be inserted manually.
This is to better be able to identify those empty lines and keep the
notes tidy.
The new value for org-cycle-separator-lines` is the current default
value.
Inspired by the `use-package` documentation, but the other places where
`add-hook` is called this simplification does not seem to be appropriate
from my point of view (missing `-hook` suffix, better readability when
calling `add-hook` directly).
This seems to be slow, causing proced to take more time updating a
buffer than waiting the one second until the next update – resulting in
an unresponsive proced buffer.
Note: I am not sure whether this setting is correct, as `(not
on-windows)` will not be evaluated when `use-package` calls
`custom-theme-set-variables`. However, I think it will be evaluated
eventually, and that should be all that's needed.
It's nice to be able to collapse plain lists easily, as I have some
quite large ones. The comment advises to be careful with certain
situations yields strange results, though, which is why this setting is
deemed experimental for the time being.
Using orderless by default get's in the way of “usual” code completion
and shell completion, where prefix completion is the expected
behavior (for me). So let's try to use basic completion first, and try
to rely on orderless completion to kick in as soon as spaces are
involved (which should not happen for shell and code completion).
The completion colors should also help to see whether we are still using
basic completion or orderless completion. Let's try this for now.
Since `counsel-switch-buffer` has been replaced by the plain
`switch-to-buffer`, recently used files are not shown there anymore, so
let's make `recentf` easier to access.
NB: `consult` also provides a function akin to `counsel-switch-buffer`,
so maybe this keybinding will not be that relevant anymore in the
future.
Using ivy for completing in regions somehow has problems in eshell, so
let's not do it. The main use-case for using ivy in region completion
is for ledger, so maybe it can only be activated there?
This mostly reverts commit 615b285f74.
The default completion style is now to use orderless by default, but
certain categories can benefit from additional completions (e.g., file
and partial-completion).
It's quite hard to determine the appropriate completion categories,
though. Does Org have a dedicated one?
The reason is that while filtering Org headlines, sometimes one of the
other completion styles matches, hiding other possible matches that
would have been found by the `orderless` style. This can happen when
spaces are included in Org headlines (which is usually the case) and
those spaces match the search pattern. In this case, the position of
point is also relevant, which is not something I want.
It would be better to know which completion category is use in this case
and override the completion style for this only, but so far I haven't
found it. Continue looking …
This may change back in the future.
The ivy configuration is kept on purpose, in particular because some
counsel functions are still in use. Maybe those can be also be replaced
later on, maybe with helm functions? Not quite sure whether this is a
good idea, though.
This is mostly to speed up agenda generation, in particular the main
agenda view. It turns out that filtering out SCHEDULED items is
expensive, but in tags views there is no variable to exclude scheduled
items – as for todo and tags-todo views. Thus, SCHEDULED items must be
removed with a corresponding search pattern, which is slow.
`hydra-org-clock` thus only hosts keybindings for clock-related
commands, while the new `hydra-org-jump` is for jumping to Org items in
various ways. Feels cleaner to me this way.
This is an experimental setting to increase usage of completion
functionaly in my workflow. It's not clear yet whether I will find this
disturbing, though.
No need to conditionally enable it in main initialization function when
it can be done directly directly after loading `org-roam`. This keeps
the configuration of the package local, i.e. syntactically together.
It's annoying that `org-agenda-redo-all` always jumps back to today, so let's
try to avoid this by not having it bound anymore. I am usually completely
satisfied with `org-agenda-redo` anyway.
This never worked anyway, I would probably have had to define the source
globally for adaptive sorting to work, or something like that. However, I am
usually happying with the interactive narrowing of the candidates, so let's get
rid of adaptive sorting for now.
Get rid of some helm sources I usually don't use, to speed up function
execution. Indeed, on Windows 11, if this function takes too long, the Emacs
frame will loose its focus, which is super annoying!
`org-return-indent` is obsolete since 9.4, one should use `org-return` with
`indent` set to `t` instead – and I am not sure whether it will work if I rebind
`org-return` to some interactive lambda form. So let's try to not indentent
automatically anymore, maybe this is good enough?
This is instead of repeating the path again and again in the code. It's cleaner
this way, also easier to spot mistakes (see the now fixed definition for
`abbrev-file-name' …).
