I use Jetbrains' PHPStorm as my primary editor for any digital project and have been since mid-2017. It's an all round solid editor, especially useful when working with WordPress projects and I've found it a bit more powerful than VSCode but one thing that really gets on my nerves with it is that every time the application updates my CLI launcher script breaks.
Ironically when this happened it was announced as a feature via their Toolbox announcement post however I find this just another flaky feature, alongside the random spikes of CPU and network the app uses (I often just force close it when I have work to do).
There is an issue being tracked for this however it's still less intuitive than the previous
Tools > Create Command-line launcher method implemented previously. After a little digging and some annoying application behaviour involving version numbers I found the reason why this happens and with it, the solution to my first-world development problem.
I use the
pstorm command to open things in my editor. Much like code works for VSCode:
$ pstorm ./path-to-project-dir
The bash script that runs when I execute my
/usr/local/bin/pstorm) command looks like this:
open -a "/Users/james/Library/Application Support/JetBrains/Toolbox/apps/PhpStorm/ch-0/191.7141.52/PhpStorm.app/Contents/MacOS/phpstorm" "$@"
So here we can see this lovely version number looking thing following the
/ch-0/. This is what changes for each new version of the application. As we're using this in the path it breaks as soon as that old version is replaced with the new one. Yay for using version numbers as a directory and not using something like
/@latest/ or something similar.
Just a note as you'll need to add the
/Contents/MacOS/phpstormsegment after the path you copied as this is the executable that will ingest the file path provided by the CLI.
As our bash script is still using the previous version number we need a way to find the new version number and replace it in the launcher.
- To find this path open the JetBrains toolbox find the application that is being a nightmare.
- Click on the little gear icon, and open up the settings page. On this page there is a section displaying the install location path.
- Copy this path by dragging the application to your terminal window or by adding this nifty right click copy-path option utility I wrote.
- Copy the new version number between the
PhpStorm.appsegments and replace the previous on in our bash script (
/usr/local/bin/pstorm) save and exit and we're done. The CLI launcher now behaves itself again!