From owner-freebsd-current Mon Mar 25 08:18:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA06455 for current-outgoing; Mon, 25 Mar 1996 08:18:08 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA06444 for ; Mon, 25 Mar 1996 08:18:01 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id QAA26400 for ; Mon, 25 Mar 1996 16:15:57 GMT Received: from tees by snowdon with SMTP (PP); Mon, 25 Mar 1996 16:10:16 +0000 Received: (from dpr@localhost) by tees (SMI-8.6/8.6.12) id QAA08847 for FreeBSD-current@FreeBSD.org; Mon, 25 Mar 1996 16:16:11 GMT From: Paul Richards Message-Id: <199603251616.QAA08847@tees> Subject: Re: Patch to talkd To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Mon, 25 Mar 1996 16:16:11 +0000 (GMT) In-Reply-To: <11264.827762066@critter.tfs.com> from "Poul-Henning Kamp" at Mar 25, 96 01:54:26 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Poul-Henning Kamp who said > > > I found another problem. I tried doing a "mesg n" in all my xterms > > except one from my .bashrc. However, the xterm that is started with > > "-e systat -iostat" doesn't read my .bashrc (of course), and > > furthermore, it always has zero idle time for some reason (no I'm not > > touching it). Thus, all the unqualified talk messages show up on that > > window. > > All of this would be much better if the timestamp on the tty device-node > was only updated on input... This is exactly the problem I was getting at. Instead of hunting for the window with the talk message you'll just sit there really puzzled since there won't be any talk message, just an occasional beep from somewhere because the message will keep getting overwritten. Even more likely is that you'll see the message appear but it'll vanish before you can work out who to reply to. This is hardly major stuff but you've just moved the problem, everyone told me to use mesg n to which I'll say, why wasn't this the solution in the first place? Thing is, I've now got to remember to set mesg n everytime I start a continually updating process whereas before I didn't because the message would always be there somewhere if I just looked for it. At least previously it was pretty obvious where to place the mesg n. -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155