Xref: news-dnh.mv.net comp.os.msdos.djgpp:2878
Path: news-dnh.mv.net!mv!news.sprintlink.net!dispatch.news.demon.net!demon!tank.news.pipex.net!pipex!dish.news.pipex.net!pipex!lade.news.pipex.net!pipex!news00.sunet.se!sunic!news99.sunet.se!news.uni-c.dk!diku.dk!terra
From: terra AT diku DOT dk (Morten Welinder)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: That rings a bell!!
Date: 26 Oct 1995 11:01:08 GMT
Organization: Department of Computer Science, U of Copenhagen
Lines: 28
Sender: terra AT tyr DOT diku DOT dk
References: <DH0MLz DOT BzC AT jade DOT mv DOT net>
Nntp-Posting-Host: odin.diku.dk
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp


While using another interrupt sure is possible we are a few who would
like to know what _causes_ this behaviour, so we can really make sure
it is gone.

Morten




"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk> writes:

>  Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote
>(Subject: Re: Error, Emacs for DOS, Random upper case letters):-

>> ... extraneous characters would appear in the buffer when a key was pressed
>> during auto-save in the DOS port of Emacs (like if you press PageDown to
>> scroll the buffer which shows a modified file). ... this is somehow
>> connected to the way the terminal bell is rung on a DOS machine.  The
>> problem never happens if you use visible bell; even under non-visible bell,
>> it never happens until the bell is rung for the first time. ... The way the
>> bell is rung in DOS version of Emacs is by writing the bell character
>> ('\07') to the standard output with a call to write();

>I never get this nuisance in my AAMACS which I wrote. In it when I want to
>ring the bell I directly call the DOS interrupt "AX=0x0200; DX=7; int21;" =
>"send character \007 to stdout (= the screen, there)", bypassing all of
>djgpp's buffers and all of DOS's write-to-file buffers.