Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 28 Apr 2004 13:02:52 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Jim Gelasakis <gelasakis AT Pulse DOT com DOT au>
cc: cygwin AT cygwin DOT com
Subject: RE: Control G Beep on Telnet session using Cygwin
In-Reply-To: <018601c42cee$8b0a4080$830100c0@plsp002>
Message-ID: <Pine.GSO.4.56.0404281253570.21506@slinky.cs.nyu.edu>
References: <018601c42cee$8b0a4080$830100c0 AT plsp002>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

Jim,

First off, <http://cygwin.com/acronyms/#PCYMTNQREAIYR>.

Your use of the expression "on the server" in the two contexts is
confusing.  I think at this point you'd better provide the exact steps you
use to launch "vi" and "telnet".  AFAIK, vi simply echoes "^G" to the
terminal.  OTOH, telnet simply passes whatever characters it gets from the
remote application to the terminal (which could be "^G").  Why not try to
run "vi" both locally and remotely (via telnet) from the same type of
window (either X or rxvt or a console) and see if you get the same ding.
	Igor

On Wed, 28 Apr 2004, Jim Gelasakis wrote:

> Me Again,
>
> We have determined that a session in Vi when Escape is pressed
> we hear the the beep we want on the server - No sound card is used
> instead it is a system bell.
>
> When we do this through a telnet session the beep still happens on the
> server.
>
> Any ideas on how vi calls this the Beep? And also any ideas on routing
> it to the telnet session?
>
> And yes it is a basic piezo beep not the WAV sound. sorry for the
> maddening....
>
> Kind Regards
> Jim Gelasakis
>
>
>
> -----Original Message-----
> From: Igor Pechtchanski [mailto:pechtcha<at>cs<dot>nyu<dot>edu]
> Sent: Wednesday, 28 April 2004 12:18 AM
> To: Jim Gelasakis
> Cc: cygwin<at>cygwin<dot>com
> Subject: Re: Control G Beep on Telnet session using Cygwin
>
>
> On Tue, 27 Apr 2004, Jim Gelasakis wrote:
>
> > We are using Cygwin version 1.5.5(0.94/3/2) on Windows 2000.
> >
> > I have a telnet session to my Shell - using bash.
> >
> > I want to generate a system beep (not a WAV) in the telnet session.
>
> The Cygwin console uses the MessageBeep functionality of Windows, which
> usually plays a WAV.
>
> > We used to be able to do this previously in MKS using the control ^G
> > statement to generate a system beep to the telnet session through
> > named PIPES.
>
> Huh?  ^G is the BEL character, and should generate a beep (or a ding),
> but what does that have to do with named pipes?
>
> > We have tried many ways through Cygwin but are unable to achieve the
> > same result.  Is their an equivalent way to get this to work??? are we
>
> > able to get this function to work under Cygwin???
> >
> > Any ideas would be appreciated.
> >
> > Kind Regards
> > Jim Gelasakis
>
> If you aren't getting any sound at all, try googling for "cygwin
> defaultbeep".  Otherwise, if you are getting the sound but not the one
> you want, try it from an X application (e.g., xterm).  See
> <http://cygwin.com/ml/cygwin/2004-03/msg00903.html> for more info (be
> sure to read the follow-ups, though).
>         Igor

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/