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

[Question] Project status #14

Open
karambaq opened this issue Mar 22, 2023 · 2 comments
Open

[Question] Project status #14

karambaq opened this issue Mar 22, 2023 · 2 comments

Comments

@karambaq
Copy link

I see you didn't change your config in 2 month (crazy), Is it means that you back to vim or you just found perfect config? :)

@LGUG2Z
Copy link
Owner

LGUG2Z commented Mar 31, 2023

I am constantly dipping in and out of Helix, NeoVim, VSCode and IDEA depending on what I'm working on. 😅

The biggest part (and probably the most lasting part) of this project is actually the README. Just today, I saw this comment on Hacker News:

I recently tried this: https://github.com/LGUG2Z/helix-vim which attempts to provide vim mappings to Helix. It's funny how the description in the page describes my progression almost 100%. And while it makes things slightly better, it's still not accurate enough to make this a non-issue.

What tends to happen is people use the config as a starting point and then refine it more and more to match their own tastes (since no two Vim configs are ever alike!) but generally speaking I'm always open to accept PRs integrating more "default Vim" bindings into the config in this repo.

@m-fonseca
Copy link

FYI, I couldn't believe how spot on this README was... I've got 20+years of vim muscle memory, and I just don't see me adopting to Helix keybindings. Probably even more importantly vi is on so many places I ssh to. I don't need the extra confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants