Date: Thu, 1 Feb 1996 14:27:43 -0600 (CST) From: "Mike Pritchard" <mpp@mpp.minn.net> 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: <199602012027.OAA27026@mpp.minn.net> 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
> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602012027.OAA27026>