[-] throwawayish@lemmy.ml 4 points 9 months ago* (last edited 9 months ago)

It seems as if the uBlue images ship the required OpenRazer kmod by default. Therefore, I would suggest you to take a look at those. You still need to follow some additional steps though 😅. Which might not be very intuitive... Thus, I propose the following: if you'll rebase to uBlue, you might as well rebase to Bazzite. After the rebase has been completed, the (post-)installation software should already give you the option (it's just a simple toggle) to install OpenRazer. The toggle is clearly visible in this frame.

If you perceive Bazzite as too opinionated for your taste, then perhaps you might opt to the following instead:

install-openrazer:
    sudo wget https://download.opensuse.org/repositories/hardware:/razer/Fedora_$(rpm -E %fedora)/hardware:razer.repo -O /etc/yum.repos.d/hardware:razer.repo && \
    ublue-update --wait && \
    rpm-ostree install -y openrazer-meta razergenie && \
    if ! grep -q "plugdev" /etc/group; then \
      sudo bash -c 'grep "plugdev" /lib/group >> /etc/group' \
    ; fi && \
    sudo usermod -a -G plugdev $USER && \
    echo "Please reboot to apply needed changes."

Which should be the just-entry (and thus responsible) for whatever happens after the toggle is enabled*.

[-] throwawayish@lemmy.ml 4 points 9 months ago

I agree that Fedora's habit for pushing (sometimes breaking) changes is definitely something to keep an eye out. However, it has been so good over the last (almost) two years. I would even argue that Fedora has become more self-conscious of the consequences and (especially) how this might affect their more casual user base.

Btw, how long ago did you try out Fedora? FWIW, Fedora (Silverblue; to be more precise^[1]^) was the first distro that I've tried and while I've had some experiences with other distros over time (mostly through dual boot), Fedora (Atomic) seems to have become the distro I call home.


  1. It's probably not as masochistic as you might think for a new user 😅. Though I'd have to say that it took some effort, control and discipline to not instantly go back to Windows (or any other Linux distro for that matter).
[-] throwawayish@lemmy.ml 4 points 9 months ago

Good to see more laptops being release with Dasharo/Coreboot.

Can't agree more. I hope that Framework will soon follow suit.

[-] throwawayish@lemmy.ml 4 points 9 months ago

That’s a 40% price increase just to get your keyboard layout and a CPU upgrade

Fixed that for you*.

[-] throwawayish@lemmy.ml 4 points 9 months ago

Unless you really want vim bindings

I kinda do for how ubiquitous Vim keybindings are.

try them out.

Regardless, I think I will try it out after I'm at least somewhat productive with Vim.

I much prefer the way Kakoune works over vim

I think preference is generally subjective. So you're completely in your right to prefer Kakoune over Vim (and vice versa). Though, if possible, would you mind elaborating what you prefer exactly and why?

while still being close enough so that you can pick it up quickly if you already know vim and the other way around.

Doesn't that disrupt muscle memory?

[-] throwawayish@lemmy.ml 4 points 10 months ago

I have used vim/neovim for years and cannot go back to a non-modal editor. But TBH I got sick of its configuration. You need far too many plugins and config to get things into a sane working order to be usable on a day to day bases for any type of development. It takes ages to learn and become as productive as you were before and a lifetime to refine.

Interesting. Though I can definitely see where you're coming from. Uhmm.., have you used any of the Neovim distributions to make maintenance easier?

For the past year or so I have switched to helix and don’t plan on going back to vim/neovim as my main editor ever again.

Both Helix and Lapce have certainly piqued my interest as FOSS alternatives to VS Code. However, both have issues related to how well their current Vi(m) implementation is. As you've touched upon it; Helix' keybindings and 'sentence-structures' are different to those found on Vi(m).

Furthermore, neither of the two have existed long enough to be able to profess any statement regarding their longevity. Like, there's no guarantee that I can keep using either of the two 20 years into the future. While no program is able to 100% guarantee that, undoubtedly, the track records for both Emacs and Vi(m) testify that -if anything- they would be the most likely ones to survive 20 years down the line; like how they've done for the last couple of decades.

I appreciate the input, but I simply don't want to invest in a program whose future is very unclear to me at this point in time.

[-] throwawayish@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

OP was relatively verbose so I act accordingly. Don't feel compelled to read larger pieces if you're sensitive to wasting your time. I don't recall forcing you to read it, so it's entirely on you. While information density might have suffered, "little info" is too harsh. Though, as long as there's even one sentence of 'original' information (compared to all the other comments) a piece of writing of that length is worth reading IMO. Though, thinking otherwise is definitely justifiable.

[-] throwawayish@lemmy.ml 4 points 1 year ago

Surely dotfiles are meant to change over time?

Indeed. But any and all changes should await my 'permission' of sorts before being committed declaratively (or related) if at all. This might indeed make it hard(er) for software to create and change dotfiles as they will, which is somewhat the intended purpose.

[-] throwawayish@lemmy.ml 4 points 1 year ago

DuckDuckGO for the bangs, with a custom !bang made for my favorite SearXNG instance; on which most of my 'googling' actually happens.

[-] throwawayish@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

I’d say that they’re mainly made for CI/CD, cloud environments etc, and probably not something you want to put in a laptop and use as a daily driver.

Why do you think that? Would you be so kind to elaborate?

[-] throwawayish@lemmy.ml 4 points 1 year ago* (last edited 1 year ago)

You can install Distrobox on Fedora (or any of the distros that support it), create a Debian distrobox on your Fedora install, and within the Debian distrobox you can use apt-get to install whichever Debian package you like. Or..., you could make an Arch distrobox and even install stuff from the AUR. Or really any package from any of your favorite distros as long as it's supported.

[-] throwawayish@lemmy.ml 4 points 1 year ago

Would you be fine with some tooling that enables one to make their own custom iso from an existing distro? This path still allows for a substantial amount of freedom, though it's not a blank slate by any stretch of the imagination. But it makes up for it with how relatively easy and painless it can be.

Or would you instead like to get into the nitty-gritty of things and want all the freedom you'd want? This increased freedom does come with a substantial cost in convenience and labour.

Pick your poison :P . I'll be waiting ;) .

view more: ‹ prev next ›

throwawayish

joined 1 year ago