elixir_sense

elixir_sense copied to clipboard

Hi,

I've started a fork of this project with the goal of providing complete support for alchemist.el and, by extension, other LSP clients.

I look forward to coordinating on contributions, in case you intend to pursue upkeep and/or development of this project. If you're uninterested, please let me know whether you care about the name staying the same or being changed.

Thank you.

Hi @Trevoke. The intention of this project is to be agnostic regarding any specific editor. That's why I've split it from atom-elixir in the first place. I'm not sure what kind of features do you need in ElixirSense in order to provide full support for alchemist.el. As far as I understood, you're going to use elixir-ls, right? In this case you're already using ElixirSense. So what are the changes you're considering doing? Are they useful for other editors?

Hi @msaraiva , thank you for responding!

I've not yet had to make any changes, and with luck I won't have to make any, but I've had a really hard time reading through the code and understanding what things meant, or figuring out if some behaviors were intended, in no small part because there's no documentation, either for code or macros, and in the past three months or so I've not been able to get in touch with you, so it seemed like a fork where I could rename variables, functions, and modules, and add documentation, may be the least costly solution, without affecting anything else.

Related, I think that, much like elixir-ls ( which I also forked https://github.com/JakeBecker/elixir-ls/issues/78 for similar reasons ), this should be a community project, not under anyone's particular ownership, but something that can be worked on and easily maintained by many people, so removing the ownership from a single person seemed like a good idea.

Honestly, one of my hopes is to get these projects under the elixir-lang org as well.

I didn't really want to fork, but I had received no reply on https://github.com/msaraiva/elixir_sense/issues/28 and I had opened a bunch of other issues which I self-closed because the project didn't seem actively maintained at all...

Anyway - other than my perspective on communal ownership, I have no vested interest right now in keeping the fork open, other than "I'm the most responsive person I know who's working on this".