Lewis Russell ee41153a94 feat(diagnostic): revert default behaviour of goto_next/prev() ...

Follow-up to #28490

Problem:

The new behaviour of goto_next/prev() of navigating to the next highest
severity doesn't work well when diagnostic providers have different
interpretations of severities. E.g. the user may be blocked from
navigating to a useful LSP warning, due to some linter error.

Solution:

The behaviour of next highest severity is now a hidden option
`_highest = true`. We can revisit how to integrate this behaviour
during the 0.11 cycle.

2024-04-30 13:39:27 +01:00

..

nvim

fix(healthcheck): expand vimrc variable (#28379)

2024-04-17 14:31:13 +08:00

provider

fix(checkhealth): error in node.js check #28348

2024-04-15 09:23:22 -07:00

vim

feat(diagnostic): revert default behaviour of goto_next/prev()

2024-04-30 13:39:27 +01:00

_vim9script.lua

refactor(lua): rename tbl_islist => islist

2024-04-21 17:08:07 +02:00

coxpcall.lua

build(lua): vendor coxpcall

2023-09-10 11:43:37 +02:00

editorconfig.lua

fix(editorconfig): syntax error regression

2024-03-11 10:06:57 +00:00

man.lua

fix(man.vim): q quits after jump to different tag in MANPAGER modified (#28495)

2024-04-26 13:14:45 -05:00

tohtml.lua

feat(lua): deprecate vim.tbl_add_reverse_lookup

2024-03-07 10:24:34 +01:00