[Elixir] Apprentice, a new alchemist.el fork

Hello everyone! Some time ago, I commented in the [Alchemist Resurrection](https://github.com/tonini/alchemist.el/issues/371#issuecomment-1198455900) issue, talking about how alchemist.el can be a nice alternative to LSP. BUT, with the news that in the next Emacs version [eglot](https://github.com/joaotavora/eglot) (lsp client) is going to be in the core, I decide to modify alchemist in a different way, enhancing other capabilities and letting eglot do what he best does (which is the functionality of [elixir-ls](https://github.com/elixir-lsp/elixir-ls)). I'm quite relief to know that this lsp server is FROM the community and heavily inspired by the original alchemist-server. For now, Apprentice is usable, similar to alchemist.el but with most of the merge requests in place and with some changes: * Remove s, f and dash dependencies * Remove cask as a project manager, using a simple Makefile (I don't have anything against Cask, but I prefer to use my method) * No alchemist server, this is the main point and all the functionality that was using some of the underlying capabilities are not working (but some of them will be implemented in a different way) * An optional vterm REPL with IEx My next steps will be to fix some underlying functionality that was quite useful like help and macroexpand. I hope in the future to submit this fork to MELPA (given that alchemist.el is no longer maintained),for now, here is the project: [https://github.com/Sasanidas/Apprentice](https://github.com/Sasanidas/Apprentice) :)

I use Elixir daily so I'm happy to see this! I like the approach of it being a companion to LSP.

Is it eglot dependant in any way? I'd be really interested if it worked with lsp-mode as well

Neither this nor your github readme says what (or where) Elixir is.

It says in the README, the first line behind the logo: "Elixir Tooling Integration Into Emacs " (I'm refering to the Elixir programming language)

Oh no, I mention eglot because it's now officially in Emacs core, in the end you can use whatever lsp client you want (or none)

Yes, that was exactly my point. What (and where) is "Elixir Tooling"? You're posting to a general Emacs forum and expecting all of the readers to have heard of that programming language, and to know what "Elixir Tooling" means. I suggest that you provide the *bare minimum* of a link to the "Elixir Tooling" that you're referring to, for people who haven't the foggiest idea what you're posting about.

I don’t think people who don’t know about elixir would be interested of this package, and the target audience of this announcement would certainly know about elixir.

> the target audience of this announcement would certainly know about elixir. I don't doubt it. > I don’t think people who don’t know about elixir would be interested of this package I don't think the people who don't know about elixir would be able to tell what the package is for, so how would they know whether it was of interest? (This is the crux of the issue.) I can't believe I have to defend "include a link to the thing that your repository is related to", but honestly, it's always helpful, and there's no good reason not to do it. Even the general assumption that there will only ever be one thing out there by a given name is a bad one. Linking to the related things is a trivial way to ensure that everyone knows what's what, no matter how or why they arrived at your readme.

If you are really interested in the package, you can always click in the doc repository (point out by the main README) and go to the install file: [https://github.com/Sasanidas/Apprentice/blob/master/doc/installation.md](https://github.com/Sasanidas/Apprentice/blob/master/doc/installation.md) There are two links there, one for Emacs an the other for the Elixir programming language. I think at this point the relationship is quite clear.

I agree -- http://elixir-lang.org/ seems like the perfect URL. If you put that in the readme file, the problem is solved.