feat!: fine tune user interface#158
Merged
xiaoshihou514 merged 48 commits intonvimdev:mainfrom Oct 3, 2024
Merged
Conversation
Member
Author
|
@glepnir I think you would have to add some repo secrets as instructed here |
Member
Author
|
It seems like |
glepnir
reviewed
Aug 20, 2024
Member
|
also create a .luarc.json file for luals config. |
Member
|
thinking about create a floating window to show the all config of user defined and config for current buffer. like lspinfo we can call |
Member
Author
I went for just printing, though that would be nice. |
Member
|
yup. but no rush. can in the subsequent PR |
Member
Author
|
Added info in floating markdown window :) |
glepnir
reviewed
Sep 1, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pr fine tunes the user interface according to nvim-best-practices
Guard+ subcommands instead of multiple individual commandsft(...):fmtshould work immediatelyfiner typing forHARD, maybe laterft(...):fmt,ft(...):lint, etc.vim.validatecalls for perfhaskell-tools.nvim