Re:Being a bash developer in the 21st century
by wodenokoto on Friday September 22, 2023 @04:39AM
(#37609524)
I don't know which editor you are using, but the shellcheck plugin for VS Code works really well. Underlines warnings and errors, and on hover gives you a short description and a link to a long description. There's also a "fix" button, but I it only works for the simplest of cases.
[ Parent
| on HN ]
Re:Being a bash developer in the 21st century
by keepamovin on Friday September 22, 2023 @06:06AM
(#37610102)
Oh, I use vim. And I don't really know about any plugins that work.
But I would try VS Code just to go through my shell files with shellcheck! :)
Re:Being a bash developer in the 21st century
by marcelarie on Friday September 22, 2023 @06:28AM
(#37610258)
you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)
here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...
Re:Being a bash developer in the 21st century
by keepamovin on Friday September 22, 2023 @06:39AM
(#37610323)
Thanks, for the link, man! Helpful. Is nvim, like, command line? I don't like to be in GUI when I'm coding. I mean I guess I could hook up my Quake style iTerm2 dropdown overlay to display a GUI window (but I think that only works on Windows with ConEmu). It's just easier for me to stay in command line, switch to GUI to eval or research...or watch videos! Haha
Re:Being a bash developer in the 21st century
by llimllib on Friday September 22, 2023 @07:19AM
(#37610548)
nvim is a fork of vim, so yes it’s a command line editor
Re:Being a bash developer in the 21st century
by keepamovin on Friday September 22, 2023 @07:28AM
(#37610617)
Cool! Will give a try.