After a long time I’m in a situation where I sometimes work on a temporary system without my individual setup. Now whenever I might add a new custom (nushell) command that abstracts the usage of CLI tools, I think about the loss of muscle memory/knowledge for these tools and how much time I waste looking them up without my individual setup. No, that’s not a huge amount of time, but just out of curiosity I’d like to know how I can minimize this problem as much as possible.

Do you have some tips and solutions to handle this dilemma? I try to shadow and wrap existing commands, whenever it’s possible, but that’s often not the case. Abbreviations in fish are optimal for this problem in some cases, but I don’t think going back to fish as my main shell for this single reason would be worth it.

  • MajorHavocEnglish
    1·
    16 days ago

    but in this case it’s a Windows Sandbox.

    If it’s Windows 10 or later, winget is preinstalled (sort of / mostly) and has acess to a release of git. (WinGet is available on ‘Modern’ Windows 10 and later., and it may take a few minutes to bootstrap itself after first login.)

    So I’m able to bootstrap this pattern on Windows with something like:

    winget install --id Git.Git -e --source winget

    Syntax from Stack Overflow

    I’m pretty sure I just use winget install Git.Git, but someone on SO recommends the above longer version. I’m guessing it prevents an interactive prompt, since there are more than one package source for git, if I recall.