Comments by "Anony Mousse" (@anon_y_mousse) on "From Zero To Hero With Bash Scripting ('While' Loops and 'If' Statements)" video.

  1. If you make a habit of it then you don't have to think about it. Spaces are especially annoying and if you've already added a " then it's simple to use one at the end and double quotes still allow you to expand shell variables and do command substitution.
    6
  2. You should do a short showing people how to make a function in the top three major shells to combine mkdir and cd into mkcd so that from then on you can just use that in the videos and point to the short for anyone confused by it.
    2
  3. Yes. You can also bind things like readline commands.
    2
  4. Either is acceptable, but `./script.sh` is easier than `bash script.sh`, and you can even use different languages for scripts and point the shebang to that runtime, such as a Python program that you wish to execute from the terminal.
    2
  5.  @XenHat  You would think every shell would've added it to the toolkit.
    1
  6.  @tatsutakamaro  You can always write a short program in C or some other language then call it from a bash script.
    1
  7.  @tatsutakamaro  Realistically that's how you should do things if you really feel the need to glue things together with bash. Implement tasks that are difficult or slower to process within bash as some compiled language binary that you call. But I would suggest just using all of one language that makes most tasks easy or more performant and can handle calling external programs if necessary.
    1