And all that just because someone decided that an array bigger that 16 bytes would have been too expensive (/s probably)

I’m almost sure the backstory to how you gained this knowledge is “i spent hours debugging something, and that 15 chars limit was the problem”

I might be a robot, I don’t know why but i can’t solve the captcha lol

I’d love to give this a try tho so maybe I’ll come back later

Just a random idea, but would you consider using anubis instead? (That new thingy that has been popping up lately, for example on the archwiki). I haven’t checked it out but I bet it’s also better on a privacy standpoint in respect to google’s captcha

There’s no shame in combining multiple tools, that’s what pipelines are all about

Not at all, but some times it’s just funny

You can select specific lines, with regex or by using a line number; or you can select multiple lines by using a comma to specify a range.

Yep, learning this made sed even more useful to me.

I also gave awk a try and now i know what i’ve missed all these years

(Also, sorry for the 12 days old reply :))

12 days late, but thanks for the bit of history, I always enjoy this stuff :)

I understand what argument could be made against musl, which is licensed under MIT, but what’s wrong with GPLv2?

I remember Torvald saying something about not wanting to change the kernel’s license to GPLv3, but I’ve never understood the differences

Are you opposed to using awk?

Not at all, I’m just not familiar with it so I find it confusing.

Although, looking at your command, i think I understand what it means

I see. I guess what confused me was that i didn’t understand what addresses were.

Thank you for your explanations :)

I meant to ask what is the difference between, i.e., sed '/myregex/ s/from/to/ p' and sed '/myregex/ s/from/to/ ; p', but while testing to explain what i meant I answered myself, and in the process I also understood what addresses are ehe

Right, awk is a proper programming language, right? that’ll be for another day…

!/dev/dm-2!!p

This weired me out until I read the explanation. I’m so used to the slashes lol

In the end I’ve used the first command you wrote, because KISS, but I appreciate your explanation

Check the sed man page for more details

Yes that’s been my only source so far, but to be honest it’s really cryptic. it might just be that I’m used to syscalls man pages (also sed is kinda complex it can’t be easy to write a single man page for it)

The -n suppresses auto-printing

That’s something I was missing! It makes the command look definitely less complicated.

Also, what is the difference between separating expressions with a space vs with a semicolon?

Easier IMHO is awk

Eh, that’s another beast. For some reason tho I find sed more appealing.