Backup diff of Shell vs current(No. 3)

• Backup list
• View the diff.
• View the diff for visual.
• View the source.
• View the backup.
• Go to Shell.
  • 1 (2010-11-08 (Mon) 16:56:28)
  • 2 (2021-12-29 (Wed) 13:49:48)
  • 3 (2021-12-30 (Thu) 03:12:19)
  • 4 (2023-12-12 (Tue) 13:06:51)
  • 5 (2023-12-12 (Tue) 19:18:45)

• The added line is THIS COLOR.
• The deleted line is THIS COLOR.

- UNIX & Linux コマンド・シェルスクリプト リファレンス
--  http://www.geocities.jp/geo_sunisland/

- 【永久保存版】シェルスクリプト完全攻略ガイド
--  https://qiita.com/osw_nuco/items/a5d7173c1e443030875f

- [[Shebang]]

* ノウハウ [#n64be415]

- Tips: 実行中のシェルスクリプトを書きかえるときには
--   https://qiita.com/kitsuyui/items/d0048eeaa50293a92a60

- The first two statements of your BASH script should be…
--  https://ashishb.net/all/the-first-two-statements-of-your-bash-script-should-be/

 !/usr/bin/env bash
 set -euo pipefail
>
“set -e” which ensures that your script stops on first command failure. By default, when a command fails, BASH executes the next command. Looking at the logs, you might feel that the script executed successfully while some commands might have failed. Caveat: Be careful about applying it to existing scripts.
>
“set -u” which ensures that your script exits on the first unset variable encountered. Otherwise, bash replaces the unset variables with empty default values.
>
“set -o pipefail” which ensures that if any command in a set of piped commands failed, the overall exit status is the status of the failed command. Othe

- bash スクリプトの実行中上書き動作について
--  https://zenn.dev/mattn/articles/5af86b61004bdc