• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: July 24th, 2024

help-circle
  • I’ve used this neovim keybind for years:

    vim.keymap.set({'n', 'x'}, 'gy', '"+y') -- copy
    vim.keymap.set({'n', 'x'}, 'gp', '"+p') -- paste 
    

    I was able to copy/paste between nvim and other applications on sway, Hyprland, Niri and KDE on Wayland.

    The global clipboard register + should also work in modern regular vim afaik.


  • ne0phyte@feddit.orgtolinuxmemes@lemmy.worldFeature parity or get out
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    2 months ago

    You must use a different Wayland than I do.

    I play competitive multiplayer games with VRR on a 4k240 monitor in a tiling wm with direct scanout. Color management support (HDR, 10bit, anything beyond 8bit sRGB) is also coming along.

    I’ve never had a better working setup than this. Everything on X was painful. Even just getting vsync to work properly used to be tricky in some cases.

    I agree that wayland does miss features compared to X but a lot of them are conscious design decisions and don’t affect me personally. For example running graphical applications remotely through e.g. SSH or the complete lack of security allowing any application to easily read my keyboard input.



  • But to be fair, Nix is not the only answer to that. There are lots of tools for just dotfiles but you can also build something using e.g. ansible to manage everything.

    All my computers have their config in a git repo. That includes users, packages, services, dotfiles, /etc configs and so on. I used ansible before writing my own tool. I can install Arch from scratch and only need to partition, run one script and then apply my config on first boot using my tool to have my system restored. I know it’s not as declarative and absolute/reproducible as Nix, but it works and it’s way less painful than my last attempt at giving NixOS a go.


  • The code of the packages is the documentation. So the newcomers better start learning Nix language and reading the paper about how Nix works under the hood before they get started! /s

    But seriously, I used NixOs for about 2 years almost 10 years ago and while it was/is fascinating when you have everything setup, getting there and maintaining everything across so many packages that each have their own way of configuring them took hundreds of hours. I’m back on Arch using a custom tool I wrote to fully manage my configs, packages, dotfiles etc.

    The way I remember it is that there is no consistency across Nix packages and it all feels like a giant puzzle for people who enjoy spending time configuring more than actually using the computer. And I say that as someone who actually enjoyed getting into that when I had unlimited time.