From: Nikhil Nair <nn201@cus.cam.ac.uk>
To: blinux-list@GOLDFISH.CUBE.NET
Subject: Re: emacs/vi can coexist...
Date: Mon, 14 Oct 1996 11:37:28 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.3.95.961014113053.23075A-100000@amasis.trin.cam.ac.uk> (raw)
In-Reply-To: <199610110354.VAA00317@zygote.ivory.com>
On Thu, 10 Oct 1996 brian@henge.com wrote:
> > 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.
Absolutely. Sorry, I shouldn't make throw-away comments like that without
explaining what I mean :-). For the record, I'm actually an emacs user
... but then I use Braille rather than speech ...
What I was really thinking is that there could be situations where a vi
user wouldn't actually want to install emacs. On some older laptops,
where disk space may be short, emacs is a bit big to install if you don't
really want it.
But that's not a criticism, just a comment. Anyway, these problems will
become very rare (if they aren't already) since disk sizes are increasing.
Cheers,
Nikhil.
--
Nikhil Nair
Trinity College, Cambridge, England
Tel.: +44 1223 368353
Email: nn201@cus.cam.ac.uk
nnair@debian.org
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
brian
` Nikhil Nair [this message]
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=Pine.LNX.3.95.961014113053.23075A-100000@amasis.trin.cam.ac.uk \
--to=nn201@cus.cam.ac.uk \
--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).