Currently, many Bash scripts in the repository are marked as executable. I wonder if we really need executable permissions for all of them.
In Linux, the executable permission is mainly useful for scripts that are intended to be run directly from the command line, e.g., ./build.sh. However, most of the Bash scripts in this repository are examples or test scripts. They are typically executed through an interpreter, e.g., bash ex01.sh. In such cases, the executable permission is not required.
Removing the executable permission can also solve the @joa-quim's issue on Windows (#9047 (comment)).
Therefore, I suggest removing executable permissions from Bash scripts that are not intended to be executed directly by users, and keeping executable permissions only for a few scripts in the GMT/bin directory.
Currently, many Bash scripts in the repository are marked as executable. I wonder if we really need executable permissions for all of them.
In Linux, the executable permission is mainly useful for scripts that are intended to be run directly from the command line, e.g.,
./build.sh. However, most of the Bash scripts in this repository are examples or test scripts. They are typically executed through an interpreter, e.g.,bash ex01.sh. In such cases, the executable permission is not required.Removing the executable permission can also solve the @joa-quim's issue on Windows (#9047 (comment)).
Therefore, I suggest removing executable permissions from Bash scripts that are not intended to be executed directly by users, and keeping executable permissions only for a few scripts in the GMT/bin directory.