edit:

I’ve updated & expanded the list (finished for today)

  • WereCat@lemmy.worldOP
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    3 days ago

    IDK why the Atuin config file that got generated is commented out in it’s entirety and nothing works. Right now I can’t be bothered to go trough the entire config and enable things one by one. From what I’ve tried nothing works and IDK why. CTRL+R does not invoke the Atuin search it still invokes the old one. I uncommented everything and still nothing seems to work. The atuin definitely responds to my commands in terminal though. I did run atuin setup as well.

    edit: OK, I’ve spent another 30min+ on this and I still can’t understand why it does not work. I’ve adjusted config, even got a custom config from other users and I can’t seem to be able to invoke it in the terminal besides using it’s commands which are the only thing that seem to work. I was able to make an account and login via terminal as well.

    edit2: Figured it out! I’ve tried mcfly and encountered the same issue. Turns out I needed to edit .bashrc which is read only even for sudo and even after chmod. So after beating my head against a wall I’ve realized that .bashrc is symlinked to my home.nix and that’s where I need to place my edits. So now mcfly runs fine and I’m assuming Atuin would as well since after looking at github I pretty much had to do the same edit for both.

    • ivn@tarte.nuage-libre.fr
      link
      fedilink
      Français
      arrow-up
      3
      ·
      3 days ago

      You don’t need to add mcfly bash integration to your .bashrc manually. Remove it from home.packages and instead enable the home-manager module with programs.mcfly.enable = true;. That’s all you need to do, it has a enableBashIntegration setting that’s true by default. Same for atuin, programs.atuin.enable = true; is enough.

      It’s an habit you have to learn when switching to nix, check first if there is a module for the program you want to install before resorting to home.packages or environment.systemPackages.

      • WereCat@lemmy.worldOP
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        I thought that I’ve already replied but apparently not… Thanks for this. I did not realize it’s this simple. Looks like I’ve found one of the many instances where I can make this work differently while it may not be optimal to do so :)