From owner-freebsd-current Thu Feb 1 12:28:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA26655 for current-outgoing; Thu, 1 Feb 1996 12:28:42 -0800 (PST) Received: from mpp.minn.net (root@mpp.Minn.Net [204.157.201.242]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA26647 Thu, 1 Feb 1996 12:28:36 -0800 (PST) Received: (from mpp@localhost) by mpp.minn.net (8.7.3/8.6.9) id OAA27026; Thu, 1 Feb 1996 14:27:43 -0600 (CST) Message-Id: <199602012027.OAA27026@mpp.minn.net> Subject: Re: Multiscreen, Bell & Talk To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Thu, 1 Feb 1996 14:27:43 -0600 (CST) From: "Mike Pritchard" Cc: current@freebsd.org, sos@freebsd.org In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Feb 1, 96 06:28:36 pm X-Mailer: ELM [version 2.4 PL25 ME8b] 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. I've thought about doing the same thing myself. However, can you make the bell a different pitch/duration or something so that you have an idea that the bell is ringing in a another screen, and not in the current one? -- Mike Pritchard mpp@minn.net "Go that way. Really fast. If something gets in your way, turn"