fix: disable autostart after :LspStop

[brookhong]

Remove autocmd BufReadPost on LspStop so that lsp won't be auto started on buf read after explicit stop with LspStop.

[justinmk]

Can the callback check if the client was force stopped? Then it can return true, which will automatically remove the autocmd.

Suggested change

	M.manager:try_add_wrapper(arg.buf, root_dir)
	if client.is_stopped -- psuedocode
	return true
	end
	M.manager:try_add_wrapper(arg.buf, root_dir)

[brookhong]

Nice, with this addressed, other two comments should be also good.

Thanks, updated.

[justinmk]

This seems fragile. OTOH, I guess LspStop itself is kind of a hack so...

[justinmk]

I was hoping there is a way to checking that the clients were force-stopped. Could there be an edge case where the client dies because of an error, which would then (unintentionally) remove this autocmd?

I guess we can try this. LspStart will recreate this autocmd again.

[artkpv]

@justinmk , @glepnir Thank you for this tool.

I wish to stop Lsp in my personal wiki. I start it with

 nvim -c 'cd ~/mydir/notes' -c WikiEnable  -c 'lua vim.g.init_my_wiki_config()' "$@"

Where this funciton there is

--- Inside my Lazy config for my wiki pluging (https://github.com/lervag/wiki.vim)
    'lervag/wiki.vim',
    lazy = false, -- we don't want to lazy load VimTeX
    config = function()
      vim.g.init_my_wiki_config = function()
        --- ...
        vim.cmd 'LspStop'
       end
    end

It works for my first buffer I open. But when I move to another buffer (.md) the lsp starts. And I need to enter :LspStop. Then the lsp doesn't start for other buffers.

How to stop the lsp? Expected behavior: my function there in my config in init.lua stops the lsp and I don't need to type :LspStop each time I open another buffer. Is there some flag like 'disable_lsp' or something to do that?

[glepnir]

which server you used for wiki.vim find it and set auto_start =false.