Reduce scope to only scripts
That would simplify the installation to:
- clone repo to
some/path
- add
PATH="some/path:$PATH"
to.{ba,z}shrc
And afford users to only type script-name
to run it, same as if we would wrap scripts in functions.
What do you think, @b_freitas & @greg?
Background
I rescind my initial idea about functions rather than scripts, because our source
ing everything will have a performance penalty on each start of a new terminal.
Side effects
- The script files would need to be either in this repo's root folder, and named usefully (e.g.
SOS-full-report
) AND contain the instructions within them, or- if a rendered ReadMe should be present, those would either be in a dedicated
doc/
or/man
folder, and named the same:SOS-full-report.md
- or we continue with the idea of 1 folder per script:
SOS-full-report/run
or/script
andSOS-full-report/README.md
- if a rendered ReadMe should be present, those would either be in a dedicated
Edited by Katrin Leinweber