Closed xiaoshihou514 closed 2 weeks ago
@glepnir I think you would have to add some repo secrets as instructed here
It seems like vim.fn.executable
may return 1 for tools that are installed by mason but not in PATH, I added a check for this in lua/guard/health.lua
.
also create a .luarc.json file for luals config.
nice work
thinking about create a floating window to show the all config of user defined and config for current buffer. like lspinfo we can call guard info
or something else.
thinking about create a floating window to show the all config of user defined and config for current buffer. like lspinfo we can call
guard info
or something else.
I went for just printing, though that would be nice.
yup. but no rush. can in the subsequent PR
Added info in floating markdown window :)
This pr fine tunes the user interface according to nvim-best-practices
Guard
+ subcommands instead of multiple individual commandsft(...):fmt
should work immediatelyft(...):fmt
,ft(...):lint
, etc.~ HARD, maybe latervim.validate
calls for perfhaskell-tools.nvim