Date: Fri, 2 Feb 1996 02:36:01 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su> To: Terry Lambert <terry@lambert.org> Cc: current@freebsd.org, sos@freebsd.org Subject: Re: Multiscreen, Bell & Talk Message-ID: <FGXvK4nig2@ache.dialup.ru> In-Reply-To: <199602012042.NAA13624@phaeton.artisoft.com>; from Terry Lambert at Thu, 1 Feb 1996 13:42:32 -0700 (MST) References: <199602012042.NAA13624@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199602012042.NAA13624@phaeton.artisoft.com> Terry Lambert
writes:
>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.
I can use originating console pitch value, but usualy it is the same
as current console have.
So, I can up or down originating console pitch with some const
instead.
--
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FGXvK4nig2>