Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to configure spinner and lsp_client_name to not be hidden #10

Open
snaggen opened this issue Nov 9, 2021 · 3 comments · May be fixed by #12
Open

Option to configure spinner and lsp_client_name to not be hidden #10

snaggen opened this issue Nov 9, 2021 · 3 comments · May be fixed by #12

Comments

@snaggen
Copy link

snaggen commented Nov 9, 2021

When I use lualine with lsp setup and this extension I get a pretty nice experience, what I miss is an indication if a lsp is active at all. So I think just having an option to not hide the spinner and lsp_client_name would solve this. This would change the semantic of the spinner a little bit to just be an lsp indicator when idle, to indicate a lsp is present and connected with a new icon, then the current spinner when showing progress.

@aktau
Copy link

aktau commented Nov 28, 2021

I was looking for such an option too. Thanks for filing a FR before I could :).

@tamirzb tamirzb linked a pull request Dec 26, 2021 that will close this issue
@syphar
Copy link

syphar commented Jan 5, 2022

I'm not sure if this really fits into this component, since it's only for the status progress.

You can easily add this yourself as a custom component in lualine:

local function lsp_client_names()
	local client_names = {}
	for _, client in ipairs(vim.lsp.get_active_clients()) do
		table.insert(client_names, client.name)
	end
	return table.concat(client_names, ",")
end

require("lualine").setup({
	sections = {
		lualine_a = {
			lsp_client_names
		}
	}
}

@bercly0b
Copy link

Hi guys. I have made PR with this option.
But since 4 months have passed since the last commit to the repository, I dont know will this request be accepted..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants