That’s the real linux user story.

We come for the speed, flexibility, FOSS values … but we STAY for the middle mouse paste.

What’s Germany? You mean Německo?

Don’t fold them diagonally before wringing them out.

Who does that?

Ah that’s why he’s small and bald: he cleans so hard he scrapes a layer of himself off every time.

r?

Teach him kindly and lead him to be a better man. Only if he will not be led, cut him down with a regretful stroke and send him to Buddha.

…

Forgive my unsolicited advice. Perhaps you know this already but if you want the blockquote…

Just for entertainment, I’m going to assume your post was a Markdown equivalent of “teaching kindly”

Fun on paper, but… then imagine people generating their theories to justify why, eg. RFK Jr lost to Musk or vice versa.

We should not be talking about why “shithead x is actually not so bad as shithead y”, we should be isolating before NASA can actually send BOTH of them to Mars where they belong.

Well it seems like this “Aaron Day”, for one, does.

(I hope he’s not the only one :D)

And you stare at it forever and wonder what you could have done better.

Or move on after realizing that there’s no way you’re going to learn stuff without doing a LOT of stuff, most of which won’t work out or even go anywhere, and it’s perfectly normal and fine to have lots of unfinished/dead/dormant/abandoned/(call-them-whatever-helps-you-move-on) projects.

I think vipe is underrated; it takes whatever is on its stdin, shoves it in a temp file, opens your favorite text editor (EDITOR environment variable) and waits in the background until you finish editing the file and close it. Then it outputs the edited text to its stdout.

It’s useful in all kinds of pipes, but personally I use it tons of times a day in combination with xclip, in something like this:

xclip -o -selection primary | vipe | xclip -i -selection clipboard

(I actually have a bit fancier version of this pipe wrapped in a Bash function named xvxx.)

On my setup, this takes my current text selection, opens it in vim, and lets me edit it before it sends it to the “traditional” Ctrl+C clipboard. It’s super handy for editing comments like this one.

If you often find yourself writing complex Bash pipelines involving generating some output and then running set of commands per line (perhaps in a while loop), sometimes replacing the “selection part” with vipe can be easier than coming up with right filter.

find_or_ls_or_grep_something | vipe | for while read -r foo; do some_action "$foo"; done

And if you are really confident with Bash, you can go even a step further and do:

you might find something like this useful sometimes:

find_or_ls_or_grep_something | vipe | bash

and just create a large dumb one-off script, manually curating what’s exactly done. Remember that editing large lists in vim can be made much easier by utilizing vim’s ability to invoke unix filter commands (those greps and uniqs and seds et al.) on the buffer, and /or block editing mode using Ctrl+V (that last one method goes really well with column -t).

alias lr='ls -lhrt'

FTR, <<< is a bashism. it’s a nice one, though.

it’s real, it’s when you gather with friends to wyom.

Call me a grumpy stubborn old hacker if you want, but no thanks I prefer printf shower.

I wonder if anything exists beyond the context of me writing this comment on Lemmy right now.

FAR manager (clone of Norton Commander) might be worth giving a look. Not a GUI, though, it’s TUI but responds to mouse.

On Debian, sudo apt install far2l and then run far2l.

BTW, to add ssh-agent authenticated scp connection, press F11, go to NetRocks and create connection. in the dialog you’ll need to select the protocol to scp and then auth method in “protocol options”. you can edit an existing connection by going back to the connection “directory” and using F4 on the connection. Once you connect you can copy/move files back and forth.

Along with scp it supports eg. smb, nfs and davs.

Your question, “What features does the Windows version of Calibre have that the Linux version not have?” cannot be answered without accepting an unargued premise: that the windows version has more features than the Linux version.

Nope, it simply asks (or even expresses genuine curiosity) about a subset of features on windows which might be missing in Linux version. That’s if you want to be super logical and fussy about things. If not, you could have just answered or moved the discussion in any relevant direction you would like. That was always allowed.

Ironically, you kinda did answer it, at least in part, by mentioning the AI slop bloat. Why hide your answer behind a wall of being a jerk, though? I can only speculate. Too little sleep, too many old Rationality Rules videos? :-) Thatt’s none of my business; I just hope you feel better now.

point taken. I see how it can be a good balance of pros/cons.

re: debianland, i’m not sure i understand the question so…

Certain major version of a “traditional distro”, say debian 13 provides fixed list of libraries and apps (which get updated during the lifetime but only to necessary extent). each of those can only depend on a particular version selected by debian. eg. if for libfoo, the provided version is libfoo-1.2, then anyone who depends on libfoo must depend on libfoo-1.2. (if that can’t be achieved before release then that package is simply removed.)

note that two versions of the same package can’t co-exist on the same system. (this is basically true for debianland and fedoraland; because packages share the same filesystem it would be not feasible to make it work without huge amount of added complexity and bug surface. definitely not on a distro-wide level).

honestly i’ve never used backports; I don’t know what process they use to select versions; i would assume that it’s basically on a best effort basis.

personally if i don’t find the stable version new enough, I look for vendor repo, appimage or flatpak (roughly in that order)

I’ve found it helpful to install as much as possible as flatpak, since that decouples app updates from system updates

But doesn’t it eat all disk space? And don’t flatpak apps tend to proliferate dependencies on outdated stuff? From my experience (and that’s just maybe dozen of apps that simply don’t exist in the distro) when running flatpak update i always get deprecation warnings about some platform flatpaks that some of the apps depend on. And given that everything is few hundreds of megs, sigh…

That’s why I like distros like Debian: there’s always strong pressure for apps to converge towards newer versions of libs/frameworks. Sure, it takes work to maintain but IMHO it’s worth it: once the app is in, you know it’s playing nice at least to that extent. AFAIK one of Flatpak’s core features is to lower the barrier by allowing multiple dependencies co-existing and thus removing that pressure, but that’s when the mess is inevitable.

Sorry for the rant.