[09:26] <JonathanD> Good morning.
[10:17] <rmg51> Morning
[10:21] <JonathanD> Baking ice cream muffins.
[13:20] <teddy-dbear> Morning peoples, dogs, turkeys and everything else
[13:21] <teddy-dbear> JonathanD: bring me some of those ice cream muffins :-D
[13:55] <JonathanD> teddy-dbear: come get em
[13:55] <teddy-dbear> I can't drive :-(
[13:55] <JonathanD> muffinapult
[13:55] <teddy-dbear> and it;s too long a walk
[13:55] <teddy-dbear> send them my way
[13:56] <teddy-dbear> I'll catch them
[15:01] <ChinnoDog> ice cream muffins?
[15:02] <JonathanD> ChinnoDog: ice cream muffins.
[15:03] <ChinnoDog> I want ice cream muffins.
[15:45] <ChinnoDog> On an unrelated subject, I realized yesterday that I didn't know how to properly use screen.
[15:46] <ChinnoDog> I thought you were supposed to create a separate screen session to encapsulate every TTY so that you could arbitrarily detach from them and attach to a different one.
[15:46] <ChinnoDog> Now I know you are only supposed to create one screen session and it encapsulates multiple TTYs
[19:09] <square-r00t> i don't think there's really a "right" way to use screen
[19:09] <square-r00t> kind of like there isn't a "best" desktop environment-
[19:09] <square-r00t> all depends on preference and personal workflow style
[19:10] <ChinnoDog> It is slow and awkward to switch terminals with multiple instances of screen, not to mention it wastes memory.
[19:11] <ChinnoDog> now I "ctrl+a, c" for a new TTY and "ctrl+a, n" to switch to the next one.
[19:12] <ChinnoDog> And I don't have to worry about accidentally starting or restoring one screen session inside another.
[20:10] <jedijf> ChinnoDog: thats how bosses do it
[20:11] <jedijf> others do the ind 'named' sessions - i like the one
[20:19] <square-r00t> jedijf: you can still name sessions when multiplexing :)
[20:26] <jedijf> yes, but that got old
[20:26] <jedijf> more to type