• 10 Posts
  • 518 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle





  • Exactly. That’s Windows’ secret. Give us a control center where it’s easy to control NetworkManager, Pipewire, systemd, and other parts of the OS, and give them not-so-technical names. That’s one of the keys to Windows’ success. Others involve EEE and anticompetitive practices but we don’t want Linux going that way now, do we?

    It’s not that Windows isn’t complicated, it’s just that there’s a GUI for everything.



  • Never heard of Spiral, and I’ve heard of a lot of distros, so I’d steer clear of projects like it, that are new and/or niche, as there will be lower reliability and support available. Aurora is also pretty new, but it (and Fedora Atomic, and uBlue in general) has a strong community, so I’m more likely to trust them.

    PopOS and Linux Mint get a thumbs up from me.




  • Fair enough. I basically gave you a large chunk of vim so it will feel super overwhelming. The trick is to do one command or combo at a time. For example, I started with dd. Then I added yanking. Then I added visual mode. Then I added “o” (which I think I forgot to mention: o creates a newline under the current one and puts you in insert mode. Capital O does the same but above the current line). The real trick is going little by little. And to be honest, there are some commands I still rarely use or forget to mention. I’ve never used f instead of t. And in terms of forgetting to mention, there’s the x command which deletes the single character under the cursor rn.

    Also, I’m sure someone will find this list helpful, so on top of this, I’ll also add this video (and hope that Piped bot will appear): https://www.youtube.com/watch?v=RSlrxE21l_k

    It contains some things I haven’t mentioned.

    As for learning all this, I’m repeating myself for the third time. Do it little by little. And when a command is already a thing you do almost without thinking about it, you’re ready to add more.

    I’m mentally checking out

    Why? dw is delete word, c5b change 5 words backwards, and those are the most complicated commands you’ll ever get to use, unless you start adding cuatom keybinds.

    But I digress. If you don’t want to learn it, it’s fine.


  • Not even Basic Command-Count-motion like c3w aka change 3 words after cursor, or d3b delete 3 words before the cursor?

    To that, you add the D aka delete command C for change Y for yank (copy)

    So yy to yank line, or dd to delete line.

    Also p for paste

    Also, i sends you before the cursor, a sends you after. Capital I is insert at beginning of line, Capital A is insert at end of line (append).

    I terms of motions and moving around, you need: hjkl, C-d and C-u (half page jumps down and up), and within the line: 0 or ^ for beginning of line, $ for end (taken from regex), w for moving by word forwards, b for moving by word backwards. That’s pretty much all you need imo. There is also t and f. Where t goes forwards (think 'till aka until). Like dtc delete until the c character. F is the same but goes backwards in the line rather than forwards. Remember you can use these with xommands, so d$ deletes until the end of the line. Or “dt.” deletes till the “.” so… yeahI know there’s more, but that’s all you need for Normal and Insert mode imo.

    For Visual mode, you only need to know how the Visual modes work. Visual (v), Visual Line (Shift-v) and Visual Block (Ctrl-V).

    Also, for visual mode, it might be helpful to learn how to use V-Block to comment out multiple lines at once. Can’t be bothered to go into it.

    But I’d argue that’s all there is to learn about vim keys in terms of getting work done.



  • I know 2 people have already said it, but NixOS is in very desparate need of documentation. It’s so immensely difficult and at a certain point the learning curve feels more like a vertical line than a curve, so that’s my top pick.

    Other than that, I recently tried a project called Bluebuild and its docs are very incomplete (also the project doesn’t work for me but that’s another topic).

    In fact, the topics of packaging software and creating (custom) live isos are both very underdocumented in general.

    So packaging for deb and rpm is also quite difficult to find good and easy to follow docs and guides for.


  • uBlue is good, but only if you follow the official templates. I was following some other thing which did things very differently and my custom iso ended up broken i.e Anaconda was crashing and installation was impossible.

    Edit: the thing is called Bluebuild. I’d recommend to steer clear of Bluebuild and just using the official template on Github. I’m still yet to do that myself but it seems like it might actually work, unlike Bluebuild.



  • Same. Except that one time I forgot to charge my laptop and my battery decided it will go to 0% during a kernel update. Charge, Reboot into live iso, arch-chroot, do update. Reboot into normal system, all good. A 5 minute job, but it’s the most serious issue I’ve had to deal with, alongside the keyring issues once which were solved by an Erik Dubois video, a 15-minute fix incuding the video runtime.