This could just be one sed command:
echo $line | sed -E 's/TH|[EL ]|DO//g'i guess you
sedbetter than i do. smh. the syntax in the screenshot is the only syntax i’ve ever had to use. i should definitely start reading the mans.EDIT: actually, while your approach is more elegant, it doesn’t capture what happened in the scene. Hodor doesn’t immediately go from “HOLD THE DOOR” to “HODOR”, there are multiple iterations and it gets less intelligible with each one
no pipe necessary, just
sed -E 's/TH|[EL ]|DO//g' <<<"$line"No
sednecessary withextglobenabled:echo ${line//@(TH|[EL ]|DO)/}I was waiting for someone to come along with this response lmao
I’m terrible at remembering shell string operation syntax, but this is the ultimate answer.
Definitely not the ultimate, since it’s not POSIX, but still a nice tidbit.
Idk, writing POSIX-compliant shell is so miserable that I avoid doing it when I can. You can use Bash on BSD and all other unixes, so it’s still a relatively portable solution.
True enough, but it’s pretty much the same to use sed, unless you need those milliseconds of performance boost.
I think I find the pipe faster to parse.
idk who downvoted you, it’s a very common sentiment. I advocate for
<<<, but a pipe is often fine when performance doesn’t matter.Performance doesn’t really matter with any of my scripts. They’re mostly for personal use.
And the even funnier thing is getting downvoted for a style preference. XD
I was thinking sed, too, but to replicate the behaviour (and scene):
echo "HOLD THE DOOR" | sed -n ' p s/E//g p s/L//g p s/TH//g p s/ //g p s/DO//g p'Note:
-nsuppresses the default printing that sed does, so I could include the lastpfor symmetry and clarity 🙂
