64
all 33 comments
sorted by: hot top controversial new old
[-] thingsiplay@kbin.social 60 points 1 year ago
[-] bloopernova@programming.dev 13 points 1 year ago* (last edited 1 year ago)

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

[-] thingsiplay@kbin.social 8 points 1 year 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 4 points 1 year 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.

[-] gamma@programming.dev 6 points 1 year ago* (last edited 1 year ago)
[-] bloopernova@programming.dev 3 points 1 year ago

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

I'll edit my comment.

[-] drew_belloc@programming.dev 5 points 1 year ago

This is the way

[-] Simulation6@sopuli.xyz 4 points 1 year ago

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

[-] gamma@programming.dev 3 points 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]'.
[-] thingsiplay@kbin.social 3 points 1 year 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 1 points 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@programming.dev 1 points 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.

[-] brennesel@feddit.de 3 points 1 year ago

This is the right way

[-] ilega_dh@feddit.nl 39 points 1 year ago

find “$(echo $HOME > variable_holder.txt && cat variable_holder.txt)/$(cat alphabet.txt | grep “d”) $(cat alphabet.txt | grep “o”)$(cat alphabet.txt | grep “c”)$(cat alphabet.txt | grep “s”)”

This is the easiest method

[-] igorlogius@lemmy.world 7 points 1 year ago
[-] eager_eagle@lemmy.world 7 points 1 year ago

when you're paid by character written

[-] ale@lemmy.world 5 points 1 year ago

This really enterprises my bash.

[-] thingsiplay@kbin.social 3 points 1 year ago* (last edited 1 year ago)

@ilega_dh You don't need cat in cases when grep "d" alphabet.txt can read from file too. Edit: But obviously your comment was more of a joke to over complicate it. So never mind then.

[-] gendulf@kbin.social 3 points 1 year ago

To be safe, should probably output grep to a file, then cat that.

[-] ilega_dh@feddit.nl 2 points 1 year ago

Agreed. Everything in Linux is a file so let’s keep it that way.

[-] monsterpiece42@reddthat.com 1 points 1 year ago

What should I search to better understand what is written here? Don't mind learning myself, just looking for the correct keywords. Thanks!

[-] marcos@lemmy.world 2 points 1 year ago

Read the Bash manual. That one patter on the GP is called "Command Substitution", you can search for it.

[-] oneiros@lemmy.blahaj.zone 2 points 1 year ago

This comment is a joke and you wouldn't want to do it like that in reality, but here are some related keywords you could look up: "Unix cat", "Unix pipeline", "grep", "output redirection", "command substitution".

[-] monsterpiece42@reddthat.com 1 points 1 year ago

Perfect, I have some light reading for the evening!

[-] key@lemmy.keychat.org 17 points 1 year ago

First one, then the other, then I forget the quotes, then I put them in single quotes by accident, then I utilize that "default value" colon syntax in case I'm missing HOME , then I just stick to ~ for the rest of the file.

[-] gamma@programming.dev 6 points 1 year ago* (last edited 1 year ago)

Typically find "$HOME/docs", but with a few caveats:

  • In Zsh or Fish, the quotes are unnecessary: find $HOME/docs

  • If I'm using anything potentially destructive: mv "${HOME:?}/bin" ...

  • Of course, if it's followed by a valid identifier character, I'll add braces: "${basename}_$num.txt"

[-] karlhungus@lemmy.ca 5 points 1 year ago
this post was submitted on 26 Aug 2023
64 points (94.4% liked)

Programming

16971 readers
267 users here now

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



founded 1 year ago
MODERATORS