Marco Bueß

For some reason it is more consistent if you're binding without explicit prefix but rather using `[""]` directly in the binding. Then if setting `mode { "n", "v" }` it's...

Latest version of Windows Terminal (v1.20.11271.0) also introduced a situation where `` was not working as expected anymore. I was able to fix that defining a custom action in the...

@IvanXh0 Are you running in WSL? I'm running outside WSL and the sequence yields `"` for me.

Having no clue about all this, I thought it might be as simple as adding `markdown-it-admonition` to `package.json` and the following code to `index.jsx`: ```jsx import admon from 'markdown-it-admonition' ......

@shadmansaleh Are there ways to make the `active` color dynamic? I'd like to change color based on the mode im currently in. Thanks for the headsup.

@shadmansaleh Do I need to trigger some sort of a refresh, so that when the mode changes the colors get reloaded? Any tips or docs on howto go about that?...

It was surprisingly easier that I thought. Here is the code for anyone interessted. ```lua buffers_color = { active = function() local mode_names = { n = "lualine_a_normal", i =...

I don't know if something broke recently, but it seems like the `buffer` component doesn't detect active buffers correctly. I'm sure this has worked in the past. When you have...

@CppCXY I just tried the suggest option but behavior wise nothing changed. Still behaves as @KayleMaster described above.

Aight. So the situation is that I'm providing the arguments directly through `nvim-lspconfig` rather that `.editorconfig`. It can't handle the value passed als lua bool. You will have to provide...