Xref: utzoo comp.emacs:3255 comp.unix.wizards:7895 comp.sources.wanted:3907
Path: utzoo!mnetor!uunet!husc6!cmcl2!beta!unm-la!unmvax!turing.UNM.EDU!mike
From: mike@turing.UNM.EDU (Michael I. Bushnell)
Newsgroups: comp.emacs,comp.unix.wizards,comp.sources.wanted
Subject: Re: talk and talkd
Message-ID: <969@unmvax.unm.edu>
Date: 19 Apr 88 22:36:59 GMT
References: <233@jim.odr.oz>
Sender: news@unmvax.unm.edu
Reply-To: mike@turing.UNM.EDU.UUCP (Michael I. Bushnell)
Organization: University of New Mexico, Albuquerque
Lines: 31
Keywords: talk talkd

In article <233@jim.odr.oz> brw@jim.odr.oz (Brian Wallis) writes:

>Does anyone know the protocol that the `talk' program uses to talk to the
>daemon `talkd'? Or does anyone have source to a PD `talk' program?
>(In case it's relevant, we are running Ultrix 2.0 on a MvaxII + SunOS 3.2
>on a Sun3/110)

Yeah, I know the protocol.  I am working on an emacs lisp/c program to
do talk in emacs.  You can figure out the protocol, kind of, from the
relevant include file.  Incidentally, talkd is used only to rendezvous
the talks.  It doesn't transfer the info, the talks do that
themselves.

>What I would like to do is write a version to use with a GNU emacs `talk'
>mode rather than suspend emacs each time I use talk (a lot).

>I'd also like to stop talkd splattering it's message all over the screen, a
>message in the mode line and ringing the bell would be better.

Since talkd is the system program, you can't change its behavior.
Sigh.

                N u m q u a m   G l o r i a   D e o 

			Michael I. Bushnell
			HASA - "A" division
14308 Skyline Rd NE				Computer Science Dept.
Albuquerque, NM  87123		OR		Farris Engineering Ctr.
	OR					University of New Mexico
mike@turing.unm.edu				Albuquerque, NM  87131
{ucbvax,gatech}!unmvax!turing.unm.edu!mike