I had broken bash in my arch installation and managed to make it dump core like Chernobyl (baby leet’s first segfault!) so one quick reinstall later I’m exploring the joys of alternate shells, my feelings sufficiently summed up by this image:
I would be unimaginably glad if someone knew a CLI editor that was the same thing to nano as fish is to out-of-the-box bash. This is such good, perfection, sense-makingness, convenience and most importantly teh pretty.
How…
How did you manage to break bash?.
Isn’t that thing older than and more widely used than Linux? Like, the last significant bug it had was counter-intuitive handling of environment variables, no? How do you manage to break it?
For CLI editors – absolutely no idea, I’ll be honest (I just use emacs), but I’ve heard `jed`… mentioned once or twice? And not in a way that is “it has many good extensions” I don’t think? So it might be worth a look?
I think sourcing .bash_profile in .bashrc according to some customization instructions for OSX bash was the cause, because on my second try undoing that part unbroke it. First time I broke my account promethea with it, just got locked out and had no clue why (because it happened substantially after editing the files) and mucked around on root trying to make i3 and sddm work and managed to lock myself out of root as well. So I got back to ChromeOS (doing this on a c100pa chromebook because baby leet’s first arch must be as non-standard as possible because I always play life on hard mode), reinstalled (it was easy this time because I knew what I was doing) and broke bash again, but this time I was su’d to promethea from root, so it dumped me back to root instead of login, showed an error message and made debugging easy.
So why the fuck was I using OSX instructions for Arch? The bootcamp preparation didn’t include linux instructions, presumably assuming that anyone using linux either doesn’t need handholding (because they know how to do stuff) or doesn’t deserve it (because they’re running linux without knowing how to do stuff or bothering to figure it out themselves), which is IMO perfectly justified. I assumed they’d be similar enough because bash is bash, it wasn’t, and I learned. Fucking up and unfucking it taught me a lot more about bash than just following instructions successfully.
conductivemithril liked this
neurocybernetics liked this
raginrayguns liked this
thetransintransgenic reblogged this from socialjusticemunchkin and added:
socialjusticemunchkin reblogged this from thetransintransgenic and added:
eliza-was-here liked this
arbitrarilychosen liked this