linter-shellcheck icon indicating copy to clipboard operation
linter-shellcheck copied to clipboard

shellcheck crash when starting atom.io - inter-registry.js:155

Open Pickacho opened this issue 7 years ago • 3 comments

C:\Users\*Myusername*\.atom\packages\linter\lib\linter-registry.js:155 [Linter] Error running ShellCheck Error: Failed to spawn command `shellcheck`. Make sure `shellcheck` is installed and on your PATH
    at C:\Users\*Myusername*\.atom\packages\linter-shellcheck\node_modules\atom-linter\lib\helpers.js:130:24
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

Pickacho avatar Jan 16 '19 06:01 Pickacho

As explained in the Installation section of the README, you need to have shellcheck installed on your system before you can use it in Atom through this package.

Arcanemagus avatar Jan 16 '19 06:01 Arcanemagus

Dear Landon,

Thank you for your answer,

I have performed the installation of Linter-shellcheck package by scoop and received -"Done" Also tried again by installing using the Atom package manager , same error every time. What logs you need?

On Wed, Jan 16, 2019, 08:34 Landon Abney <[email protected] wrote:

As explained in the Installation section https://github.com/AtomLinter/linter-shellcheck#installation of the README, you need to have shellcheck installed on your system before you can use it in Atom through this package.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/AtomLinter/linter-shellcheck/issues/129#issuecomment-454668376, or mute the thread https://github.com/notifications/unsubscribe-auth/AnBGIGJSDm5HCYBOjrnCgpK88_WDU49wks5vDsfugaJpZM4aCZle .

Pickacho avatar Jan 16 '19 07:01 Pickacho

Has this scoop package manager added the location it installed shellcheck to into your %PATH%? You should be able to open a Command Prompt and run where.exe shellcheck and get the location where it is installed.

You might need to close the shell and re-open it for that to work.

If it is returning a path there the next thing to try would be to close all instances of Atom, then opening a new one.

Arcanemagus avatar Jan 16 '19 08:01 Arcanemagus