Origanization Name

[gj1118]

Folks,
I am creating this poll to understand what we should be calling our organization. If you have more choices, please let me know and I will add them to the list. Once when I have done , that, I will move this repo under that org.

[RokKosSloyd]

Can we add these two options to the list:

• Lumen: "Lu" prefix for future Lua plugin system. It also means "light" in Latin, to credit all the "glow-up" features and improvement features (notification system, gradients, borders etc).
• Orbital: To give credit to the core Helix engine around which we build.

[m0n99]

Helua

[Rudxain]

I have a dilemma:

• "NeoHelix" feels wrong, but it makes perfect sense
• "Orbital" and "Lumen" feel right, but they would only make sense if this project was substantially different, and/or was a detached-fork or hard-fork

(I see no reason to choose "Uno" 😕)

[tylerlaprade]

Realistically, NeoHelix is the only name that will get any traction

[tylerlaprade]

NeoHelix is perfect, actually! It's an evolution of Helix to modernize it and give a better out-of-the box experience, which is in line with the original Helix and even kakoune philosophies.

[sheam]

While I don't love NeoHelix, it makes the most sense. It is a furthering of the Helix project, and it's name alone conveys that it is a furthering of the Helix editor. While the other names are good, someone would specifically have to be looking for a Helix like editor to come across them. With NeoHelix, anyone looking into Helix editor would naturally stumble across NeoHelix. Inherent SEO if you will. My biggest concern with switching to helix (4 months ago), is that it is a dead project. So I have been using this fork for a couple months now. The point being that the name NeoHelix could help the project gain some momentum, which I think is really important.

[gj1118]

While I don't love NeoHelix, it makes the most sense. It is a furthering of the Helix project, and it's name alone conveys that it is a furthering of the Helix editor. While the other names are good, someone would specifically have to be looking for a Helix like editor to come across them. With NeoHelix, anyone looking into Helix editor would naturally stumble across NeoHelix. Inherent SEO if you will. My biggest concern with switching to helix (4 months ago), is that it is a dead project. So I have been using this fork for a couple months now. The point being that the name NeoHelix could help the project gain some momentum, which I think is really important.

How are you liking this fork ? Any issues so far that we might have introduced as part of this fork ? Any performance issues?

[sheam]

No I haven't had any issues. Other than the fact I use it on 5+ machines, so building from source every time is a bit of a pain. I also don't really care about the plugins, IMHO plugins are what has made neovim such as pain, and the reason I stopped using it after 20 years of being a vim/neovim user. I like the concept of simple, but batteries included. The biggest thing I miss is the * operator selecting the word into the search buffer. With Helix I need to do e, b, *, n. It seems a little clunky. 99% of the time, when a cursor is on a word, and the user hits *, chances are they want to search for occurrence of the whole word. I know I can likely solve that with a keybinding, just haven't got it. But I think focusing on the 90% use case for new feature is generally better.

[axodentally]

EDIT: may be irrelevant. Read #17 too late, sorry!

ORIGINAL COMMENT:
I agree with @sheam that a name that incorporates helix makes more sense than something like lumen. However the name neohelix sounds to me more like a resurrection of a dead project, in which I disagree with sheam, that the original helix project is not dead, but only really slow moving.
I dont't know what the vision for this project will be and how close the maintainers want to keep it to upstream, but if the project will more be like an "unstable helix" (which others called it previously), mostly incorporating opened / recently closed PRs with the hopes of getting most of those upstream, then a name like "neohelix" does not signal that correctly. (However if this project wants to "move beyond helix", then such a name is fitting, I would say)

So for me the question first ist: what will the vision for this project be like?

[tylerlaprade]

Helix is never going to accept new features in core because they can now defer to "just make an extension" for everything. This is antithetical to Helix's own original philosophy. So in that sense, it is a dead project. And this project is moving beyond that by adding new features in core.