public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Dave Hunt <dave.hunt2@verizon.net>
To: blinux-list@redhat.com
Subject: Re: Linux, how do you eat yours?
Date: Thu, 4 Dec 2003 09:11:52 -0500 (EST)	[thread overview]
Message-ID: <16335.16552.833042.129088@localhost.localdomain> (raw)
In-Reply-To: <001301c3ba58$1f4e0100$27356bd5@NigelStoppard>

Hi,

Many of the tools I use with emacspeak are either entirely written in
emacs-lisp or front ends for accessing tools written in other
languages.  Emacspeak, itself, is one of the former.  All these are
extensions of emacs's feature set.  

I have three web clients I use with emacspeak,  w3, w3m, and lynx.
There's a nice mode for launching and running lynx from within
emacspeak.  W3 is a web client, written entirely in emacs-lisp.  Finally, there's a
speech-enabled "front end" for the w3m web client.  I need three
because none works on all sites I often visit.  

For irc and other things, I run a shell (mine happens to be BASH),
from within emacs.  All the editing features of emacs are available in
a shell buffer.  Thus, you can move around the buffer, do searches,
save a bunch of commands and responses, and so on.  It's better than
any screen-review mode; you have a running log of your shell session.  


This letter is written with yet another emacspeak-enabled extension
called VM.  


-Dave










  reply	other threads:[~ UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Stoppard
 ` Dave Hunt
   ` Stoppard
     ` Dave Hunt [this message]
       ` Stoppard
         ` Dave Hunt
 ` Kenny Hitt
   ` Kenny Hitt
     ` Stoppard
       ` kenny
 ` Lorenzo Prince
   ` Stoppard
     ` Lorenzo Prince
 ` Jude DaShiell
   ` micq? Stoppard
     ` micq? Dave Hunt
     ` micq? Jois
       ` micq? Stoppard
         ` micq? Jois
     ` micq? Jude DaShiell
       ` micq? Jois
         ` micq? Jude DaShiell

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=16335.16552.833042.129088@localhost.localdomain \
    --to=dave.hunt2@verizon.net \
    --cc=blinux-list@redhat.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).