working with nano

Fri Jun 16 18:37:44 UTC 2017

I know there's a way to have nano perpetually display current line,
column, and character counts, though I have no idea what you'd add to
nanorc to make it the default behavior or what keyboard shortcut
toggles it(ctrl+c makes nano display this information until you type
or delete another character, which I've always found sufficient).

speakup reading the perpetual position display, if active, instead of
echoing keystrokes sounds consistent with my attempts at using that
screen reader, which coupled with it's tendency to read the line nano
just scrolled onto the screen instead of the line the cursor was just
moved to is among the reasons I don't care for speakup.

On 6/16/17, Linux for blind general discussion <blinux-list at redhat.com> wrote:
> Actually, all showcursor does is the same thing showcursor does in lynx,
> it shows the cursor on the screen.  It does not display coordinates on
> any part of the screen while typing, I know I tested it.
>
> On Fri, 16 Jun 2017, Linux for blind general discussion wrote:
>
>> Date: Fri, 16 Jun 2017 11:24:35
>> From: Linux for blind general discussion <blinux-list at redhat.com>
>> To: blinux-list at redhat.com
>> Subject: Re: working with nano
>>
>> 	This has been an interesting thread so far. I began using
>> unix in 1989 on a DEC system which used the trade name of Ultrix
>> and the standard editor was vi so I've stuck with vi ever since
>> since it is so common.
>>
>> 	Well, ultrix went away many years ago and my working
>> group used Sunos for several years as well as IBM's aix and
>> finally Linux and I kept using vi.
>>
>> 	To me, nano was and mostly still is that aggravating
>> application one gets on a new Debian system before we have time
>> to fix it.
>>
>> 	I have on rare occasions used it long enough to do
>> something that just had to be done quickly and wasn't too
>> complicated but the first thing I noticed was that rather echoing
>> the characters I was typing, it echoed the current column number
>> on the line which is probably what happens with show-cursor on.
>>
>> 	As I said, this usually happens when you are trying to
>> fix something that is seriously broken and people are waiting and
>> breathing down one's neck so I have never been too happy to hear
>>
>> "gnu nano 2.x.y" instead of what one usually hears when vi or vim
>> fires up and one knows what the keys do so you can concentrate on
>> the task at hand.
>>
>> 	Shortly before I retired, one of my coworkers asked me if
>> I would put nano on the FreeBSD system we were using as the unix
>> machine in our department. I installed it with no problem and
>> realized that I was dealing with someone who was used to nano and
>> didn't like to use vi any more than I liked to be forced to use
>> nano so as far as I was concerned, it was turn abouts, fair play.
>> It's kind of a case of saying "yes" when you possibly can rather
>> than hassling somebody over basically nothing.
>>
>> 	When I first started out in 1989, I was using an EchoGP
>> hardware synth through an IBM PC/XT running DOS and kermit as the
>> terminal emulator and I now use Debian Linux with speakup. These
>> are the good old days right now-- not perfect, but certainly
>> better than when I first started using computers which was 1979
>> on an Apple II followed in the eighties by IBM PC's and clones.
>>
>> 	By the way, elvis was a DOS version of vi that I used a
>> lot back in the day. Don't forget that we all walked 5 miles up
>> hill to and from school in the snow even in Summer.
>>
>> Martin McCormick
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> --
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

-- 
Sincerely,

Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.