I get that it’s open source provided you use codium not code but I still find that interesting

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

    I have the exact same setup.

    Do you use tmux on your main computer, especially if you’re using a WM? I can’t imagine the need for tmux with tiling window managers if you have workspaces and can partition windows how you like.

    • nybble41@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Not the GP but I also use tmux (or screen in a pinch) for almost any SSH session, if only as insurance against dropped connections. I occasionally use it for local terminals if there is a chance I might want a command to outlive the current graphical session or migrate to SSH later.

      Occasionally it’s nice to be able to control the session from the command line, e.g. splitting a window from a script. I’ve also noticed that wrapping a program in tmux can avoid slowdowns when a command generates a lot of output, depending on the terminal emulator. Some emulators will try to render every update even if it means blocking the output from the program for the GUI to catch up, rather than just updating the state of the terminal in memory and rendering the latest version.

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

        I would definitely use tmux on my servers, but I’m wondering about why I’d use it for the desktop. Your use-case of needing commands/output beyond the need of a graphical interface is interesting (would like to know a couple of examples), I should probably consider that.

        I can do the splitting with a window manager though, wouldn’t need tmux for that. I agree with the program GUI part.

        • nybble41@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Examples of local commands I might run in tmux could include anything long-running which is started from the command line. A virtual machine (qemu), perhaps, or a video encode (ffmpeg). Then if I need to log out or restart my GUI session for any reason—or something goes wrong with the session manager—it won’t take the long-running process with it. While the same could be done with nohup or systemd-run, using tmux allows me to interact with the process after it’s started.

          I also have systems which are accessed both locally and remotely, so sometimes (not often) I’ll start a program on a local terminal through tmux so I can later interact with it through SSH without resorting to x11vnc.

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

            Thanks for the comment. Long-running commands make a lot of sense.

            Do you happen to run your GUI session inside of a tmux session? If you log in and out, wouldn’t the tmux session inside of the user-session terminate?