[TriLUG] question about ytalk

[Warren Myers]

Hey Jym,

I was kind of afraid the answer would be "open the code and poke around" ..
not that I'm averse to doing such things... but I am distinctly out of
practice in that area (from shame! I used to love coding, and now can barely
stand it... guess that's what cruddy professors do to you in college... but
I digress).

What I've been doing is starting a screen session per person I want to talk
to, and them doing the same, then starting ytalk in the screen session so we
can come back to it later. The only reason to want the comm side-by-side is
that a typical line back and forth is only a few words, and there's alot fo
wasted space on the screen when it's over-under.

-Warren

On Thu, Aug 19, 2010 at 12:07, Jym Williams Zavada <trilugj at jrwz.net> wrote:

>
> Anyway, Warren, I don't know that there's a way to do what you want with
> ytalk other than by editing the source and doing a re-compile.  I think
> you'd have a quicker time of it combining 'write' with 'screen', to be
> honest.  However, when I need a quick-n-dirty way to talk to somebody like
> that, I just open up another ssh session and fire up the write command (then
> iform the other party to do the same :).  Although it's not anywhere near as
> tidy screenwise as talk/ytalk, it's is pretty much ubiquitous to *nix (I've
> not enough experience on HPUX and AIX to say for sure that it *is* there,
> but I recall using it on both AT&T and BSD systems back in the day, so I
> can't imagine why either of the two would *not* have it implemented), so
> unless you're dealing with customised, very minimalist systems it should be
> a part of the kit.
>
> -Jym Williams Zavada
>