You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I define more priorities then just "highest", "lowest" and "default", then the "intermediate" priority is not recognized as priority when changing an existing priority and a new one is added to the headline.
Steps to reproduce
Define more sophisticated priorities in config, like:
* test: implement test to expose the bug
* test: add more cases in priority_state_spec
* refactor: make priority_state independent of config
To prepare the fix, we need to avoid a dependency cycle between config
and priority_state, because we will need priority_state in config to
implement the fix.
We inject the needed values, whereever an instance of PriorityState is
created.
* fix: generate missing intermediate priorities
A headline priority gets only detected correctly, if it is part of the
table returned by Config:get_priorities(). While it previously only
returned the priorities explicitly defined by the user, it now uses
PriorityState to generate also intermediate ones. This happens, if the
highest and the lowest priority define a range of more than three
priorities.
* docs: mention new highlight groups
Add new highlight groups to "Colors" chapter.
---------
Co-authored-by: Sebastian Flügge <seflue@users.noreply.github.com>
* test: implement test to expose the bug
* test: add more cases in priority_state_spec
* refactor: make priority_state independent of config
To prepare the fix, we need to avoid a dependency cycle between config
and priority_state, because we will need priority_state in config to
implement the fix.
We inject the needed values, whereever an instance of PriorityState is
created.
* fix: generate missing intermediate priorities
A headline priority gets only detected correctly, if it is part of the
table returned by Config:get_priorities(). While it previously only
returned the priorities explicitly defined by the user, it now uses
PriorityState to generate also intermediate ones. This happens, if the
highest and the lowest priority define a range of more than three
priorities.
* docs: mention new highlight groups
Add new highlight groups to "Colors" chapter.
---------
Co-authored-by: Sebastian Flügge <seflue@users.noreply.github.com>
Describe the bug
When I define more priorities then just "highest", "lowest" and "default", then the "intermediate" priority is not recognized as priority when changing an existing priority and a new one is added to the headline.
Steps to reproduce
Expected behavior
The headline priority should change from [#E] over [#D], [#C], [#B] to [#A] and then nothing again.
Emacs functionality
Bug doesn't exist in Emacs org mode. Priorities are explained here.
Minimal init.lua
...
Screenshots and recordings
No response
OS / Distro
Linux, as always
Neovim version/commit
0.10
Additional context
I already fixed the bug, PR is in the making.
The text was updated successfully, but these errors were encountered: