Few deprecations of methods in neovim nightly.

[231tr0n]

Hi @echasnovski! It seems mini.bracketed is using few functions which will be deprecated as of nvim 0.13. Is it in scope to migrate from these methods as of now, or will this be held till nvim 0.13 is released and then migrated. I dont know if these are going to get addressed now or later and hence I decided to create a discussion instead of an issue.

- ⚠️ WARNING opts.cursor_position is deprecated. Feature will be removed in Nvim 0.13
  - ADVICE:
    - use opts.pos instead.
    - stack traceback:
        /tmp/.mount_nvimdDdFAE/usr/share/nvim/runtime/lua/vim/diagnostic.lua:1312
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:462
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:1266
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:486
        lua:1
    - stack traceback:
        /tmp/.mount_nvimdDdFAE/usr/share/nvim/runtime/lua/vim/diagnostic.lua:1436
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:491
        lua:1

 ~
- ⚠️ WARNING vim.diagnostic.get_next_pos() is deprecated. Feature will be removed in Nvim 0.13
  - ADVICE:
    - use access the lnum and col fields from get_next() instead instead.
    - stack traceback:
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:462
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:1266
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:486
        lua:1

 ~
- ⚠️ WARNING vim.diagnostic.goto_next() is deprecated. Feature will be removed in Nvim 0.13
  - ADVICE:
    - use vim.diagnostic.jump() instead.
    - stack traceback:
        /home/zeltron/.local/share/nvim/site/pack/deps/opt/mini.nvim/lua/mini/bracketed.lua:491
        lua:1

[echasnovski]

Is it in scope to migrate from these methods as of now, or will this be held till nvim 0.13 is released and then migrated. I dont know if these are going to get addressed now or later and hence I decided to create a discussion instead of an issue.

Yes, it is in scope, but not in a hurry. I'll adjust the code some time in the future. Thanks for reporting this!