From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: working with nano
Date: Fri, 16 Jun 2017 16:51:45 +0000 [thread overview]
Message-ID: <CAO2sX33LTChmNgbg+cOXFdFx1NC8bonUUOgWtTCO1G1nb6E7yg@mail.gmail.com> (raw)
In-Reply-To: <42cf078b-c1a9-8184-1a51-930e9fa07103@verizon.net>
You guys make me feel like a wet behind the ears baby(which feels kind
of weird since people on the Internet usually make me feel like a
fossil). Anyways, in 1990, all I knew about computers was how to suck
at Super Mario Bros. and Super Mario Bros. 3 on my older sister's NES,
it was 1996 before I learned how to touch type on old Win 3.1 and DOS
machines at school, and my family's first proper PC was a Win98
Machine. I made the switch from WinXP to Ubuntu around Ubuntu 5.10 or
6.06 and then to Debian somewhere around 2010, but prior to my vision
failing in mid-to-late 2012, I did most of my document editing in
graphical editors only occasionally using nano to edit my sources.list
or another config file that requires root privileges. As vision loss
forced me to make heavier use of my terminal knowledge, nano became my
primary editor out of familiarity, though I'll admit it took me a
while to get use to it having different cut, copy, paste behavior from
pretty much every graphical application with a text box I've ever
used. I don't think I've ever tried emacs, but what I've tried of vi
has brought me to the conclusion that, even if it's ultimately a
superior editor, I don't have the time to learn vi well enough to use
it on par with how I already use nano.
--
Sincerely,
Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
-- strict thread matches above, loose matches on Subject: below --
Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
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=CAO2sX33LTChmNgbg+cOXFdFx1NC8bonUUOgWtTCO1G1nb6E7yg@mail.gmail.com \
--to=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).