Breakages with latest plugin versions

[tommyalatalo]

This is not lazy.vim specific I think, but if I sync my plugins to the latest versions I've noticed for some time (a few months) that a couple of behaviors are broken or overwritten, and I feel it's time to try to fix them:

1. Shift+S is overwritten by some plugin now, I very often use shift+s to replace an entire line, but now some plugin is catching this and creates a visual selection with interactive scope selection. How can I check what is taking the shift+s input? (I tried looking in :no but I couldn't find it.
2. mini.comment is broken for .hcl files for some reason, I can see in :LspInfo that the file type is detected as hcl, but when I use my comment key combo I get a response from the plugin saying (mini.comment) Option 'commentstring' is empty.. Any idea what's causing this?

[folke]

shift+S is flash. You can disable that mapping in your config.

You can add extra comment strings with
LazyVim/LazyVim#1368 (comment)

[tommyalatalo]

Hmm, so I added this in my core.lua plugin file where I collect customizations to the bundled plugins. I want to set the keybind to start with <leader>, but the plugin is still overriding the default, current config below.

< more above >
{
	"folke/flash.nvim",
	event = "VeryLazy",
	vscode = true,
	---@type Flash.Config
	opts = {},
  -- stylua: ignore
  keys = {
    { "<leader>s", mode = { "n", "x", "o" }, function() require("flash").jump() end, desc = "Flash" },
    { "<leader>S", mode = { "n", "o", "x" }, function() require("flash").treesitter() end, desc = "Flash Treesitter" },
    { "r", mode = "o", function() require("flash").remote() end, desc = "Remote Flash" },
    { "R", mode = { "o", "x" }, function() require("flash").treesitter_search() end, desc = "Treesitter Search" },
    { "<c-s>", mode = { "c" }, function() require("flash").toggle() end, desc = "Toggle Flash Search" },
  },
},
< more below >

[folke]

please read the lazyvim docs on how to update/disable plugin keymaps

[tommyalatalo]

Ah thanks, I found it.

I suddenly have another error popping up though, a bit of whack-a-mole this.

Failed to run `config` for indent-blankline.nvim

.../share/nvim/lazy/indent-blankline.nvim/lua/ibl/utils.lua:18: 'show_current_context_start' is not a valid key of ibl.config

# stacktrace:
  - /indent-blankline.nvim/lua/ibl/utils.lua:18 _in_ **validate**
  - /indent-blankline.nvim/lua/ibl/config.lua:111 _in_ **validate_config**
  - /indent-blankline.nvim/lua/ibl/config.lua:271 _in_ **set_config**
  - /indent-blankline.nvim/lua/ibl/init.lua:59 _in_ **setup**
  - vim/_editor.lua:341
  - /telescope.nvim/lua/telescope/actions/set.lua:200 _in_ **run_replace_or_original**
  - /telescope.nvim/lua/telescope/actions/mt.lua:65 _in_ **run_replace_or_original**
  - /telescope.nvim/lua/telescope/actions/mt.lua:65 _in_ **run_replace_or_original**
  - /telescope.nvim/lua/telescope/actions/mt.lua:65 _in_ **key_func**
  - /telescope.nvim/lua/telescope/mappings.lua:257

Is this due to a break in the indent-blankline plugin, I'm thinking yes?

[folke]

obviously? Check the indent-blankline readme. It's updated to v3. You may have to migrate some settings.

Please just read docs.

[tommyalatalo]

You're right, I was in a bit too much of a hurry when looking at this. Thanks.