roflo1

joined 2 months ago
[–] roflo1@piefed.social 2 points 6 hours ago* (last edited 6 hours ago)

I’d guess more like gopher

[–] roflo1@piefed.social 4 points 4 days ago

What options have you tried that you find half-baked?

When I’m not in the mood for gdb’s CLI/TUI, I often use KDbg, Nemiver, or just good old CodeBlocks.

[–] roflo1@piefed.social 9 points 3 weeks ago* (last edited 3 weeks ago)

I do that very often. I’ve found that people’s expressions are a lot less “stiff” that way.

Edit: it’s entirely possible I started doing it after I read this comic for the first time.

[–] roflo1@piefed.social 3 points 3 weeks ago

Funny. I actually prefer the plastic reels. I feel like the metal ball bearings (not present in the only metallic reel I ever owned) do all of the hard work for me.

Maybe it’s just what I got used to?

[–] roflo1@piefed.social 3 points 3 weeks ago

I’m intrigued.

Do you recall something in particular?

FWIW, I usually just connect to a ssh location from within Nautilus.

[–] roflo1@piefed.social 22 points 1 month ago

I’ll try to explain it in another way. First, let’s talk about “semantics”:

Usually we assume that a tarball contains multiple files, and a gz is a single file compressed.

So a .tar.gz file is a single tarball that has been compressed.

A .gz.tar is understood to be a tarball containing a single gzipped file. But if that’s indeed what the file is, it doesn’t make much sense to tar it in the first place.

Moving on to what you really want to accomplish: you can certainly create many gz files and tar them, but we wouldn’t call it a .gz.tar file since tar doesn’t care about the format of the included files. Much like a bunch of compressed PDFs aren’t named .pdf.tar

Also, I’d like to point out that neither tarballs nor gzipped files are optimized for modifying.