2.3.1 (2024-11-28)
- Support multi-byte mappings for aliases. (d66b6a2)
2.3.0 (2024-06-24)
2.2.0 (2024-06-08)
2.1.11 (2024-06-06)
2.1.10 (2024-05-30)
- Default delete should work if
find
key is sane. (#331) (6d2be37) - Don't translate termcodes twice on input (#326) (de828d6)
- Typo in help docs. (fa5b365)
2.1.9 (2024-05-29)
2.1.8 (2024-05-16)
2.1.7 (2024-04-30)
2.1.6 (2024-04-11)
2.1.5 (2024-02-27)
- Add bang to the
g@
normal command. (#297) (0c02c52) - dot-repeat: Clear dot-repeat after indentation (#306) (8f2af76)
- Visual selection highlight disappearing. (#312) (a72a97c)
2.1.4 (2023-12-04)
2.1.3 (2023-11-13)
2.1.2 (2023-10-22)
2.1.1 (2023-08-05)
2.1.0 (2023-05-28)
- Implement
change_line
mapping. (ff9c981)
- buffer:
set_mark
should check for validity of input. (841f83f)
2.0.5 (2023-04-02)
- Don't re-indent single-line surrounds. (2fca63c)
2.0.4 (2023-03-28)
2.0.3 (2023-03-27)
2.0.2 (2023-03-27)
2.0.1 (2023-03-21)
- config: User-defined surrounds fallback on defaults. (29929a5)
2.0.0 (2023-03-11)
- The function
get_char
has been moved fromutils
toinput
. - The function
get_delimiters
has been moved fromutils
toconfig
. - The
textobject
field forconfig.get_selection
has been deprecated; please usemotion
instead. See this comment.- To update your functions, prepend 'a' to the
textobject
key, i.e.(
→a(
- To update your functions, prepend 'a' to the
- The highlight group used has been renamed from
NvimSurroundHighlightTextObject
toNvimSurroundHighlight
. See this comment. - User defined
invalid_key_behavior
handlers will be activated for control characters that don't have definedsurrounds
. In other words,<C-a>
is now a valid input that can be passed toinvalid_key_behavior
. See this comment.- Note:
<C-c>
is still invalid, and terminates the input.
- Note:
- Smart quotes have been removed. Modifying quotes will now always operate on the immediately surrounding pair of quotes. See this comment.
- Add
node
field toconfig.get_selection
, allowing users to retrieve selections based on treesitter nodes. - Add
indent_lines
field tosetup
, allowing users to configure what indentation program should be used for certain line-wise surrounds (if any). - Add
<Plug>
mappings; decouple mappings. (af10059) - Add
exclude
key toconfig.get_selections
. (e2c22a6) - Implement basic query-matching. (a634889)
<Plug>(nvim-surround-insert)
mapping. (#176) (6b45fbf)- Add indentation when using line mode. (#185) (9da7ced)
- Add protected call around Tree-sitter module. (d91787d)
- Change
reset_cursor
semantics. (a207e3b) - Change type annotations to
|nil
from?
. (1ac5abf) - Correctly restore visual selection marks. (#155) (c6a1993)
- Failing test cases due to Tree-sitter dependency. (c057fb8)
- Fix catastrophic error that broke everything. (c323fa5)
- Fix quote bug, closes #172. (58b0a55)
- Handle special characters for
getchar
. (#170) (1f79449) - Improper look-behind for quotes. (1d83fec)
- Improper table handling for
add
, resolves #191. (d51d554) - Minor bugs. (7f7ca04)
- Properly handle linewise normal surrounds. (90821ad)
- Remove
remap = true
from keymaps. (#219) (89c82e7) - Revert some changes. (ce01942)
- Revert to pattern-based function calls by default. (ba19320)
- Support Lua 5.1 instead of only LuaJIT. (#169) (fa7648e)
- Tweak pattern for function calls. (3accef6)
- Update function pattern. (c0835d2)
- Use
line_mode
parameter when possible. (#194) (ad56e62) - utils: Ensure chars is a table in ipairs. (#192) (64e2106)
- Error when
vim.o.selection='exclusive'
. (#158) (81f672a)
Sorry for the long time in between releases everybody, I thought I could implement queries support in a sensible way in a short amount of time, but it quickly became much more to handle than I had thought. Moving forwards, I aim to make the plugin "more stable" and to improve the user experience:
- Be more consistent with SemVer releases (i.e. version more frequently)
- Improve the automated testing suite
- Improve the documentation (considering automated documentation)
- Improve the customizability of the plugin (it should do what you think it
does)
- This is somewhat accomplished in the current release, as more fields can be
set to
false
, but could still use some work
- This is somewhat accomplished in the current release, as more fields can be
set to
Thanks again to everyone for using this!