I think for terminal users, and I definitely use it enough, fish shell makes even more sense as not only is it simpler, its also faster. It isn’t some dumbed down version,
For my ebooks I was using Calibre, but managing an ebook collection can be tedious, so I switched to Lector, which became unstable cause unmaintained and then I used Bookworm.
I just discovered an ebook reader for the terminal and it works great, even in a TTY, it’s called baca :
I created a function with fd/fzf to search ebooks and open them with baca, I think it will be my default reader .
NovelWriter would be close to perfection if it had collaborative features
I have been looking at that for a couple of years now. I’m waiting for it to have more features before I test it. Always looks really interesting to me!
The classic DOOM game over htop, the text-based process viewer
@UncleSpellbinder Why should we avoid to use Flatkpaks? by the way, in Discover used to see the AUR software and flatpaks, but now it only shows flatpaks…i mean, i do everything with yay…but does anyone knows why did that happen?
Same vibe:
You probably don’t have packagekit-qt6 installed but its strongly discouraged to using it:
Warning: As explained in a GitHub comment by a Package Maintainer, “Handling system packages via packagekit is just fundamentally incompatible with our high-maintenance rolling release distro, where any update might leave the system in an unbootable or otherwise unusable state if the user does not take care reading pacman’s logs or merging pacnew files before rebooting.”
I never said we should avoid using Flatpaks. What I said was…
Meaning I prefer Arch repo or AUR over Flatpak. I only use a Flatpak app as a last resort. For example… OnlyOffice via AUR doesn’t work well for me. I tried the Flatpak and it work perfectly. As of now, the only app I have installed via Flatpak is OnlyOffice
AppImageLauncher. I didn’t know this existed. Looks intriguing.
“AppImageLauncher can control how the system treats AppImages. It integrates them into the system, provides helpers for updating or removing AppImages, and a lot more. On their first execution (i.e., if they have not been integrated yet), it displays a dialog prompting the user whether to run the AppImage once, or move it to a predefined location and adding it to the application menus, launchers, etc.”
ncspot
“spotify on terminal”, marvelous on low-end machines
For whatever reason, I thought this was a requirement to launch Appimages.
I wonder how many people think Appimages are bad simply because they don’t have this installed.
For me, I put all my Appimages, .sh files, and other portable executables in a folder in my Home directory. For the ones I use all the time, I launch them with a shortcut. And I set that same directory as the “app directory” (or whatever the actual term is) for Appimage Launcher.
Only time I ever used appimmages was the one-time use scenario, like balena etcher. I’d just download the appimage, click properties, and mark “executable.” Now, with AppimageLauncher, it treated as close to a system app as possible. In the menu, ready to be pinned to taskbar or in favorites.
As a side note, quick question… Would an official appimmage be safer than Flatpak or even AUR?
Safer in terms of coming directly from the source? → Yes.
Safer in terms of being up-to-date? → Possibly no.
However, if the developer only provides an Appimage for Linux, then it’s as safe as you can get if there are no alternatives. That is, without cloning the repo and forcing it to use more up-to-date libraries — something most people do not know how to do.
$ pwgen -Cny 11 25
ju9Ax.ai3ai igei9Ne"u7O ro9Ohgaich; ef=o8koC_ah guKeiv5xae? tooxoC2Ni+m
sai8Ti4di}e uchee4YueX+ Eu4Air/ohse phei9yaFu!n poeph5Oow:e Ekaib$ae5in
aoP8Ahvoh<S oot)uY#u*j0 ees8aiGhil( eng9Ielu&vi pumeQue@s5k seib9voo]Zi
Poh2eig$ahd phoo~zoe0Ie oW)ai5Aim6j moh0aijoo>V shu*umeer1F ohXu0chohv+
heT{eesohd3
~ $ pwgen -Cny 25 25
iequaeQu6ie[w5ainaem4eng1 ieb{ieraicoot(iR8Aeshei4o uxu5ieGhu;v8pohVoobahPil[
eu6Me5ooqu^ae5Oxae2maiGh| ea|n/ah2zav$eeh3Ii}z=ed1i fe1imeothee[Jo:bieN2Ochoo
oF7loh=qu4ke(alae1IXith9g eir2Vad4uNg<eJai7iegu5bie oi1yazaeh3Eetaenai#tailae
ogh8aiseesh3Die[sh1heek3E Aebeshoonae5dae8tee4eus$a uu&pohnga6phaetae;n`aiLoo
ooZ6yooh0thaib0hoth'o=gh0 ooghooTh9pu0dei9bie/ji[ze sieb2Ahchah7ooc2aiPe(a2ei
aitohCee,h8hej8meax4ood0J Wei2anah7gee{m4phei:X7foh phu1chi{s%e1che0efuil9Xah
iG&ah7xie[Pah1eiTie`ch)of Ahloo4Lie1queeb0iez|as2Ce UeCair}ei0boo:p1or8quievi
Ear9Jaena^r6eu\fa!pho9Hei ahThoosh+uGh1uti5jiyeev5a aoyieFei4ohk_ueb9ieh9Vies
Aifue0aik2gu#x8vaenooghai
edit for the question mark: a CLI password generator, with arguments.
No terminal application can use the Spotify free account, right? Needs premium?
Haven’t tried with the free version, sorry.
This app is rather handy.
@anon26269396 Especially handy after the last Arch update!
just installed this. It was in the Endeavour extras repo. thanks.