You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2020. It is now read-only.
Followed the steps and was able to partly reproduce the issue only if uninstalled previously installed version of the plugin and restart.
In details: after installing EAP and restarting PhpStorm, existing non-sh files with shebang and underscore in the name weren't highlighted, called the action to generate the report (result on the screenshot). Copied one of those files to a new file (also non-sh and named with underscore) and selected a Bourne Again Shell in appeared "Register New File Type Association" dialogue, suddenly all files (existing and the new) were highlighted. The same trick worked with the stable version. I wasn't able to reproduce this issue with the new file shell file and renaming existing.
I may be mistaken here but I think there was no "Register New File Type Association" dialogue on the copying before. I may have applied PhpStorm patch or something since the origial post
PhpStorm 2018.2.1
Build #PS-182.3911.43, built on August 8, 2018
JRE: 1.8.0_152-release-1248-b8 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
PHPStorm 2018.2.1
BashSupport 1.6.13.182
How to reproduce:
#!/usr/bin/env bash
).sh
from filenameIt's a commong thing to have no extensions for bash script when they placed to bin/.
The text was updated successfully, but these errors were encountered: