Comment on Some people just can't place themselves

ArcaneSlime@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

• regular_human@lemmy.world ⁨1⁩ ⁨year⁩ ago

  For loops in scripting languages like bash should be a punishment. Try out something like python

  source
• coloredgrayscale@programming.dev ⁨1⁩ ⁨year⁩ ago

  Don’t let yourself down because you don’t know the syntax off the top of your head.

  Even after 15 years of programming, and studying computer science, I would have to look up how to write loops, conditions, variable assignments in bash / sh / batch.

  Coming to python from a primarily java focus background wasn’t any different. I knew what steps the program should do, but had to look up how to translate it into whatever language. And for further improvements what features the language has to express the things “in the style of the language”

  source

  • ArcaneSlime@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

    Thanks, that encouragement is definitely helpful, it felt like I was struggling with something most programmers would consider should be mastered day 1, right after lunch because hello world is before lunch haha. Glad to know people still have to look it up even after a while sometimes.

    source
• joyjoy@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Is your issue about just syntax?

  for part in $text; do
    echo "xX$partXx"
  done
  

  In bash, this loops over each word in a variable. If you want each line, you’ll need to use a while read loop instead.

  while read -r line; do
    echo "xX$lineXx"
  done <<< "$text"
  

  source

  • ArcaneSlime@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

    I think my issue may be more than just syntax, I really am inexperienced lol, all just learning as I go (unix philosophy and all lol, I kid).

    The for loop I stole from the internet for use with ffmpeg is

    for i in *$input; do ffmpeg -i “$i” “${i%.*}$output”; done

    So I know what it does, it takes the input (read by the script earlier) filetype and changes it to the output filetype also read earlier for all of the files of $input type in the current directory, and I know how I got input and output as variables, and I know the ffmpeg -i foo -o bar command, but I get completely lost on “$i” “${i%.*}$output”;. I don’t really understand when to use what brackets or where I need semicolons and why, though I do understand that $ calls a variable and * is an operator to designate “all,” I’m not entirely sure what this part of my script is doing (as this loop is the part I copied from stackexchange, and only half understood it “but it worked so fuck it” lol.)

    source

    • joyjoy@lemmy.world ⁨1⁩ ⁨year⁩ ago

      The ${} syntax manipulates a variable. In this instance, I believe % removes a suffix. # is for a prefix. I can never remember which is which.

      Semicolons just separate statements. You can replace them with a new line to get the same effect.

      source

      • ArcaneSlime@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

        Thanks for the info, it definitely helped!

        source