chat.sr.ht supports multi-client identification, but as it stands, there's no real way to use the same config across multiple computers (if I have my config checked into version control) and set the value dynamically.

https://man.sr.ht/chat.sr.ht/quickstart.md#multi-client-identification

Is there a way to do this?

Sorry, I mean XDG_CONFIG_HOME, not XDG_CONFIG_DIR.

On macOS, config defaults to $HOME/Library/Application Support/senpai/senpai.scfg.

Obviously, XDG_CONFIG_DIR is not a thing on macOS, and setting it has no effect. Is there another way to default the config directory to ~/.config/senpai/senpai.cfg without having to specify --config when running senpai?

Thank you for the workaround. I read through the issue for lazy.nvim and I fully agree that the best way to fix this issue would be a filetype exclusion list.

Looks like this is fixed: https://github.com/neovim/neovim/issues/22704

This is my diagnostic config:

    vim.diagnostic.config({
      update_in_insert = false,
      signs = false,
      severity_sort = true,
      virtual_text = false, -- Since we're using lsp_lines
      virtual_lines = true,
    })

And here is what a file with diagnostics looks like to me, compared to :Lazy after running sync: https://imgur.com/a/fMZYf39

I'm not sure why Lazy is showing both, and why it's showing it as diagnostics as opposed to just virtual text... but I prefer not having lsp_lines for just :Lazy.

I understand, and it is specifically lazy.nvim

I have my regular buffers configured properly and it's really beautiful. Really love your plugin.

But in lazy, I just need to disable the virtual_lines.

With lazy.nvim, it'll show both lsp_lines, as well as the default diagnostic when I run :Lazy, even if I turn the default diagnostic off.

If I require('lsp_lines').toggle(), both will go away... and if I toggle again, only the lsp_lines one will come back.

I'm wondering if there's a way to ONLY have the default virtual text show up, as it makes sense for it to be on the right of the text in this context only. I think simply disabling lsp_lines for this filetype would work out well for this case.