public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "T. V. Raman" <raman@Adobe.COM>
To: bsmart@pobox.com
Cc: raman@Adobe.COM, blinux-list@redhat.com
Subject: Immediate silencing emacspeak
Date: Sat, 19 Dec 1998 16:43:40 -0800 (PST)	[thread overview]
Message-ID: <13948.18492.246137.462038@labrador> (raw)
In-Reply-To: <13947.21511.658203.674367@stono.cs.cofc.edu>

>From memory, I have now told you *many* times --politely at
first--
to post emacspeak specific questions to the emacspeak list
so the question and response gets archived. >>>>> "Bryan" == Bryan R Smart <bsmart@CS.cofc.EDU> writes:

    Bryan> On my system, recreating this problem depends on
    Bryan> first the type of buffer and then the size of
    Bryan> data.  Emacspeak-speak-buffer, for example, will
    Bryan> respond to dtk-stop regardless of the size of
    Bryan> data that is dumped to the DECtalk.  On the other
    Bryan> hand, output from shell mode, if it exceeds a few
    Bryan> K, will hopelessly lockup the DECtalk.  I can,
    Bryan> for example, accidently type a shell command that
    Bryan> returns a large amount of output.  Even though
    Bryan> the command has completed and the shell prompt is
    Bryan> again visible, the DECtalk will not respond to
    Bryan> dtk-stop.

    Bryan> Another example is when you inadvertently open a
    Bryan> nontextual file in an edit buffer.  Pressing the
    Bryan> down arrow will produce a large amount of octal
    Bryan> values and such.  The introduction of the "speak
    Bryan> this XXX line" question in Emacspeak 9.0 has
    Bryan> helped me avoid this problem, but, regardless of
    Bryan> being able to avoid it, it ignores dtk-stop in a
    Bryan> similar manner as the large amount of shell
    Bryan> output.

    Bryan> I am running Emacspeak 9.0 on Emacs 20.3 with a
    Bryan> revision 4.2CD DECtalk Express.



    Bryan> I've long suspected that Raman's DECtalk is
    Bryan> superior to what is commonly available.  -- Bryan
    Bryan> R. Smart E-Mail: bsmart@pobox.com System
    Bryan> Administrator Home Page:
    Bryan> http://www.pobox.com/~bsmart Department of
    Bryan> Computer Science Home Phone: 843-953-2721 the
    Bryan> College of Charleston DCS Phone: 843-814-7627
    Bryan> (814-SMARt)

-- 
Best Regards,
--raman

      Adobe Systems                 Tel: 1 408 536 3945   (W14-128)
      Advanced Technology Group     Fax: 1 408 537 4042 
      W14-128 345 Park Avenue     Email: raman@adobe.com 
      San Jose , CA 95110 -2704     Email:  raman@cs.cornell.edu
      http://labrador.corp.adobe.com/~raman/        (Adobe Intranet)
      http://cs.cornell.edu/home/raman/raman.html    (Cornell)
----------------------------------------------------------------------
    Disclaimer: The opinions expressed are my own and in no way should be taken
as representative of my employer, Adobe Systems Inc.
____________________________________________________________


           reply	other threads:[~ UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <13947.21511.658203.674367@stono.cs.cofc.edu>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13948.18492.246137.462038@labrador \
    --to=raman@adobe.com \
    --cc=blinux-list@redhat.com \
    --cc=bsmart@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).