From: Michael Whapples <mwhapples@aim.com>
To: speakup@braille.uwo.ca
Subject: editors
Date: Thu, 01 Nov 2007 12:59:52 +0000 [thread overview]
Message-ID: <1193921992.3402.9.camel@localhost> (raw)
Hello,
I am currently looking for a better editor than my current favourite
(nano). I have just been doing some bash scripting training, and in that
they were teaching using vi (the training was for people who may never
have used unix before), but I have to say I just wasn't getting on with
vi. How does speakup work with vi best? I found it not very good. People
were saying to me that nano isn't so powerful (and I know what they are
getting at), so I am thinking about emacs (or emacspeak). It seems more
to my liking than vi, but I have a few questions about it. If I were to
use emacspeak, how is it best to stop conflicts of speakup and emacspeak
wanting to use the same synth (an apollo in my case)? Or is it good to
use emacs with speakup (so doing away with emacspeak? Or alternatively,
is there any other editors people might suggest.
From
Michael Whapples
next reply other threads:[~ UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
Michael Whapples [this message]
` editors Chuck Hallenbeck
` editors Albert E. Sten-Clanton
` editors John Heim
` editors Albert E. Sten-Clanton
` editors W. Nick Dotson
` editors Michael Whapples
` Editors? Hart Larry
` editors Albert E. Sten-Clanton
` editors dan Murphy
` editors Georgina Joyce
` editors John Heim
` editors C.M. Brannon
` editors Gaijin
` editors Tomas Cerha
` editors Tyler Spivey
` editors Lukas Loehrer
-- strict thread matches above, loose matches on Subject: below --
editors Jude DaShiell
editors Kyrath. (AKA Rob)
` editors Kirk Reiser
` editors Steve Holmes
` editors Alex Snow
Editors TJ McElroy
` Editors Charles Crawford
` Editors Alex Snow
editors Saqib Shaikh
` editors frankiec
` editors Geoff Shang
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=1193921992.3402.9.camel@localhost \
--to=mwhapples@aim.com \
--cc=speakup@braille.uwo.ca \
/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).