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.
Any item could be of interest, not only those that are valid refile
targets.
This might be slow. May we should not be using the refile mechanism to
jump to any item?
Items tagged with HOLD should be ignored in normal processes and should
thus not appear as backlinks. Items tagged WAIT are supposed to appear,
though, and are not excluded from the list of relevant backlinks.
In the previous implementation, when in some buffer which is not an Org
buffer that accidentally contains lines that partially match the regular
expression describing an Org heading, errors could occur when the Org
refile cache was empty. To address this issue, let's temporarily switch
to some Org buffer before generating the list of all Org heading
targets.
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.
Daniel -