• Dynamic variable naming.
• Internal variables.
• Turn the non-functions into functions.
  • This is so tests can be written.
  • It also shows a working use case for the task.
• Add a CONTRIBUTING.md.
• Look into side effects of using shopt and set.
• /dev/tcp
• Convert to pdf
  • Add a cover.
  • Add references.
• Write some

I am wondering if autoenv could not be used in complex CI environments where we have multiple steps and where we need to save/restore status between different steps.

We are currently doing appending variables inside some env_jenkins.properties files and on some some steps (builders) and on others we do source env_jenkins.properties in order to load them.

If autoenv would work also for

👷 Bash/Shell最佳实践与安全编程

• Google Shell Style Guide
  • https://google.github.io/styleguide/shell.xml
  • 中文版 https://zh-google-styleguide.readthedocs.io/en/latest/google-shell-styleguide/background/
• 编写可靠shell脚本的八个建议
  https://www.xshell.net/shell/1577.html
• Bash Pitfalls: 编程易犯的错误 - 团子的小窝
  • http://kodango.com/bash-pitfalls-part-1
  • http://kodango.com/bash-pitfal

In trying to add a project to bpkg, I had to pull materials from several sources (n.b. I'm still not sure that this list is complete/correct):

• package details section was the only place I found that referenced exactly what a project needed to be compatible with bpkg
• submission instructions told me how to get my packa

The Slax URL which explains the boot internals is here:

https://www.slax.org/internals.php

The corresponding URL in the tutorials should be updated. Also, the websites should be updated (put the new tutorial document) as well in order to reflect this change.

Dash allows users to contribute docsets, as outlined in zealdocs/zeal#170. dasht should provide a command to automatically download and extract these as well.

(See also #4.)

Currently ARG_OPTIONAL_BOOLEAN is displayed like so:

$ ./foo.sh --help
foo!
Usage: ./foo.sh [--(no-)no-deps]
-n,--no-deps,--no-no-deps: some description

With many of those the negating (no-) text adds a lot of visual noise and can be borderline silly as in the above case. I would imagine that most people have no use for an option flag that equals the application's default va

In the docs it says:

This plugin allows you to run any shell commands before or after webpack builds. This will work for both webpack and webpack-dev-server.

maybe it could specify it works with webpack --watch too?

For instance, there are a few tests that Dash does not pass and that are probably issues that we should report. It would be nice to have an automated way to test any program against the test suite (without checking the JSON, obviously).