4 ms·

Exactly my thought: I switched from screen to tmux years ago, why I should care now? tmux does everything that screen didn't back then, and has improved even mo

by _ak 12y ago

Exactly my thought: I switched from screen to tmux years ago, why I should care now? tmux does everything that screen didn't back then, and has improved even more since then.

skrowl 12y ago
In the *nix world, when something gets abandoned people are pretty quick to move on. I've been using tmux for a long time as well and see no need to even consider going back to screen.
- pilif 12y ago
  screen supports serial lines and zmodem. While that might not be something you'd use a lot these days, it's very handy when dealing with equipment from the stone-age. Thankfully though, I can have both screen and tmux on my machine, so may day-to-day tool is tmux and screen gets used whenever I need a time machine (which still happens at times)
  - raimue 12y ago
    Couldn't you just use minicom, picocom, or some similar tool inside tmux? Is there a unique feature of screen that is not satisfied by these standalone alternatives? I am curious, as for me this setup is good enough to see debug messages on the serial console.
    - pilif 12y ago
      The reason why I prefer screen over minicom is that minicom has a lot of features related to dialling modems and accessing mailboxes, none of which is relevant to the case of setting up equipment. A quick screen /dev/ttyS0 115200 beats writing a configuration file, learning another text based stateful UI and working around various instances of your tool trying to be helpful and helping you dialling a modem. Keep in mind that this could be related to the default minicom config my distro shipped back when I was "evaluating" my options, but because screen works totally well for my cases, I've had since zero motivation to go back and give minicom another try.
      - duskwuff 12y ago
        You might want to give picocom a try. Equivalent command line is: picocom -b 115200 /dev/ttyS0 It's also got a lot of serial-specific features closer to hand, like changing the baud rate, sending a break, toggling RTS/CTS, etc.
        mzs 12y ago
        Or tip or cu too.
  - vdm 12y ago
    cu (from Taylor UUCP) with lrzsz. http://wiki.soekris.info/Updating_Bios http://wiki.soekris.info/Updating_Bios
    - voltagex_ 12y ago
      I have a distinct memory of being unable to quit cu. Was I just missing the SIGHUP command?
wting 12y ago
I've tried switching to tmux a few times but it never stuck because my workflow involves multiple terminals attached to different windows of the same session. However this isn't allowed in tmux without some hackery / wrapper scripts.
- sillysaurus3 12y ago
  Would you mind going into more detail about your workflow? It seems interesting, and I'd like to learn it. You use Ctrl-Alt-F1 through Ctrl-Alt-F6 to fire up multiple terminals, right? You're saying you have screen running on one of those terminals, and then from other terminals you're somehow attaching to different windows of that one screen instance? How's that done? It sounds pretty clever. What are the advantages of doing it that way?
  - ordinary 12y ago
    -x Attach to a not detached screen session. (Multi display mode).
    - sillysaurus3 12y ago
      Indeed, thanks! I really appreciate it! I was hoping to hear about their workflow, though. What are the advantages of using that? How does multi display mode fit into their workflow in practice? I could try to think of use cases myself, but I prefer to learn from the experience of others whenever possible.
  - deleted 12y ago
    [deleted]
- easytiger 12y ago
  > I've tried switching to tmux a few times but it never stuck because my workflow involves multiple terminals attached to different windows of the same session. You are going to need to explain this as it sounds exactly to me what tmux does

by _ak 12y ago

Exactly my thought: I switched from screen to tmux years ago, why I should care now? tmux does everything that screen didn't back then, and has improved even more since then.

skrowl 12y ago

In the *nix world, when something gets abandoned people are pretty quick to move on. I've been using tmux for a long time as well and see no need to even consider going back to screen.

pilif 12y ago
screen supports serial lines and zmodem. While that might not be something you'd use a lot these days, it's very handy when dealing with equipment from the stone-age. Thankfully though, I can have both screen and tmux on my machine, so may day-to-day tool is tmux and screen gets used whenever I need a time machine (which still happens at times)
- raimue 12y ago
  Couldn't you just use minicom, picocom, or some similar tool inside tmux? Is there a unique feature of screen that is not satisfied by these standalone alternatives? I am curious, as for me this setup is good enough to see debug messages on the serial console.
  - pilif 12y ago
    The reason why I prefer screen over minicom is that minicom has a lot of features related to dialling modems and accessing mailboxes, none of which is relevant to the case of setting up equipment. A quick screen /dev/ttyS0 115200 beats writing a configuration file, learning another text based stateful UI and working around various instances of your tool trying to be helpful and helping you dialling a modem. Keep in mind that this could be related to the default minicom config my distro shipped back when I was "evaluating" my options, but because screen works totally well for my cases, I've had since zero motivation to go back and give minicom another try.
    - duskwuff 12y ago
      You might want to give picocom a try. Equivalent command line is: picocom -b 115200 /dev/ttyS0 It's also got a lot of serial-specific features closer to hand, like changing the baud rate, sending a break, toggling RTS/CTS, etc.
      - mzs 12y ago
        Or tip or cu too.
- vdm 12y ago
  cu (from Taylor UUCP) with lrzsz. http://wiki.soekris.info/Updating_Bios http://wiki.soekris.info/Updating_Bios
  - voltagex_ 12y ago
    I have a distinct memory of being unable to quit cu. Was I just missing the SIGHUP command?

wting 12y ago

I've tried switching to tmux a few times but it never stuck because my workflow involves multiple terminals attached to different windows of the same session. However this isn't allowed in tmux without some hackery / wrapper scripts.

sillysaurus3 12y ago
Would you mind going into more detail about your workflow? It seems interesting, and I'd like to learn it. You use Ctrl-Alt-F1 through Ctrl-Alt-F6 to fire up multiple terminals, right? You're saying you have screen running on one of those terminals, and then from other terminals you're somehow attaching to different windows of that one screen instance? How's that done? It sounds pretty clever. What are the advantages of doing it that way?
- ordinary 12y ago
  -x Attach to a not detached screen session. (Multi display mode).
  - sillysaurus3 12y ago
    Indeed, thanks! I really appreciate it! I was hoping to hear about their workflow, though. What are the advantages of using that? How does multi display mode fit into their workflow in practice? I could try to think of use cases myself, but I prefer to learn from the experience of others whenever possible.
- deleted 12y ago
  [deleted]
easytiger 12y ago
> I've tried switching to tmux a few times but it never stuck because my workflow involves multiple terminals attached to different windows of the same session. You are going to need to explain this as it sounds exactly to me what tmux does