From owner-freebsd-current Thu Feb 1 12:45:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28040 for current-outgoing; Thu, 1 Feb 1996 12:45:54 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28031 Thu, 1 Feb 1996 12:45:48 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA13624; Thu, 1 Feb 1996 13:42:32 -0700 From: Terry Lambert Message-Id: <199602012042.NAA13624@phaeton.artisoft.com> 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 13:42:32 -0700 (MST) 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 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > 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. Does it deliver the bells in the pitch, frequency, and duration of the originating console, or does it always use the current console settings? I could see it being marginally useful to use the local console (that's what SCO does), on the other hand, being able to identify console beep origination by pitch would keep people from confusing a local event (like a vi error bell) with an event that requires their attention. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.