Closed sharksforarms closed 3 years ago
Thanks, I appreciate this! This is a bit nitpicky, but if we're going to add this level of customization to the statusline (which I'd always intended more as a demonstration for how you can build your own statusline component), then I think it makes more sense to pull the different parts of the statusline component out into their own functions, to make it easier to build customized statuslines.
We can keep the config variables too (though I would suggest restructuring them to be a nested table, for cleanliness), but I'd prefer that the variables gate calls to functions providing the various status sub-parts.
@wbthomason I agree, that makes more sense to me too.
In relation to: https://github.com/nvim-lua/lsp-status.nvim/issues/30
Let me know what you think! I'll make a docs commit once the config options are OK'd