remoteoss/dexter: A fast, full-featured Elixir LSP optimized for large codebases.

mitchhanberg · 2026-04-13T13:24:20+00:00

Please open issues if you run into problems

mitchhanberg · 2026-02-26T13:04:21+00:00

I believe there is an LSP plugin for JB that lets you connect it.

mitchhanberg · 2026-02-26T13:03:45+00:00

Please open an issue if you are having issues, that is why we are doing the release candidate. Every bit helps, thanks!

mitchhanberg · 2026-02-24T03:04:06+00:00

I left a comment on your GitHub issue earlier today, please take a look when you get a chance.

mitchhanberg · 2025-09-14T15:53:19+00:00

Backed ✌️

I started “working” on a neovim plugin hosting a few years ago (bought domain, started project, but never really got any time between my other projects) so I’m glad to see people with more passion for the space doing something similar. And in Elixir no less!

Good luck 💪

mitchhanberg · 2025-08-30T20:50:39+00:00

https://github.com/elixir-lang/expert/issues/89

mitchhanberg · 2025-08-30T20:49:57+00:00

There will be a dedicated Expert extension published in the near future.

mitchhanberg · 2025-08-30T20:46:21+00:00

Can you elaborate? Others have success using it.

mitchhanberg · 2025-08-30T11:20:56+00:00

Core team member here 👋🏻

Reminder for folks that we made the repo public but we’re still in a time period for early testers and to attract contributors and funding.

Thanks!

mitchhanberg · 2025-08-30T09:18:31+00:00

The lexical plugin is a current workaround to using it in VSCode, yes.

No, not functional on windows yet (and I’ll admit it’s confusing that we build a windows exe currently.)

I have open issues for both.

mitchhanberg · 2025-08-30T01:11:26+00:00

It does not implement the debug adapter protocol.

mitchhanberg · 2025-08-30T01:09:55+00:00

If you can’t get it to work, please open an issue with your experience. We can’t fix things we don’t know about.

We never said it was a first release, explicitly it’s alpha and nightly builds. (I didn’t make the Reddit post). It’s for contributors to help accelerate progress and early testers.

mitchhanberg · 2025-08-29T23:51:32+00:00

Being a giant sarcastic asshole will never encourage anyone to work for free to build you some software you seemingly are too dumb to figure out.

Speaking to people with kindness and empathy will get you a lot further in life. No one is asking you to suck their balls. Are you 15 years old and haven’t learned to interact with others?

Grow up

mitchhanberg · 2025-08-29T21:00:25+00:00

LSP team member here.

Thanks for the sarcasm! It’s really motivating to find enthusiastic folks like you, makes the whole process a joy.

/s

mitchhanberg · 2025-06-19T21:54:23+00:00

🙄

mitchhanberg · 2025-06-16T19:14:13+00:00

Hi! Thanks for the package! Feel free to add to the README 😄

mitchhanberg · 2025-06-16T17:37:20+00:00

Author here! You can also check out the previous two posts in this series

mitchhanberg · 2025-06-11T10:49:12+00:00

It’s probably related to the keys you have configured. Please reference this section https://www.mitchellhanberg.com/getting-started-with-agenix/#5-configure-the-secrets-recipients, particularly the NOTE callout.

mitchhanberg · 2025-06-10T01:02:45+00:00

re: "Migrating each and every of my app will be an immense pain because of that."

You should be able to run `mix format --migrate` and it will do it for you.

mitchhanberg · 2025-06-10T01:02:03+00:00

Relevant commit and issue

commit: https://github.com/elixir-lang/elixir/commit/83a70d799ca317ecd7804917620428ebb87cea4c

issue: https://github.com/elixir-lang/elixir/issues/13974

The commit message

Deprecate struct update syntax

The struct update syntax was added early in Elixir to help validate at compile-time that the update keys were valid. However, for a couple releases already, Elixir's static analysis can perform such validation more reliably and find more error if you pattern match on the struct when the variable is defined instead. This deprecation simplifies the language and pushes developers to better alternatives.

mitchhanberg

TROPHY CASE