yyx990803 / launch-editor

Open file in editor from Node.js.
MIT License
568 stars 65 forks source link

Cannot open components with webstorm: spawn webstorm ENOENT. #9

Open bokub opened 6 years ago

bokub commented 6 years ago

I'm using launch-editor with webpack.

When I try to open a component in Webstorm, the following message is displayed in the dev-server console:

Could not open App.vue in the editor.
The editor process exited with an error: spawn webstorm ENOENT.

The browser console says File src/vue/App.vue opened in editor, and it works well with other editors so I guess it's well configured.

Any idea how to fix this ? Thanks

Amorites commented 6 years ago

solved by https://github.com/yyx990803/launch-editor/issues/4#issuecomment-359348189

bokub commented 6 years ago

Helps a little bit but it still doesn't work completely

After doing what's suggested in #4 , I can run webstorm myFile.vue, and it works great.

However, using your plugin, the file is opened with vim in the 'Terminal' tab of WebStorm, it's very strange... image

jdf221 commented 3 years ago

3 years late here but for anyone who may come across this from Google trying to fix that vim issue.

If you set the env variable EDITOR="webstorm" it will open as expected. On Mac I've added this to my .zshrc:

# Adds support for various open in editor features in tools
export EDITOR="webstorm"
if [[ "$__CFBundleIdentifier" == com.jetbrains.* ]]
then
  # Removes "com.jetbrains." from the beginning of string
  # Then removes "-EAP" from end of string if needed
  export EDITOR="${${__CFBundleIdentifier#"com.jetbrains."}%"-EAP"}"
fi

Should detect which JetBrains tool you're using and set it accordingly. (Defaulting to webstorm)

If you only need Webstorm support you can add the env variable in the Terminal preferences inside Webstorm.

Note: You may need to setup the shell script command launcher for the relevant program. I use JetBrains Toolbox so they're generated automatically in my path. https://www.jetbrains.com/help/webstorm/working-with-the-ide-features-from-command-line.html

icacho commented 2 years ago

3 years late here but for anyone who may come across this from Google trying to fix that vim issue.

If you set the env variable EDITOR="webstorm" it will open as expected. On Mac I've added this to my .zshrc:

# Adds support for various open in editor features in tools
export EDITOR="webstorm"
if [[ "$__CFBundleIdentifier" == com.jetbrains.* ]]
then
  # Removes "com.jetbrains." from the beginning of string
  # Then removes "-EAP" from end of string if needed
  export EDITOR="${${__CFBundleIdentifier#"com.jetbrains."}%"-EAP"}"
fi

Should detect which JetBrains tool you're using and set it accordingly. (Defaulting to webstorm)

If you only need Webstorm support you can add the env variable in the Terminal preferences inside Webstorm.

@jdf221 I'd tip my hat to you sir, I've been fighting this issue since day-1 with macOS+Webstorm, your solution works like a charm (tested using Webstorm 2021.2 | error msg before: Error: spawn docker ENOENT)

vjpr commented 5 months ago

Issue is that Jetbrains toolbox seems to use shell scripts shims/wrappers that run the binary.

launch-editor expects a binary.

launch-editor should handle shell scripts.