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

Feature request: text-based auto-completion #4326

Closed
xJonathanLEI opened this issue Oct 17, 2022 · 2 comments
Closed

Feature request: text-based auto-completion #4326

xJonathanLEI opened this issue Oct 17, 2022 · 2 comments
Labels
C-enhancement Category: Improvements

Comments

@xJonathanLEI
Copy link
Contributor

I'm trying to daily drive with Helix but find myself missing the (current buffer / opened buffers) text-based auto-completion feature from neovim a lot.

The best thing about text-based (vs. LSP) auto-completion is that it's super fast and has no dependency. It can be very helpful when:

  • the LSP is not installed (or not supported)
  • I just wanna make a quick edit, and don't want to wait for the LSP to initialize (especially ones with slow startups like rust-analyzer?)
  • even when the LSP is initialized, sometimes it takes a while to reflect code changes, and it's faster to just get text-based suggestions if I'm familiar with the codebase I'm editing

Lacking this feature, I have to do a lot of find-yank-replace instead of just typing out the first letters and selecting from the suggestions. This is especially bad in dynamic languages since a typo may not be detected until runtime, making the user more cautious and always opt for find-yank-replace.

I'm pretty certain this has been requested (or even already implemented) before, but I can't find anything relevant from the issues. Sorry for spamming if that's the case. Would love a pointer to the relevant issue. Thanks!

@xJonathanLEI xJonathanLEI added the C-enhancement Category: Improvements label Oct 17, 2022
@Omnikar
Copy link
Contributor

Omnikar commented Oct 17, 2022

#1063

@xJonathanLEI
Copy link
Contributor Author

Ah "lexical" is the keyword. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: Improvements
Projects
None yet
Development

No branches or pull requests

2 participants