• 0 Posts
  • 197 Comments
Joined 9 months ago
cake
Cake day: January 3rd, 2024

help-circle
  • what’s good about neovim?

    • NeoVim supports plugins written in modern languages without a Vim script shim. Vim script is utterly awful, and the sooner we can all pretend it never happened, the better the world will be.
    • NeoVim can be confirmed and extended with lua a language that many people actually like to use.
    • NeoVim is built client/server style, like VSCodium, so it can do the same remote/local mix and match tricks. Notably, VSCodium works nicely as a front end for editing files with NeoVim.
    • NeoVim is somehow actually faster. vim was no slouch, but a full rewrite seems to have added some…ahem…vim.





  • I think I get what you are intending to imply by the word “intuitively”; it’s that it eventually becomes as reflexive and fluid as touch-typing itself.

    Exactly like that!

    It’s also another source of the many “I can’t exit Vim” jokes, because it is now genuinely disorienting for me to try to edit text without Vim key bindings.

    Gosh you make it sound almost like you play Vim like an instrument more than use it…!

    That’s a great analogy. It does very much feel that way.

    Honestly that sounds cool _

    It is pretty cool.

    Wether it’s really worth the learning curve is probably unique to each person that tries it. But for folks who need to edit a lot of text a lot of the time, it’s pretty great.




  • Doesn’t matter we will tell you either way.

    • Instead of simply shortcuts, vim uses “chords”. Every new shortcut I learn can be combined intuitively* with all the other shortcuts I know.
    • Because of this there’s no faster way to edit files than Vim in the hands of an experienced user.
    • this let’s me spend almost no time editing code, freeing up the rest of my time for swearing at piss poor documentation.

    * I use “intuitively” here in a way that not merely stretches, but outright abuses the definition of the word.



  • MajorHavoc@programming.devtoLinux@lemmy.mlThe Dislike to Ubuntu
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    edit-2
    3 days ago

    Ubuntu was a big part of my path to full time Linux use. I adore everyone who has contributed to Ubuntu.

    But also, Snaps are bullshit, and are why I replaced all my Ubuntu installs with Debian.

    Canonical doesn’t get to pretend to be surprised by the backlash for pushing an unnecessary closed proprietary platform on their freedom seeking users.

    I still adore everyone at Canonical and in the Ubuntu community, for all they’ve done for the Linux community. Y’all still rock. Thanks!




  • Yeah. It’s not hardware, then.

    I would try searching “black screen <bios version>” with any name and version number you can figure out about your bios, next.

    If you can get it back to booting from install media, I would do a full reinstall.

    There’s recovery layers (such as grub shell) that ought to kick in if this was just a display config issue, so I’m thinking corrupted install files is more likely.

    Also, do a careful check through your various BIOS settings - search each one with “Debian 12 <setting name>”, to find out if they work with Debian 12, or need adjusted. Debian 12 supports most boot security features, that I have encountered, but I believe there’s still a couple out there that have to be turned off.

    I suspect your next practical goal will be to get the (presumably failed) bootloader install replaced.

    Edit: Tried to add a lot of specific thoughts as search term leads.






  • MajorHavoc@programming.devtolinuxmemes@lemmy.worldSnap bad
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    edit-2
    10 days ago

    the thing people dislike about that is that you’re silently moved from an open system to a closed-source one.

    Yeah. I didn’t realize I had fallen for it until I tried to automate a system rebuild, and discovered that a bunch of the snap back end seems to be closed and proprietary.

    And a lot of it for no reason. Reasonable apt and flatpak alternates existed, but Canonical steered me to their closed repackaged versions.