It is typical to use env in portable scripts to locate the executable, in this case “bash” on the users path.
#!/usr/bin/env bash
It probably should be fixed upstream.
adw632
drobban
Yeah that, but the greatest problem is the use of bash syntax but specifying (I assume) Bourne shell in the hashbang
If everything else is intended to work with sh - the upstream fix would perhaps be to use a ‘sh’ replacement for ‘<<<’-operator.
0
rsdlt
Hi there! Thanks for the guide, it was really useful. I’m relatively new to Elixir and Phoenix and I’m seriously considering them for my next big project… The ecosystem looks fantastic!
Anyways, if someone is using credo for linting I’d recommend using the nvim packages "mfussenegger/nvim-lint", "dgagn/diagflow.nvim" and "folke/trouble.nvim".
Together they provide a very nice coding experience.
0
arcanemachine
I’ve never heard of any of these packages. I’m going to look into them, but would you mind explaining why they are particularly useful when paired with Credo?
https://github.com/mfussenegger/nvim-lint
https://github.com/dgagn/diagflow.nvim
https://github.com/folke/trouble.nvim
EDIT: So I use coc.nvim and coc-elixir. I’ve been looking to ditch CoC for a while (because why have some bloated npm mess running in the background when I could avoid that), but it’s already set up so so I’ve kept it around. Plus, holy hell are there ever a lot of neo/vim plugins related to LSP/IDE stuff.
1
rsdlt
nvim-lintyou can manage all your linters andcredois on the list of supported ones.
diagflowprovides a very nice UI to expose nvim’svirtual_text(text for diagnostics from the linterns / LSPs).troubleis great for showing in one place all your diagnostics.
This is how it looks on my setup:
Cheers
3
hubertlepicki
And I just switched from LazyVim to LunarVim and I think I like it more. It’s uzing Lazy.nvim as a plugin manager but it’s coming with less by default, less keymappings and plugins enabled and more vanilla Vim experience.
I’m sorry, but after 20 years of using mostly plain Vim, the default keybindings are embedded. LazyVim does too much. Also, LunarVim’s documentation is superior, the whole Lua thing is new to me and it’s been super helpful together with configuration videos. Also, it somehow installed Elixir language server on it’s own when I opened elixir file for the first time, it just works.
You can say I’m too lazy for LazyVim
1
linusdm
Haha, nice!
I actually switched the other way around two weeks ago. It seemed to me that LunarVim does more magic behind the scenes than LazyVim. But I can be wrong. It’s interesting to see the set of plugins being chosen, which helps developing your own taste on the matter.
Even more interesting than the difference between Lunar and Lazy was my discovery of the NVIM_APPNAME environment variable. It allows you to switch between vim distro’s easily, without moving your config files back and forth.
This is the magic behind how LunarVim isolates its own config, using the lvim command (instead of the default nvim binary).
This blogpost does a good job at explaining how this works: Switching configs in Neovim • Michael Uloth
The neovim documentation about the variable: https://neovim.io/doc/user/starting/ (afaik this was a new feature since last year).
This will lower the bar for trying even anotother vim flavour (like kickstart for example).
4
hubertlepicki
oh, nice tip, I’ll try it on the next switch. I already nuked my LazyVim setup, unfortunately, I’m too impulsive. 
But the set up kinda works out of the box for Elixir. I just added a few treesitter plugins and Copilot one within config.lua and I am happy for now:
lvim.builtin.treesitter.ensure_installed = { "comment", "markdown_inline", "regex", "eex", "elixir", "heex", "surface", "erlang", "html", "graphql" }
Also, I’m doing this b/c I will mess it up otherwise
alias vim=“nvim”
1
adw632
I did the opposite of that over a year ago. LunarVim was a nightmare compared to the clean configuration and control of LazyVim.
I also much prefer the documentation of LazyVim by far, it is completely transparent and well documented. Every plugin and it’s default configuration is clearly defined.
If I was to do it myself I couldn’t imagine it being much different than what lazy does. No magic, explicit plugin configuration and not inventing a separate config system on top.
1
hubertlepicki
we’ll see how it goes. I got tired disabling LazyVim features over and over again. Less is more.
1