From owner-freebsd-current Thu Feb 1 07:31:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA03257 for current-outgoing; Thu, 1 Feb 1996 07:31:54 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA03239 Thu, 1 Feb 1996 07:31:33 -0800 (PST) Received: by sequent.kiae.su id AA15328 (5.65.kiae-2 ); Thu, 1 Feb 1996 18:29:28 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 1 Feb 96 18:29:26 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id SAA00589; Thu, 1 Feb 1996 18:28:36 +0300 (MSK) To: current@freebsd.org, S0ren Schmidt Message-Id: Organization: Olahm Ha-Yetzirah Date: Thu, 1 Feb 1996 18:28:36 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Multiscreen, Bell & Talk Lines: 19 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Imagine you work at multiscreen console and someone tries to talk you. And talk requests comes to another (not current) screen, so you may even never notice them. Another variant: ncftp2 produce bell when (long) file transfer is done, since you never hear it from another screen, you forced to check it often. I have syscons patch wich delivers all bells to current screen independently of screen they originally comes. It really helps in situation like this. I saw several multiscreen implementations which do the same thing, f.e. 'screen' program notice you when bell comes to another screen. If no objection comes, I plan to commit the patch. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849