sh
diagnostic-languageserver
sh | diagnostic-languageserver | |
---|---|---|
21 | 16 | |
6,790 | 405 | |
- | - | |
7.6 | 1.6 | |
5 days ago | 3 months ago | |
Go | TypeScript | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sh
-
Show HN: Hucksh – A Shell with a Good Memory
* The shell itself is https://github.com/mvdan/sh, a bash-like command interpreter
-
Pure Bash Bible
https://github.com/mvdan/sh
And finally, checkbashisms if you intend on making pure posix scripts that are compatible with debian/ubuntu's dash. It is part of the debian's devscripts suite, but is often individually packaged in other distros.
> Also you can use the chat as a learning tool
Or you could learn from a guide written by people who have suffered decades of experience of the pitfalls of shell scripting and have shared their woes.
https://mywiki.wooledge.org/BashGuide
- Shfmt – format shell programs
- Shfmt – format shell programs (like gofmt, rustfmt)
-
Gofumpt: It's like gofmt except more strict
My bad, I completely screwed this up... the as of yet undiscussed project is:
https://github.com/mvdan/sh
(not shmfmt)
-
Gosh Linux shell written in Golang
I support projects like this for purposes of exploration and practice. But don't expect people to use it when there are already well established projects out there like: https://github.com/mvdan/sh
- mvdan/sh: A shell parser, formatter, and interpreter with bash support; includes shfmt
-
similar to shellcheck?
There are also: - shfmt - sh - bash language server - bashate
- shfmt - formatting comments issue
-
Indenting piped shell expressions in a script?
I also like running shfmt over my shell scripts so they all look the same without me having to think about whitespace.
diagnostic-languageserver
-
Vim - Using clippy as a linter
I'm not using the rust-analyzer plugin actually. I'm using the system installed rust-analyzer and diagnostic-language-server which integrates it with vim. Is there a flag or something to make rust-analyzer return clippy results as well?
-
diagnosticls-configs-nvim - pre-defined linter and formatter configs for diagnostic-languageserver
For those who use diagnostic-languageserver, this plugin provides a list of pre-defined configurations for you to use without the hassle to figure out the config on your own. Making it easier to integrate with less code.
- How to determine which linter is currently being used?
-
Eslint Lua Solution?
So reading through everyones suggestions it seems like diagnosticls is the way to go. Looks like this is the official neovim solution https://github.com/iamcco/diagnostic-languageserver formerly https://github.com/nvim-lua/diagnostic-nvim
-
Config to edit bash scripts with fancy LSP features, linting and formatting
Does anybody have such? Maybe you could share your experience? I use coc.nvim. My eyes fell on these 3 tools. The first one is language server and it has coc extensions coc-sh. But others are not so I am not sure which vim plugin should I use to hook them up: besides diagnostic-languageserver there are syntastic and neomake - bash-language-server - shellcheck - shfmt
-
Neovim LSP and typescript
>https://github.com/iamcco/diagnostic-languageserver
-
TypeScript: ESLint code actions and (experimental) diagnostics / formatting
I also added 2 experimental features designed to reduce the amount of boilerplate required to get a functional TypeScript development environment. diagnostic-languageserver and efm-langserver are powerful, but they can be tough to set up for new users, so I wanted to implement low-config, out-of-the-box alternatives for formatting and linting:
-
Losing my mind with formatting
I’ve personally never gotten efm to work at all, and I never figured out why (much like your situation). I use diagnostic-languageserver, which worked like a charm the first time. I’ve heard some users say it’s slower (TypeScript versus Go), but I’ve never had any speed issues.
-
Neovim - Why I'm switching to Native LSP over CoC
Aside from that, the biggest difference versus CoC is the ecosystem, which affects setup / tweaking time and code actions. I was able to set up ESLint diagnostics with diagnostic-languageserver, but it doesn't integrate with typescript-language-server at all, and I haven't been able to set up ESLint fixing + Prettier, either, All of that is trivial with CoC.
-
LSP and pylama…
Some LSP like diagnostic language server and efm language server do that for you. However, you will need to do some manual setup yourself for pylama to work with them, unfortunately, I don't see either of them have an example for pylama so you will have to write one yourself for those LSP servers.
What are some alternatives?
bat - A cat(1) clone with wings.
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
ShellCheck - ShellCheck, a static analysis tool for shell scripts
nvim-lspconfig - Quickstart configs for Nvim LSP
go-pkg-xmlx
efm-langserver - General purpose Language Server
go-pkg-rss
coc-spell-checker - A basic spell checker that works well with camelCase code for (Neo)vim
inject
neomake - Asynchronous linting and make framework for Neovim/Vim
toml - TOML parser for Golang with reflection.
syntastic - Syntax checking hacks for vim