Eric Renfro

Using the `"${AWK_PROGRAM[0]}" '{print tolower($0)}' "${distro}"` caused a surge of new issues with it trying to open files named various "fedora", "arch", "linuxmint", "opensuse", "pop" in my case, with "No...

Done, tested, and verified. Thankfully I have a MacBook Pro with bash 3 handy to test with. :)

Yep I could agree with that, arch, user, and class. I'll look into that today and see about updating the PR if you'd like. And also, do you want me...

> @erenfro I don't know why, but neither `tr '[:upper:]' '[:lower:]'` or `tr '[[:upper:]]' '[[:lower:]]'` work on OpenWRT's BusyBox v1.33.2 (2023-04-14 11:34:26 UTC) multi-call binary. Fortunately, awk's `tolower()` does work....

I would think so, yes. I'd have likely detected the message, and allowed user input to respond about it to proceed, right now, it's just doing nothing, and stalling on...

I think that would be ultimately the best option. Let the user confirm, interactively.

I looked at them, but I'm not thinking this is the same. This has been going on a while, but literally only ever does it on the e character, and...

A big one as well. ext4 filesystems always make lost+found. This is owned by the user root, and the group root, and is intended to always be present. However, this...

> @erenfro Could you create a separate issue (bug) for this? Please provide details of the mover you are using. I mean, I'm using restic, it's finding lost+found owned as...

That, per the documentation, makes it like it requires a string value and if it's the same value as before, then it will not continue to do so. This seems...