[Prev][Next][Index][Thread]

# The best way for @beep

- Date: Tue, 3 Sep 1996 01:48:06 PDT
- From:
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- References: <v03007801ae5189b90f66@[132.76.55.130]>

    Hmm
    set_connection_option() is ok for making a @beep command?
    I dislike to do it this way, lot error checking.
    I preffer to use a wiz read only prop named .bell being a string with
    ascii value 7
    I know to ouput this char to a connection using binary conns...
    Is the only way to enter this value in de core, to hack it?
    I know that Lambdacode manual onky talks about binary conns and not
    about hack :) But I still think this is a more robust way to implement
    things like ANSI color and beeps than using a dangerous binary conn.
    Maybe binary conns are fine for other things like file exchange with
    other sites.

    I ve seen Dark Owl's ANSI system 2.1 and does it this way, but looks
    like a plugin to <1.8.0 server. Maybe with >1.8.0 it is done differnet
    way?

Follow-Ups:

- Re: The best way for @beep

- From: Don Schwarz <darkowl@darkowl.pr.mcs.net>

References:

- MOO types trivia

- From: Gustavo Glusman <bmgustav@bioinformatics.weizmann.ac.il>

- Prev: Re: Bb's Wish List (Sept 96)
- Next: Re: The best way for @beep
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index