this post was submitted on 10 Aug 2024
18 points (100.0% liked)
Programming
17364 readers
182 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't use VideoToolbox or Mac, so won't test it. But looking at the script, it looks clean and nice Bash scripting. I like it. Nothing serious but one thing I would suggest is for just a little bit easier and cleaner look in the code, to use cat with EOF for the help, like in one of my scripts:
Edit: I forgot that beehaw does not like the character for
<
and will destroy everything. So I changed them to%%
, just replace it with the less than character, the opposite of>
.Another Edit: In your build sh script, I like you hardcode
rm -rf ffmpeg_vt
, and don't use a variable for. And also checking if its a directory and exit if it can't cd intocd ffmpeg_vt/ || exit 1
. Well done.Thanks for the helpful advice! Shellcheck is the best :)
Edit: How do I get the ANSI escape colors to appear with the cat << EOF syntax?
Within cat EOF syntax you can just use variables and commands as well. Just tested it and I see the problem here. The EOF syntax will not interpret the backslash and print them literally. So those variables would require to be interpreted with echo -e first. I never used colors in this syntax before. It's up to you which syntax you prefer, some people still like the series of echos over cat EOF.