Merge pull request #25724 from luukvbaal/signmerge

refactor(sign): move legacy signs to extmarks
This commit is contained in:
bfredl
2023-11-18 15:04:14 +01:00
committed by GitHub
33 changed files with 768 additions and 1898 deletions

View File

@@ -317,8 +317,8 @@ function vim.api.nvim_buf_get_commands(buffer, opts) end
--- @return integer[]
function vim.api.nvim_buf_get_extmark_by_id(buffer, ns_id, id, opts) end
--- Gets `extmarks` in "traversal order" from a `charwise` region defined by
--- buffer positions (inclusive, 0-indexed `api-indexing`).
--- Gets `extmarks` (including `signs`) in "traversal order" from a `charwise`
--- region defined by buffer positions (inclusive, 0-indexed `api-indexing`).
--- Region can be given as (row,col) tuples, or valid extmark ids (whose
--- positions define the bounds). 0 and -1 are understood as (0,0) and (-1,-1)
--- respectively, thus the following are equivalent:

View File

@@ -5923,12 +5923,6 @@ vim.go.siso = vim.go.sidescrolloff
--- "number" display signs in the 'number' column. If the number
--- column is not present, then behaves like "auto".
---
--- Note regarding "orphaned signs": with signcolumn numbers higher than
--- 1, deleting lines will also remove the associated signs automatically,
--- in contrast to the default Vim behavior of keeping and grouping them.
--- This is done in order for the signcolumn appearance not appear weird
--- during line deletion.
---
--- @type string
vim.o.signcolumn = "auto"
vim.o.scl = vim.o.signcolumn