-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: enable blink #119
Merged
Merged
feat: enable blink #119
Conversation
This file contains 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
Also - Disable cmp for now
<leader>dL launches osv (nvim debugee) anywhere, not just lua. This improves the ergonomics of debugging neovim lua.
Add a debugging flag (and keymap toggle) that causes most messages to get output & available via `<leader>sna`. This makes it much easier to figure out how to configure routes for messages. As part of this, also update noice routes to greatly simplify the way in which I silence the annoying toast messages.
Switched the snippet forward/back keymaps to blink from luasnip as this prevents the issue of accidentally getting back into a snippet in insert mode making <c-{j,k}> typos take you to surprising places.
I should use <leader>sC to fuzzy match commands rather than rely on a memorable prefix.
I find I really want <m-j> to step over, not into.
I need to configure wezterm whenever adding a new M-x keymap
function M.foo is better than M.foo = function because it only creates one function definition location for the lua LSP, making go-to-definition immediately jump to the function rather than force you into a selector
Disable following the current file and instead expand <leader>e to multiple keybindings <leader>ee <leader>eE to have control over whether or not to reveal the current buffer. In practice I often, but not always, want the current file revealed, and the autofollow behaviour winds up being annoying when trying to set up two buffers for comparison.
In general I prefer <s-*> to mean "do this more aggressively", so I typically expect <leader>fF to have the broader search semantics
Add -unscoped to the unscoped variants, to make it possible to select them just with the fuzzy query and not have to actually navigate the completion items.
>2m is a bit annoying, presumably I can cache both fzf installation and binutils binaries
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.
Also has a lot of changes related to bumping plugins generally.