aboutsummaryrefslogtreecommitdiff
path: root/runtime/queries/kdl/highlights.scm
diff options
context:
space:
mode:
authorMichael Davis2023-07-11 00:06:13 +0000
committerBlaž Hrastnik2023-07-31 06:05:38 +0000
commit2d838d729cca26a718e3536e8d75c60396420dbd (patch)
tree53db56db8d4c97a782a3e78395937b3942101ccf /runtime/queries/kdl/highlights.scm
parent86a1f0177ca734e0ce66f4e55c41eda306f1adbb (diff)
Preview the latest value for regular registers
This fixes a discrepancy between regular registers which are used for yanking multiple values (for example via `"ay`) and regular registers that store a history of values (for example `"a*`). Previously, the preview shown in `select_register`'s infobox would show the oldest value in history. It's intuitive and useful to see the most recent value pushed to the history though. We cannot simply switch the preview line from `values.first()` to `values.last()`: that would fix the preview for registers used for history but break the preview for registers used to yank multiple values. We could push to the beginning of the values with `Registers::push` but this is wasteful from a performance perspective. Instead we can have `Registers::read` return an iterator that returns elements in the reverse order and reverse the values in `Register::write`. This effectively means that `push` adds elements to the beginning of the register's values. For the sake of the preview, we can switch to `values.last()` and that is then correct for both usage- styles. This also needs a change to call-sites that read the latest history value to switch from `last` to `first`.
Diffstat (limited to 'runtime/queries/kdl/highlights.scm')
0 files changed, 0 insertions, 0 deletions