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

Project goals? #65

Closed
pickfire opened this issue Jun 2, 2021 · 3 comments
Closed

Project goals? #65

pickfire opened this issue Jun 2, 2021 · 3 comments
Assignees
Labels
A-documentation Area: Documentation improvements C-enhancement Category: Improvements

Comments

@pickfire
Copy link
Contributor

pickfire commented Jun 2, 2021

I wonder what are the project goals of helix. I have used quite a few editors, vim, neovim, vis, kakoune, doom emacs but I wonder what are the goals of this project? All of them have some stuff that I like but up till now all have their own downsides. I wonder what helix aims to achieves.

Also, since the project is new, we have the luxury to change the keymaps at the start, having used quite a few editors I think some of the keys in kakoune could be improved (some not easy to remember and some useless, like x vs X). Maybe we could create an RFC and discuss the alternatives and which keys to do what? By the way, I like kakoune alt, but not the limitation of terminal not being able to differentiate between ctrl-shift and ctrl, alt is similar case IIRC.

@rieger-jared
Copy link

I guess this is also associated with the issue #165

I would also like to contribute to what I hope the project would become.

I've also used Doom emacs, nvim, vscode but like you've said @pickfire, they all have their own downsides. For example, I found Doom emacs to be slow and too bulky, however I liked that it came preconfigured with the ability to perform file navigation, search ect. nvim is great in the fact that it's really customisable. I also find that this is also it's negative, as a lot of the plugins I end up installing are essential features that I find are missing in an editor. For example, tpopes "surround" plugin that allows a user to manipulate quoted text. Or telescope that allows a user to use fzf finding to quickly access files.

I guess it also depends on how opinionated the editor wants to be.

@blaggacao
Copy link

blaggacao commented Aug 2, 2021

Prime support for foot pedals that correspond to the mode switches? half in ernest. At least it's novel. And could be merchandise number 1. 😄 (and frees up 2 keys or potentially more prime estate)

@kirawi kirawi added A-documentation Area: Documentation improvements C-enhancement Category: Improvements labels Aug 19, 2021
@kirawi
Copy link
Member

kirawi commented Sep 26, 2021

Closed 31f1455

@kirawi kirawi closed this as completed Sep 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-documentation Area: Documentation improvements C-enhancement Category: Improvements
Projects
None yet
Development

No branches or pull requests

5 participants