Feddit.dk
  • Communities
  • Create Post
  • Create Community
  • heart
    Support Lemmy
  • search
    Search
  • Login
  • Sign Up
zephyr@lemmy.world to Programming@programming.dev · 2 years ago

How do you shell expand your variables and why?

lemmy.world

message-square
27
link
fedilink
  • cross-posted to:
  • shell@programming.dev
63

How do you shell expand your variables and why?

lemmy.world

zephyr@lemmy.world to Programming@programming.dev · 2 years ago
message-square
27
link
fedilink
  • cross-posted to:
  • shell@programming.dev
  • thingsiplay@kbin.social
    link
    fedilink
    arrow-up
    58
    ·
    2 years ago

    @zephyr echo "${HOME}/docs"

    • bloopernova@programming.dev
      link
      fedilink
      English
      arrow-up
      12
      ·
      edit-2
      2 years ago

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

      • thingsiplay@kbin.social
        link
        fedilink
        arrow-up
        8
        ·
        2 years ago

        @bloopernova As you mention it, here the links for anyone interested: Online tool https://www.shellcheck.net/ and you can install it locally too https://github.com/koalaman/shellcheck .

        • hascat@programming.dev
          link
          fedilink
          English
          arrow-up
          4
          ·
          2 years ago

          While this looks like a handy tool, it does make me think shell scripting itself needs a cleaner approach than what we have currently.

          • thingsiplay@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            2 years ago

            deleted by creator

      • Gamma@programming.dev
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        2 years ago

        This isn’t true. Shellcheck doesn’t insist on braces unless it thinks you need them.

        • bloopernova@programming.dev
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          2 years ago

          Oh! I didn’t know that (um, obviously lol)

          I’ll edit my comment.

    • Drew Belloc@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      2 years ago

      This is the way

    • Simulation6@sopuli.xyz
      link
      fedilink
      arrow-up
      4
      ·
      2 years ago

      I also do this so the variables are more easily spotted.

    • brennesel@feddit.de
      link
      fedilink
      arrow-up
      5
      arrow-down
      2
      ·
      2 years ago

      This is the right way

    • Gamma@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 years 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]'.
      • thingsiplay@kbin.social
        link
        fedilink
        arrow-up
        3
        ·
        2 years ago

        @gamma I just use them out of consistency and principle, so I don’t need to think in which case it is required or not.

      • Cyclohexane@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        2 years 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@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 years 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.

Programming@programming.dev

programming@programming.dev

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 134 users / day
  • 1.04K users / week
  • 2.91K users / month
  • 7.05K users / 6 months
  • 55 local subscribers
  • 20.1K subscribers
  • 2.18K Posts
  • 33.2K Comments
  • Modlog
  • mods:
  • snowe@programming.dev
  • Ategon@programming.dev
  • MaungaHikoi@lemmy.nz
  • BE: 0.19.11
  • Modlog
  • Legal
  • Instances
  • Docs
  • Code
  • join-lemmy.org