I can't speak for anyone else, but for me, it's just one file to backup to keep all your custom commands (.bashrc) while it would be many files if you have a script for each.
I can't see the benefit of having a script for just one command (with arguments) unless those arguments contain variables.
I use bash and I usually put /bin/bash in my scrtipts, because that's where I know it works. /bin/sh is only if it works on many/all shells.
I don't have many such scripts, so I just have one. I don't really share them, as they are made for my usecase. If I do create something that I think will help others, then yes, I share them in git somewhere.
I do have a scripts folder in my Nextcloud that I sync around with useful scripts.
Some of your examples can probably just be made into aliases with alias alias_name="command_to_run".
I assume you have added the repo because it fixed some issues at some point. Is the repo still needed to fix those or could you remove the repo and just update using normal distro packages?
DISCLAIMER: I don't use OpenSUSE or any of the variants. I assume that the obs stuff is kind of like how the AUR is for Arch, or PPA's are for Ubuntu. If it's something difference, please disregard my comment.
Silverbullet looks pretty easy to set up. Can you change the font and such it uses?
Okay. I can already do that in the normal client app. But this client looks really nice and I'm glad it's a thing. :)
I currently DM a game (going on a couple of years now) where most of the story is developed through encounters and travel time. It's just the kind of game my players like at this point as it's a much needed break from everyday life. The characters do get to explore their backstories through stuff that happens and people they meet though.
In addition to the previous comments, the official telegram-desktop app is also Qt based and open source. So maybe the dev thought it to be a lot of duplicate efforts.
As far as I know, SP is an electron application and if you run Plasma in a wayland session, global keyboard shortcuts won't work, unless you enable it in the Plasma settings.
Just updated my Arch laptop to Beta 2 this morning. Can't wait to use it much more later. :)
If you have "keep above other windows" enabled, then it seems to wok as it should.
The context menu is (if I understand it correctly) a window in it self, so it would be behind a window that is kept on top.