ShellCheck VS efm-langserver

https://www.shellcheck.net/ https://github.com/koalaman/shellcheck

not sure about unit/functional testing, but https://www.shellcheck.net/ is handy for linting and finding bad practice.

First, how did ShellSheck didn't give you warnings, if you checked it?

BTW, check out https://www.shellcheck.net/. You can install it to your computer and it'll warn you about this and many other ways you can accidentally shoot at your own foot with Bash.

This is super easy but, may not always be enough.. Luckily, the fine people at ShellCheck gave this some thought and created a nifty tool. It’s got a nice README, is available via most decent package managers and, even has a web interface where you can test snippets (in case you’re bored and on the tube, I guess). The README also includes a Gallery of bad code to showcase some of the stuff shellcheck can pick up on.

Bash because it's everywhere and I've put effort into learning it properly. My scripts almost always pass shellcheck first try, and I know the syntax of bash-specific features reasonably well. I don't see any advantage to learning another shell which I need to explicitly install and relearn all over again.

The Prompt logic could include some nuance to flag potentially harmful commands, but it would still be potentially fallible. However, you raise an excellent point, and value can be added by altering the workflow to run the results through a tool like shellcheck, where you can customize acceptable BASH commands.

Idea: Incorporate shellcheck that repeats the code back to the bot until it passes shellcheck at least.

A good way to learn the finicky bits is to run all your scripts through shellcheck. (Better yet, find a plugin for your editor/IDE.) If it flags an issue, read the corresponding wiki page and see if you understand it.

Have you run them through shellcheck? https://www.shellcheck.net/

I use the LSP if it supports formatting. I supplement that with efm-langserver which interfaces with CLI formatters and linters. It works well, similar to null-ls as I understand it.

As far as I know, the only solution (other than getting formatting directly from a LSP server) is to use EFM (https://github.com/mattn/efm-langserver), which implements the tricky logic of figuring out how to only update the changed text.

There's also efm which wraps linters into an LSP server which can then communicate with nvim.

Since I'm using efm-language server with configured `misspell tool. However, this just suggest the incorrect word for the buffer. I

Note that there are also other implementations of such a multipurpose language server like the efm-langserver. While efm works for any editor/tool that uses language servers, Null-ls is a optimized solution only for NeoVim.

money! thank you for this. I was looking for answers [here](https://github.com/mattn/efm-langserver) , forgot about [this](https://github.com/neovim/nvim-lspconfig/blob/master/doc/server\_configurations.md#efm)

I see that prettierd is an option to fix this issue, but do I have to go get efm-langserver or can I just replace prettier w/ prettierd and it just works?

I've only just come across them, but I assume this could theoretically be achieved with https://github.com/mattn/efm-langserver and https://github.com/jose-elias-alvarez/null-ls.nvim

Hi! I've been trying to make golangci-lint to be used with lspconfig via https://github.com/mattn/efm-langserver