ShellCheck VS proot

not sure about unit/functional testing, but https://www.shellcheck.net/ is handy for linting and finding bad practice.

First, how did ShellSheck didn't give you warnings, if you checked it?

BTW, check out https://www.shellcheck.net/. You can install it to your computer and it'll warn you about this and many other ways you can accidentally shoot at your own foot with Bash.

This is super easy but, may not always be enough.. Luckily, the fine people at ShellCheck gave this some thought and created a nifty tool. It’s got a nice README, is available via most decent package managers and, even has a web interface where you can test snippets (in case you’re bored and on the tube, I guess). The README also includes a Gallery of bad code to showcase some of the stuff shellcheck can pick up on.

Bash because it's everywhere and I've put effort into learning it properly. My scripts almost always pass shellcheck first try, and I know the syntax of bash-specific features reasonably well. I don't see any advantage to learning another shell which I need to explicitly install and relearn all over again.

The Prompt logic could include some nuance to flag potentially harmful commands, but it would still be potentially fallible. However, you raise an excellent point, and value can be added by altering the workflow to run the results through a tool like shellcheck, where you can customize acceptable BASH commands.

Idea: Incorporate shellcheck that repeats the code back to the bot until it passes shellcheck at least.

A good way to learn the finicky bits is to run all your scripts through shellcheck. (Better yet, find a plugin for your editor/IDE.) If it flags an issue, read the corresponding wiki page and see if you understand it.

Have you run them through shellcheck? https://www.shellcheck.net/

Nice work! I recommend using https://www.shellcheck.net/ to make sure your bash script is in a good modern shape

I understand the sentiment, but I disagree. From the last time I checked, the big compromise with GNU/Linux phones is still the lack of social media and messaging apps and appstore ecosystem. Android, with root, is every bit as much a computer as a Pinephone and Librem 5, but the opposite isn't true. Termux has PRoot, a user-space implementation of chroot allowing a full distro install. I personally don't have any problem depending on Google, I have a problem with things being locked away with no alternative. Given the option, I will happily accept the risks and void my warray to root.

https://wiki.termux.com/wiki/PRoot

There is a command-line variant, proot-distro. Usage examples are given at https://wiki.termux.com/wiki/PRoot.

It's called PRoot, you can install other Linux distributions (e.g. Arch, Debian, etc.) within the virtual root environment.

https://wiki.termux.com/wiki/PRoot

The video editors are running in Termux proot.

Well, it says to use proot, which is described here. It seems you use it to install Linux distros inside Termux without root, and then if you install ledger inside such a distro, you won't run into system call issues.

XDG_RUNTIME_DIR is normally set by pam_systemd(8) on systemd-based systems (or pam_elogind(8) on non-systemd-based systems that nevertheless use elogind). Checking the Termux installation on my own phone, there are no man pages for either pam_systemd nor pam_elogind, so i assume neither is available by default. But OP talks of Ubuntu, so i assume they're running Ubuntu in a PRoot - OP, is that the case? If so, you might need to ask Termux-knowledgable people what the best thing to do is in this case. (When i was running Void Linux i just set XDG_RUNTIME_DIR via shell script on console login.)

Have you tried downloading a fresh disk image to test since you know the password now? Also, since you're trying to run aarch64 opensuse on termux, it may be a better idea performance-wise to use Proot and/or proot-distro. PRoot doesn't have the overhead that qemu does, so if you don't need any special hardware features then it may work better for you.