free software, repost to public 

we have a fortunes-off file so you can print offensive quotes at login time. No distro I know of comes with a fortunes-supportive file that lists encouraging, calming quotes.

You can make sudo(8) insult users when they type their passwords wrong ("Defaults insults" in sudoers). There's no option to make sudo be gentle and understanding when you mistype.

I grew up in free software circles and only really learned any emotional skills after growing out of them.

free software, repost to public 

When my lil dictionary is updating the db, it shows a minimal ascii animation of a steaming coffee mug, and goes like ‘X, done… Y, done… All done! $0 is ready to use, enjoy!’ In modern computers this doesn’t even take time anymore, but this little detail is by far what I got most praise on it (2nd most praised is the fact that it’s ‘pretty’, that I took care with colours and Unicode etc. in a cmdline app).

more cuteness and gentleness in sofware pls

free software, repost to public 

@elilla I want to make Rocket cute. The localised program name is the only cute thing about it so far (I just wanted Eldflaug but added all translations I know)

free software, repost to public 

@elilla very relatable, i use the fish shell mostly because the default login message says it's friendly (“Welcome to fish, the friendly interactive shell”), i don't use any of its features 😅

makes me thing of this website:

tech, fish shell good 

@flop yass fish good!! the featureset is actually elegant and powerful, it’s refreshing coming from bash/zsh, but the way it makes a deliberate effort to be friendly and welcoming is what sets it apart for me. (also pretty!) things like all features ready out-of-the-box, or readable consistent syntax, seem like obvious nowadays, but cp. to bash; they make a lot of difference to new users, & if nobody new is learning to use shells where will the command-line be?

tech, command-lines 

It’s a shame that the only decent command-line we have is the Linux/Unix ecosystem. There are reasons it is the way it is, esp. the fact that most hobbyist devs are programmers/engineers (way too few designers, writers, sensibility readers etc., & the precious ones we have get little respect).

But a cmdline could be all of:

- fully decolonised
- discoverable
- consistent
- documented
- cute

& the fact that ours isn’t is taken to be an essential limitation of cmdlines…

tech, command-lines 

Have you tried being polite to your terminal?
alias please='sudo $(history -p !!)'

$ touch /etc/newfile
Operation not permitted
$ please

tech, command-lines 

@polyphonic I'm already thinking of sudo as saying please and following a command with sudo !! is a passive aggressive way of saying please if the computer says no the first time

tech, command-lines 

@elilla the fact that we only have a handful of human-usable (i.e. not primarily for scripting) shells is criminal. the entire modern shell ecosystem that I've heard of can be listed on one hand:

* Bash
* Fish
* Zsh
* Xonsh
* Elvish

of these, xonsh and elvish have serious problems which practically disqualify them

free software culture, command-lines 

I think what hurts the most is the general problem with Linux: The people who code the tools – all the programs the shells will call – by and large aren’t interested in making them easily learnable, discoverable, documented, or kind. So there’s no consistency. There are efforts to consistency in APIs etc., but heck not even all GNU software uses GNU-standard cmdline options.

isn’t it weird that we have to hack together completion from duplicated info?

free software culture, command-lines 

@ink somebody already told the computer "this software has an option -l which does blah". but then each shell has to tell it again.

I see lots of incomplete manpages these days, lots of software distributed without manpages. why is that? what is it about manpages that make them suck so much, why ppl are resorting to webpages, github's instead? what would a good, consistent, throughout, discoverable, zero duplication, console help system look like?

free software culture, command-lines 

@ink getting to that point would take a lot of design, a lot of writing, and the hardest part – interest and participation from the programmers of the tools.

this is why I’m such a fangirl of fish. it’s not just the cleanest, most elegant of modern shells; but maybe its greatest contribution is how ridiculousfish has fostered a culture of thinking about the users not as ‘users’ but as people, as, well, friends, from the very beginning 😌

tech, fish shell, question about learning 

@elilla @flop do you think it would be better to introduce people starting to learn linux-stuff to fish instead of bash?

I haven't used fish yet, but after reading these toots I watched some videos and it looks like it takes down a lot of the barriers to learn the command line, especially the autocomplete stuff with the flags or the syntax check while typing.

My hestitation would be "But bash is everywhere, it's much more universal!", but reading your toots, this more and more seems like a bad thing anyways...

tech, fish shell, question about learning 

@tobbsn @flop :lazer_Y: :lazer_E: :lazer_S: :blobrainbow:

we unfortunately live in a world where bash is the standard (for now :owobread: ) , so there's no way around that. but if I was going to teach beginners the command-line, I'd start on fish, get them a firm footing, then at some point have a discussion about other shells (good point to talk about diversity in linux, pros & cons) and show how to install fish when u get a system with bash.

tech, fish shell, question about learning 

@tobbsn @elilla @flop I too am intrigued about fish after hearing a lot of people talk about it recently. I only switched to zsh from bash recently and have found that a huge improvement, so I'm curious to see how much better things could be! Bash may be the norm now but it doesn't have to be that way forever

re: tech, fish shell, question about learning 

@hyperlinkyourheart @tobbsn @elilla @flop Fish shell is awesome. I've been using it since ~2013, back when it would crash a lot. The history, type-ahead highlighting, dir stacking (hit alt->left/right to go to previous directories) .. it's all really good.

It might not be a good starter shell as most tutorials are in Bash and things like $(echo foo) in fish are (echo foo), but it does provide you useful error messages when you try to use bash syntax.

tech, fish shell good 

@elilla I've been using fish for a few months now, and I enjoy it a lot. it has the features I want, and I don't have to work so hard to install plugins a la zsh. the nice syntax is also a plus. this is to the point where regular bash feels gross whenever I'm forced to use it

free software, repost to public 

@elilla I don't know how to do that kind of feedback on the command-line, but I must learn because I always love it when I see it

free software, repost to public 


I think the most important things take just effort, not coding skill. I'd rank in order:

- Actually having plenty of informative documentation error/diagnostic/etc. text.

- The wording and language of these messages.

- Colour, always with additional symbols (some ppl are colour-blind) but liberally – almost everything on terminal can benefit from colour. Don't do red/green for status, it's a v common blind spot, use red/blue instead.

free software, repost to public 

As for the ascii it was really trivial 🙈 didn't bother learning animation libraries or anything, just rewrote 2 images over one another periodically with SIGALARM

such a simple little drawing, took me like an hour to figure out the code maybe, but ppl loved it anyway 😌

(at some point I tried a tea mug like


but misalignment due to full-width chars was really common in terminals back then.)

Sign in to participate in the conversation
Queer Party!

A silly instance of Mastodon for queer folk and non-queer folk alike. Let's be friends!