Found a solution to a bug that is caused when Lspsaga's hover doc and Marksman lsp are both active.

[FlawlessCasual17]

I found a solution to a bug that is caused when Lspsaga's hover doc and the Marksman Lspconfig are used together.

🪲 The Problem

Sometimes when you open the hover doc from Lspsaga, Marksman (an lsp server for markdown/MDX) will attempt to lint, provide diagnostics through virtual text, and so on. This is because the hover doc will create a new markdown buffer containing the information you are requesting from another lsp server. However, because that buffer is not modifiable, this conflict will cause Marksman to crash with an exit code of 0.

💡 The Solution

To prevent Marksman from conflicting the with Lspsaga's hover doc, you will have to modify the lspconfig setup for the Marksman lsp server. Here is how you should do it in your init.lua config file:

local lspconfig = require('lspconfig')

lspconfig.marksman.setup {
  -- This solves the problem of Marksman exiting when a new hover doc buffer (from Lspsaga) is created
  ---@param bufnr number
  autostart = function(bufnr)
    local is_md = (vim.bo[bufnr].filetype == 'markdown') or (vim.bo[bufnr].filetype == 'markdown.mdx')
    if (vim.bo[bufnr].modifiable) and is_md then
      return true -- Return true to allow autostart
    end
    return false -- Otherwise, return false to prevent autostart
  end,
  ---@param bufnr number
  enable = function(bufnr)
    local is_md = (vim.bo[bufnr].filetype == 'markdown') or (vim.bo[bufnr].filetype == 'markdown.mdx')
    if (vim.bo[bufnr].modifiable) and is_md then
      return true -- Return true to allow autostart
    end
    return false -- Otherwise, return false to prevent autostart
  end
}

This will ensure that Marksman ONLY autostarts when a newly created buffer is modifiable, AND the file type is either markdown or MDX.

I hope this helps anyone who was also facing a similar or same problem that I encountered.