Do you create a toolbox (or equivalent) to modify your interactive shell for all those nice little shell commands/programs? Seems like a pain in the ass to have to launch your terminal from a terminal (toolbox --enter whatever, just to have (doom) emacs, fzf, fdfind, qalc, nnn, zoxide etc etc) just to have a comfortable terminal?

  • j0rge@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I just set mine up to always go into the toolbox image and then I have all the tools I have in there, that way it’s transparent and fast, you shouldn’t even notice that it’s there.

  • Kekin@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I use Fedora Kinoite and I do a mix of Distrobox + layered packages for normal use. For development porpuses I prefer a Distrobox container with its own Home directory and it works nice.

  • theonlykl@partizle.com
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    MicroOS user here. Honestly I love the workflow of using distrobox for about everything I need.

    Essentially I have distrobox images setup for specific development workflows. I just hop into the one that is suited for the task I’m doing. It automatically sets up icons in the Gnome menu if you don’t want to use the cli commands.

    Between flatpaks and containers I couldn’t be happier with my setup. Combine that with the fact I can potentially trust the underlying OS to not crap the bed via updates (and when it does I can roll back my filesystem snapshots) is a win/win.

  • rwsl@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I use Silverblue. I also use distrobox which can “export” apps from the container to the host. This way I can just type nvim in the host and it’ll go into the container and start nvim there.

  • Amy@pawb.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I use a distrobox for development and almost everything as a flatpak

    But I layer packages for terminal apps because I can access them without opening a container