From: brian@henge.com
To: blinux-list@GOLDFISH.CUBE.NET
Subject: emacs/vi can coexist...
Date: Thu, 10 Oct 1996 21:54:05 -0600 [thread overview]
Message-ID: <199610110354.VAA00317@zygote.ivory.com> (raw)
Hello Nikhil,
> > also, I have heard work of trying to make a talking shell for the
> > blind. This bothers me. I like bas, other may like tcsh, ksh, or whatever.
> > Why can't a screen reader be written that is independent of the shell?
> I'd be inclined to agree with you - IMHO Braille/speech access software
> should be completely independent of applications, shells etc. (not meaning
> to take anything away from EmacSpeak, but that may not help vi users
> much). Again, though, I'm afraid I don't actually know about this project
> ...
I think we all agree that access software should
be independent from all other software. However,
emacs is not just an editor. If you like vi, emacs has a vi emulator,
or you can also run the real vi in the terminal emulator
of emacs. There are few things you cannot do from
within emacs. I have been running linux with Emacspeak for over 2
years while browsing the web, building kernels, sending/recieving email,
developing new software, writing papers for school, etc.
I appreciate that the emacs vs. vi issue is a religious one for most
people. But Emacspeak allows emacs to act as a complete
speaking environment for unix, and you can use vi to edit files if you want to.
Just my $0.02 worth.
Brian.
--
---------------
Brian L. Sellden - brian@henge.com, brians@usa.net
User of Emacspeak 4.0, making Unix talk.
http://www.henge.com/~brian
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
brian [this message]
` Nikhil Nair
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=199610110354.VAA00317@zygote.ivory.com \
--to=brian@henge.com \
--cc=blinux-list@GOLDFISH.CUBE.NET \
/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).