Xavier Delaruelle

Thanks for this report. Could you please detail how `shellcheck` was run to obtain this report. Many files checked in the above report are modulefiles or module collection, not shell...

Never mind my previous comment. I have checked the whole repository and find the files to check with `shellcheck`: ``` script/add.modules.in script/commit-msg script/envml script/mkroot script/modulecmd.in script/mt script/pre-commit configure init/bash_completion.in init/profile.sh.in...

On my side, I will create a new *lint* testsuite that will be callable with `make testlint` or `script/mt lint`. It will detect all the script shells in the repository...

No problem @lzaoral. I am closing this issue, as the work achieved for next version (5.2) on this topic is already a good step forward. But do not hesitate to...

Hi @wenzler Do you mean to get `0` exit code and the end of modulecmd.tcl code evaluation even if an error occurs ? For instance: ```console $ module load unknown_module...

In `siteconfig.tcl` you may set the `false_rendered` state to indicate the shell code for exit code has already been produced: ```tcl setState false_rendered 1 ```

> Maybe something for the cookbook then? > etc/siteconfig.tcl: > > if {[info exists ::env(MODULES_NO_EXITCODES)]} { > setState false_rendered 1 > } This is not something I will work on,...

Nice idea. I would suggest to have a `configure` option for it: `--enable-relocatable` ([seems to be](https://www.manpagez.com/info/relocatable/) the most common name for this). When set, the paths that are replaced in...

@RobyB I suggested to have a configure option as from my understanding relocatable installation goes against reproducible installation where people want to fully qualify every paths. @zerothi `DESTDIR` is already...

Additionnal details on this [message](https://sourceforge.net/p/modules/mailman/message/36771270/)