Best I can do is

"\ude41🙂".split("").reverse().join("")

returns "\ude42🙁"

Oof yeah, some programs really love to touch a lot of stuff making strace kind of annoying to use. I usually end up chaining more grep -v pipes on the end as I find files I’m not interested in seeing e.g.

strace okular | grep openat | grep -v breeze-dark | grep -v icon

Might help to first save it to a file so you don’t have to keep relaunching okular as you add more inverse greps

strace okular | tee some-file
^C
cat some-file | grep -v ...

I would probably try running

strace okular | grep openat

to see all the files it’s trying to read and see if any aren’t managed by your package manager and move those.

But the latest reply by felixernst in the kde discuss also looks helpful.

Who controls the British pound? Who keeps the metric system down? We do! We do!

Yeah good point. I suppose the problem is this function that operates on numbers allows numeric strings to be passed in in the first place. The only place where I would really expect numeric strings to exist is captured directly from user input which is where the parsing into a numeric data type should happen, not randomly in a library function.

On my machine at least man openssl shows that -k is for specifying the password you want to derive the key from, so in that case I think you are literally using the string /etc/ssl/private/etcBackup.key as the password. I think the flag you want is -kfile.

You can verify this by running the command in strace and seeing that there is no openat call for the file passed to -k.

Edit: metiulekm@sh.itjust.works beat me to it while I was writing out my answer :)

It’s kind of insane how bad this whole is-number thing is. It’s designed to tell you if a string is numeric, but I would argue if you’re ever using that you have a fundamental design problem. I hate dynamic typing as much as anyone else, but if forced to use it I would at least try to have some resemblance of sanity by just normalizing it to an actual number first.

Just fucking do this…

const toRegexRange = (minStr, maxStr, options) => {
  const min = parseInt(minStr, 10);
  const max = parseInt(maxStr, 10);
  if (isNaN(min) || isNaN(max)) throw Error("bad input or whatever");
  // ...

Because of the insanity of keeping them strings and only attempting to validate them (poorly) up front you open yourself up to a suite of bugs. For example, it took me all of 5 minutes to find this bug:

toRegexRange('+1', '+2')
// returns "(?:+1|+2)" which is not valid regexp

I can’t find a keyboard with them, or a copy/pastable line where they’ve been typed

Maybe use combining diacritical marks?

I’m using 0x326 (Combining Comma Below), but you may need the CGJ in there to render correctly in all contexts

e.g.

Foo!̦ Bar?̦

Edit: Combining grapheme joiner, not zero width joiner