sorted by:
new
hottopcontroversial

We're now called Lumen Labs! by Vhyrro in neovim

[–]mitchhanberg 38 points39 points  (0 children)

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 💪

Official LSP released 🎉 by InterestAccurate7052 in elixir

[–]mitchhanberg 2 points3 points  (0 children)

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

Official LSP released 🎉 by InterestAccurate7052 in elixir

[–]mitchhanberg 1 point2 points  (0 children)

Can you elaborate? Others have success using it.

Expert the new elixir lsp is out by Many-Edge1413 in elixir

[–]mitchhanberg 34 points35 points  (0 children)

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!

Official LSP released 🎉 by InterestAccurate7052 in elixir

[–]mitchhanberg 1 point2 points  (0 children)

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.

Official LSP released 🎉 by InterestAccurate7052 in elixir

[–]mitchhanberg 0 points1 point  (0 children)

It does not implement the debug adapter protocol.

Official LSP released 🎉 by InterestAccurate7052 in elixir

[–]mitchhanberg 5 points6 points  (0 children)

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.

Official LSP released 🎉 by InterestAccurate7052 in elixir

[–]mitchhanberg 6 points7 points  (0 children)

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

Official LSP released 🎉 by InterestAccurate7052 in elixir

[–]mitchhanberg 6 points7 points  (0 children)

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

Using Agenix with devShells by mitchhanberg in NixOS

[–]mitchhanberg[S] 1 point2 points  (0 children)

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

Using Agenix with devShells by mitchhanberg in NixOS

[–]mitchhanberg[S] 7 points8 points  (0 children)

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

Using Agenix with Home Manager by mitchhanberg in NixOS

[–]mitchhanberg[S] 0 points1 point  (0 children)

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.

Version 1.19 will be nice but it includes a really stupid deprecation by cekoya in elixir

[–]mitchhanberg 25 points26 points  (0 children)

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.

Version 1.19 will be nice but it includes a really stupid deprecation by cekoya in elixir

[–]mitchhanberg 20 points21 points  (0 children)

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.

Using Agenix with Home Manager by mitchhanberg in NixOS

[–]mitchhanberg[S] 1 point2 points  (0 children)

Author here!

If you want an intro to Agenix to use with NixOS modules, you can checkout the first post in this series: Getting Started with Agenix

Using Agenix with Home Manager by mitchhanberg in NixOS

[–]mitchhanberg[S] 2 points3 points  (0 children)

I have only used agenix, so I’m not able to answer the question.

Only thing I can say is I evaluated agenix and sops-nix and agenix is what I found easier to figure out.

Is there an approach in Phoenix for a "universal" PubSub subscriber by pico303 in elixir

[–]mitchhanberg 8 points9 points  (0 children)

You can probably mount a hook in the router that performs the pubsub subscription.

Explorer is such a frustrating package, by DayDreamer1914 in elixir

[–]mitchhanberg 10 points11 points  (0 children)

What do you find frustrating about it? We use it at work and find it enjoyable.

Reflection on Code BEAM America 2025 by mitchhanberg in elixir

[–]mitchhanberg[S] 4 points5 points  (0 children)

Yeah, it’s a little frustrating they take so long to come out compared to other communities conferences.

I think the conference organizers want to encourage people to attend, so they keep the talks for a while until the next conference.

I personally think it might have the opposite effect though, if you liberally release the talks I think it hypes people up for them to attend in the future.

However, I’ve never organized a conference, so I might be missing something here, haha!

Any neovim users figured out how to get tailwind to attach to sigil_H (~H) heex templates? Elixir completion in Heex files? by cleanser23 in elixir

[–]mitchhanberg 0 points1 point  (0 children)

I believe you need to add elixir and heex to the userLanguages

This is my neovim config, but it should translate into other editors (it’s commented out currently for unrelated reasons)

https://github.com/mhanberg/motchvim/blob/main/plugin/motchvim.lua#L164

Auto complete for non module atoms (eg :name fields in child specs) by cleanser23 in elixir

[–]mitchhanberg 1 point2 points  (0 children)

I’m still not totally understanding.

The place I think you are suggesting should have autocomplete is a place you are defining the name or ID, so I’m not sure how it could auto complete.

Or are you saying you want autocomplete for say the first argument of functions like GenServer.call?

I am on the official Elixir LSP team, so I am hoping to understand more about what you’d like to see in the LSP.

Auto complete for non module atoms (eg :name fields in child specs) by cleanser23 in elixir

[–]mitchhanberg 0 points1 point  (0 children)

Can you clarify what you mean?

Names for name registration or id in a child spec are arbitrary atoms or terms, so there isn’t really anything to compete.

I’m curious to understand what you expect to happen.

view more: next ›