Bad usability, binary logs, crummy architecture.
Bad usability, binary logs, crummy architecture.
It sort of is, the whole elogind thing.
Even better, ~/.local/share/
It’s a poor architectural choice, but making cross-platform apps is even more problematic with the current UI tooling out there. Too much fragmentation in the base OS’s. If Mac moved to support Wayland or something like that, maybe we’d start getting somewhere.
I don’t really use it that much honestly. Let me see…Ctrl-R is rename for a single file. Copy/move I think are selection operations, one way is to press space next to file names, navigate where you want and do Ctrl-P to copy or Ctrl-V to move (cut). Symlink, uh, just put the cursor on the file, “n”, “s”, type the name out and press enter.
You can also use the batch rename editor to move files it looks like. I hadn’t tried that before, but it does let you put in an arbitrary path.
sudo su - $(whoami) -c $(which $SHELL)
Seems like a lot of Linux/programming memes basically just stem from a place of real noob insecurity. “I can’t figure out how to quit vim!” “CLI is scary!” “Arch users say ‘I use arch BTW’!” No offense to the noobs, it’s just that, you know, people use this stuff for an actual reason. Yeah, vim requires you to be in normal mode and hit :q or even (gasp) :q! to quit sometimes, it’s also a hyperflexible editor that lets you program super powerful functions, macros, do dirt-easy regex replacements, etc. Including binding Ctrl-Q to quit if you really struggle with that.
Gparted is nicer for some stuff (have fun resizing a partition without it, for example), but for basics it’s hard to go wrong with cfdisk IMO. Or even plain fdisk. Very useful to actually know how to use that if you don’t have access to gparted, e.g., system recovery or install, and cfdisk is super easy to use too.
My absolute favorite is nnn (mine’s aliased from “n3”, is that insane) -> “r” which gives you a vim console for renaming all the contents of a directory. Beats perl-rename and everything else cause it’s actually interactive. Although it is possible to write files over each other with it, so gotta be careful.
In the default view you literally just use the arrow keys to navigate, basically the same as the old Windows tree explorer or whatever else like that. 1/2/3/4 flip between tabs. If you hit “right” on a file I think it hits xdg-open or something to open it in the default program. “e” opens text in your … default EDITOR
? Guessing. “?” for help and a lot of other commands.
Their stance is that you personally are banned for life from subs regardless of which account. Would be a real shame if your IP got changed between accounts, your cookies and local storage got cleared, and you never mentioned the old account again. You could accidentally post in a sub you got banned from, and they wouldn’t be able to helpfully re-ban you from the sub!
If you were still trying to spend time on reddit in the first place at least.
I’ve done it a fair bit and it’s actually pretty painless. If you know how to use vim you save a ton of keystrokes, which makes a big difference on mobile.
…ssh and vim?
They’re both very complex so it’s understandable people would have different experiences. In general I’ve found GCP fairly straightforward, with shitty documentation, generally good support of fundamentals, great k8s support, good prices, fairly modern APIs, and relatively low feature coverage. AWS more built out, awful & totally inconsistent UI, better feature coverage, higher prices, and some pretty janky XML APIs if memory serves.
Honestly, it’s not as bad as AWS or Azure. Plus if you use k8s it’s first-in-class support, since Google came up with k8s. There is a fairly steep learning curve though.
If you’re deploying anything in cloud infra you need to make sure it’s portable between providers. Vendor lock-in is a big avoidable no-no.
I mean, it’s basically a classic Jeep or maybe Japanese make car. Everything built to take apart and put back together.
I’ve got “syu” aliased to the above on Debian etc. boxes. Save me some typing.
I was about to say, half the things people write complex shell scripts for, I’ll just do in something like Perl, Ruby, Python, even node/TS, because they have actual type systems and readability. And library support. Always situation-dependent though.