Comment 23 for bug 695437

Ari (ari-lp) wrote :

Recently updated to the latest Synapse revision and was surprised by this change. As a dev this change has made Synapse an absolute mine field to navigate. I have hundreds of executable scripts that I regularly work on, but that have absolutely no reason to be executed from my graphical launcher.

For instance, why would I want to launch a build script for one if my projects outside of its project directory? What if the script is lazily coded and tries to remove files it shouldn't remove?

In my opinion this change is an absolute nightmare, and I have absolutely no clue why anyone in here supported it. If you want to launch your scripts, move them to your $PATH. It has worked liked that for ages. This change goes against every launcher UX paradigm established over the past few years and is frankly incredibly dangerous.