update settings with enable_* tweaks

Author: DannyBen

src/usage/settings.md

@@ -162,25 +162,6 @@ or `-f=value`
 - `conjoined_flag_args: true` - Expand `--flag=value` to `--flag value` and `-f=value` to `-f value`.
 - `conjoined_flag_args: false` - Do not expand `--flag=value` or `-f=value` (consider this an invalid input).
 
-### `env`
-
-```yaml
-# default
-env: development
-```
-
-Specify if the generated script should include development related comments and
-functions or not.
-
-- `env: development` - Generate with file markers and development functions, such as `inspect_args()`.
-- `env: production` -  Generate a smaller script, without file markers and development functions.
-
-!!!success File Markers
-File markers are special comments that are injected to the final script and
-specify the name of the internal bashly template (view) or the path to the
-user's partial code files.
-!!!
-
 ### `partials_extension`
 
 ```yaml
@@ -224,6 +205,95 @@ all the private elements in the usage texts, as if they were public.
 
 [!button variant="primary" icon="code-review" text="Private Reveal Example"](https://github.com/DannyBen/bashly/tree/master/examples/private-reveal#readme)
 
+### `env`
+
+```yaml
+# default
+env: development
+```
+
+Specify one of two script rendering environments:
+
+- `env: development` - Generate a script suitable for development, which is usually slightly larger
+   and contains additional development-specific features.
+- `env: production` -  Generate a script suitable for distribution, which is usually smaller.
+
+Use the `enable_*` options below to adjust settings for each environment.
+
+!!! Note
+It is recommended to leave this set to `development` in the settings file, and
+use either the `BASHLY_ENV` environment variable or the
+`bashly generate --production` command when the slimmer production script is needed.
+!!!
+
+
+### `enable_header_comment`
+
+```yaml
+# default (allowed: always, never, development, production)
+enable_header_comment: always
+```
+
+Specify if you wish to render the "do not modify" comment at the beginning of
+the script.
+
+### `enable_bash3_bouncer`
+
+```yaml
+# default (allowed: always, never, development, production)
+enable_bash3_bouncer: always
+```
+
+Specify if you wish to render the piece of code that aborts the script execution
+when bash version is < 4.
+
+### `enable_view_markers`
+
+```yaml
+# default (allowed: always, never, development, production)
+enable_view_markers: development
+```
+
+Specify if you want the rendered script to include view marker comments.
+
+View markers provide the name of the internal bashly template (view) or the
+path to the user's partial code files in the final script, to help locate
+the source file for each piece of code.
+
+### `enable_inspect_args`
+
+```yaml
+# default (allowed: always, never, development, production)
+enable_inspect_args: development
+```
+
+Specify if you want the rendered script to include the `inspect_args()` function.
+
+The `inspect_args()` function can help in reviewing the input for each command.
+
+### `enable_deps_array`
+
+```yaml
+# default (allowed: always, never, development, production)
+enable_deps_array: always
+```
+
+Specify if you want to populate the `$deps` bash array.
+
+This is applicable only if your script uses the
+[Dependency](/configuration/dependency) configuration option.
+
+### `enable_env_var_names_array`
+
+```yaml
+# default (allowed: always, never, development, production)
+enable_env_var_names_array: always
+```
+
+Specify if you want to populate the `$env_var_names` bash array.
+
+This is applicable only if your script uses the
+[Environment Variable](/configuration/environment-variable) configuration option.
 
 ### `usage_colors`