• bloopernova
      link
      fedilink
      English
      arrow-up
      13
      ·
      edit-2
      1 year ago

      This is the best way. It’s also the way the Shellcheck wants sometimes recommends.

    • Gamma
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      This has never stuck with me, and I hadn’t thought about why until now. I have two reasons why I will always write ${x}_$y.z instead of ${x}_${y}.z:

      • Syntax highlighting and shellcheck have always caught the cases I need to add braces to prevent $x_ being expanded as ${x_}.
      • I write a lot of Zsh. In Zsh, braces are optional in way more cases. "$#array[3]" actually prints the length of the third item in array, rather than (Bash:) the number of positional parameters, then the string 'array[3]'.
      • Cyclohexane@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I will always write ${x}_$y.z instead of ${x}_${y}.z:

        The difference between the two seems different to what’s in the OP. Is there a typo here?

        • Gamma
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          in the OP

          My reply is to a commenter who said they prefer "${HOME}/docs" over both options in the original image ("$HOME/docs" or "$HOME"/docs). Many people prefer to always include braces around the parameter name out of consistency, instead of only when they are required.

          My comment explained why my habit is to only include braces when they are necessary.