• 0 Posts
  • 18 Comments
Joined 4 years ago
cake
Cake day: June 1st, 2020

help-circle
  • That’s… all stow does, there’s nothing more to it. If you need some other feature don’t waste your time trying to make it work with stow, It’s just a meme in my opinion.

    About the “package manager” functionality, stow was originally supposed to be a development tool for the Perl programming language, you download a bunch of libraries into a directory, then use stow to merge those files into the root of your project (like a caveman), as it turned out some people started using it to manage dotfiles, and here we are.

    When I started trying to organize my dotfiles, I started with stow, but quickly found it very limited.

    After that I found dotdrop, which is considerably more involved, but gives you total control. My config with dotdrop quickly started growing insanely huge, at some point I even had system-wide systemd services declared.

    Then I found out I was basically reinventing nixos and home-manager, so I switched to that.















  • Long-ish time Kakoune user here.

    For those who have tried Kakoune, once you’ve included things like Treesitter and the clangd language server, which one feels faster, Kakoune or Neovim?

    I never felt the need to install something like Treesitter because I feel selection-based editing is already powerful enough, if that gives you an idea of how much faster I am with Kakoune compared to Neovim. Maybe I just don’t know everything Treesitter can do 🤔

    which apparently allows you to have one master Kakoune instance and multiple slave instances that would be in sync

    It’s not a master/slave setup, it really is client/server, even the first instance of kakoune that you open will be a client that you can close without the other instances going down with it.

    I’m not sure if Kakoune shares the clipboard with all of those instances?

    Yup, all shared: registers, buffers, marks, hooks. (You can choose not to share stuff between clients)


  • ~/.config/mimeapps.list contains a line “terminal=foot.desktop” (tried also without .desktop).

    I don’t think that is a real option.

    There is no standard way to set the default terminal emulator, you need to tell your launcher application(sometimes through your DE settings) to use that terminal. For example, j4-dmenu-desktop has the option --term.

    As a file managers I use lf and nnn, they both contain .desktop-files but I can’t launch them with keybinds or menu launcher. Same applies to vim.desktop, nothing happens.

    How are you launching these programs? For keyboard shortcuts you generally need to specifically run the terminal emulator together with the program: bindsym Mod4+Return exec alacritty -e hollywood

    Edit. I managed to find a workaround for lf and nnn by editing the Exec= line in /usr/share/applications/*.desktop file. (Exec=/usr/bin/foot -e nnn) but I still can’t figure the swayimg imageviewer.

    I would advise you to copy those files to ~/.local/share/applications so they do not get overwritten during updates.




  • I work with backend web development, so running code could not be any easier, normally there’s a docker image setup watch for changes, recompile and execute.

    My text editor is Kakoune, after learning the keybindings I just cannot go back to vim or vscode, selection based editing just makes so much sense to me.

    I use NixOS, which comes in handy for keeping my home and office computers in-sync. I also use nix shells to declare the tools necessary to develop each project.

    As for window management I use sway, one big window for kakoune to the left, other terminals for docker/tests/git to the right.