Date: Thu, 1 Feb 1996 13:42:32 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Multiscreen, Bell & Talk Message-ID: <199602012042.NAA13624@phaeton.artisoft.com> In-Reply-To: <MHamD4nmZ2@ache.dialup.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Feb 1, 96 06:28:36 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602012042.NAA13624>