Quote:
Originally Posted by GeoffR
Thanks for the suggestion, I've attached a Bash version of the patching script with those changes, if anyone using a Mac or Linux wants to test it, just unzip bash_test_4049298.zip so that the file 4.4.9298.bash is in the same directory as the 4.4.9298.sh file, and then patch in the normal way but executing 4.4.9298.bash instead of 4.4.9298.sh.
For those who test it, I'd be interested to know if you are able to run the script successfully just by double-clicking on it from your desktop / file explorer. Delete or rename the 4.4.9298_target directory before each test to easily see if a new one is being generated, and please let me know:
1. Your operating system and desktop environment
2. Does double-clicking on the original 4.4.9298.sh script work?
3. Does double-clicking on the new 4.4.9298.bash script work?
4. Did you have to make any changes to your operating system / desktop environment defaults to make it work?
E.g. for me:
1. Debian 7 (Wheezy) / Gnome 3.4
2. yes
3. yes
4. no changes needed.
1. Debian 8 (Jessie) / Gnome 3.14
2. yes
3. yes
4. Had to change default Nautilus settings: Preferences > Behavior > Run executable text files when they are opened.
Edit: Attached new version bash_test_4049298_v2.zip that creates a logfile of all output.
|
1. Ubuntu 17.04
2. yes
3. yes
4. enable ask to open executable files in nautilus
1. Ubuntu GNOME 16.04
2. yes
3. yes
4. enable ask to open executable files in nautilus
1. Debian Sid with GNOME
2. yes
3. yes
4. enable ask to open executable files in nautilus
1. Fedora 25 GNOME
2. yes
3. yes
4. enable ask to open executable files in nautilus
1. Debian Sid XFCE
2. yes
3. yes
4. This will only work on Thunar 1.6.6 and over on XFCE 4.12 and over: xfconf-query --channel thunar --property /misc-exec-shell-scripts-by-default --create --type bool --set true
Also, the script should still be a .sh, even though it is a bash script.