Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I love screen too.

    I really suggest doing three things when using screen:

        1. Having a screen number -> task convention (screen 0 is
                editor, screen 1 is mail, etc..).

        2. Using screen's bindkey to let you jump easily between the
                various screens. I use the GTK-tabbed-view-compatible
                alt-# convention.

        3. Setting up a bindkey for MRU scr
    • by gnat (29) on 2004.03.17 20:45 (#29442) Journal
      Mary Poppins writes:
      really suggest doing three things when using screen:
      1. Having a screen number -> task convention (screen 0 is             editor, screen 1 is mail, etc..).
      2. Using screen's bindkey to let you jump easily between the             various screens. I use the GTK-tabbed-view-compatible             alt-# convention.
      3. Setting up a bindkey for MRU screen (I use alt-dash).
      Absolutely! It's the same for me and iTerm [sf.net]--keep the mail tunnel in tab 0, BitTorrent downloads in tab 1, then conferences shell, remote database login, and anything else I need in the subsequent tabs. Consistency lets you do a lot of things without thinking.

      I suspect it's the same with how people lay out their screens. I wish I'd been at etech for danny's session [martian.org].

      --Nat

      • One important difference between screen and a tabbed
        terminal window is the client-server nature of screen. You
        can have more than one screen client attach to a given
        screen daemon. I leave a screen daemon running on my
        machines for months, and detach when I leave the office,
        then later ssh in from home and reattach. No X forwarding,
        rdesktop, or VNC required -- just plain ssh, and I'm right
        where I left off.

        I browse use.perl.org from a w3m browser running inside a
        more-or-less-permanent screen daemon on the se