re: working with nano

re: working with nano

[Linux for blind general discussion]

the nano Mark has is probably pretty old.  Put a # in front of line 12 
that says set linenumbers for now and you should get past that line.
line numbers do work in the current nano archlinux version.



--

re: working with nano

[Linux for blind general discussion]

Mark here,
How do i get a newer one?


Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!

On Wed, 14 Jun 2017, Linux for blind general discussion wrote:

> the nano Mark has is probably pretty old.  Put a # in front of line 12 that
> says set linenumbers for now and you should get past that line.
> line numbers do work in the current nano archlinux version.
>
>
>
> --
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

re: working with nano

[Linux for blind general discussion]

Well Mark, you can either try
sudo apt-get install nano
or
sudo aptitude install nano
On my Vinux it says 2.2.6  but here on Shellworld, its something like 2.53
Chime

re: working with nano

[Linux for blind general discussion]

If you're using debian:
apt-get upgrade <cr>
or aptitude --safe-upgrade <cr>
Fedora:
man dnf and use that to do the upgrades.

On Wed, 14 Jun 2017, Linux for blind general discussion wrote:

> Date: Wed, 14 Jun 2017 17:27:05
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: Linux for blind general discussion <blinux-list@redhat.com>
> Subject: re: working with nano
> 
> Mark here,
> How do i get a newer one?
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>
>> the nano Mark has is probably pretty old.  Put a # in front of line 12 that
>> says set linenumbers for now and you should get past that line.
>> line numbers do work in the current nano archlinux version.
>>
>>
>>
>> --
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

-- 

re: working with nano

[Linux for blind general discussion]

Mark Peveto here.
apt-get upgrade <cr> returned errors.  Unexpected tokin and all that.  Didn't work.



Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!

On Wed, 14 Jun 2017, Linux for blind general discussion wrote:

> If you're using debian:
> apt-get upgrade <cr>
> or aptitude --safe-upgrade <cr>
> Fedora:
> man dnf and use that to do the upgrades.
>
> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>
> > Date: Wed, 14 Jun 2017 17:27:05
> > From: Linux for blind general discussion <blinux-list@redhat.com>
> > To: Linux for blind general discussion <blinux-list@redhat.com>
> > Subject: re: working with nano
> >
> > Mark here,
> > How do i get a newer one?
> >
> >
> > Mark Peveto
> > Registered Linux user number 600552
> > Everything happens after coffee!
> >
> > On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> >
> > > the nano Mark has is probably pretty old.  Put a # in front of line 12
> > > that
> > > says set linenumbers for now and you should get past that line.
> > > line numbers do work in the current nano archlinux version.
> > >
> > >
> > >
> > > --
> > >
> > > _______________________________________________
> > > Blinux-list mailing list
> > > Blinux-list@redhat.com
> > > https://www.redhat.com/mailman/listinfo/blinux-list
> > >
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
>
> --
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

re: working with nano

[Linux for blind general discussion]

sudo apt-get upgrade <cr>
if you didn't set a root password.

Linux for blind general discussion 
wrote:

> Date: Wed, 14 Jun 2017 22:08:09
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: Linux for blind general discussion <blinux-list@redhat.com>
> Subject: re: working with nano
> 
> Mark Peveto here.
> apt-get upgrade <cr> returned errors.  Unexpected tokin and all that.  Didn't work.
>
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>
>> If you're using debian:
>> apt-get upgrade <cr>
>> or aptitude --safe-upgrade <cr>
>> Fedora:
>> man dnf and use that to do the upgrades.
>>
>> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>>
>>> Date: Wed, 14 Jun 2017 17:27:05
>>> From: Linux for blind general discussion <blinux-list@redhat.com>
>>> To: Linux for blind general discussion <blinux-list@redhat.com>
>>> Subject: re: working with nano
>>>
>>> Mark here,
>>> How do i get a newer one?
>>>
>>>
>>> Mark Peveto
>>> Registered Linux user number 600552
>>> Everything happens after coffee!
>>>
>>> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>>>
>>>> the nano Mark has is probably pretty old.  Put a # in front of line 12
>>>> that
>>>> says set linenumbers for now and you should get past that line.
>>>> line numbers do work in the current nano archlinux version.
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> _______________________________________________
>>>> Blinux-list mailing list
>>>> Blinux-list@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>
>> --
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

-- 

re: working with nano

[Linux for blind general discussion]

Mark here,
Sorry, but taht's not getting it.
It says there are no packages to upgrade.


Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!

On Thu, 15 Jun 2017, Linux for blind general discussion wrote:

> sudo apt-get upgrade <cr>
> if you didn't set a root password.
>
> Linux for blind general discussion wrote:
>
> > Date: Wed, 14 Jun 2017 22:08:09
> > From: Linux for blind general discussion <blinux-list@redhat.com>
> > To: Linux for blind general discussion <blinux-list@redhat.com>
> > Subject: re: working with nano
> >
> > Mark Peveto here.
> > apt-get upgrade <cr> returned errors.  Unexpected tokin and all that.
> > Didn't work.
> >
> >
> >
> > Mark Peveto
> > Registered Linux user number 600552
> > Everything happens after coffee!
> >
> > On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> >
> > > If you're using debian:
> > > apt-get upgrade <cr>
> > > or aptitude --safe-upgrade <cr>
> > > Fedora:
> > > man dnf and use that to do the upgrades.
> > >
> > > On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> > >
> > > > Date: Wed, 14 Jun 2017 17:27:05
> > > > From: Linux for blind general discussion <blinux-list@redhat.com>
> > > > To: Linux for blind general discussion <blinux-list@redhat.com>
> > > > Subject: re: working with nano
> > > >
> > > > Mark here,
> > > > How do i get a newer one?
> > > >
> > > >
> > > > Mark Peveto
> > > > Registered Linux user number 600552
> > > > Everything happens after coffee!
> > > >
> > > > On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> > > >
> > > > > the nano Mark has is probably pretty old.  Put a # in front of line 12
> > > > > that
> > > > > says set linenumbers for now and you should get past that line.
> > > > > line numbers do work in the current nano archlinux version.
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > _______________________________________________
> > > > > Blinux-list mailing list
> > > > > Blinux-list@redhat.com
> > > > > https://www.redhat.com/mailman/listinfo/blinux-list
> > > > >
> > > >
> > > > _______________________________________________
> > > > Blinux-list mailing list
> > > > Blinux-list@redhat.com
> > > > https://www.redhat.com/mailman/listinfo/blinux-list
> > > >
> > >
> > > --
> > >
> > > _______________________________________________
> > > Blinux-list mailing list
> > > Blinux-list@redhat.com
> > > https://www.redhat.com/mailman/listinfo/blinux-list
> > >
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
>
> --
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

re: working with nano

[Linux for blind general discussion]

Actually Mark, if you were to run aptitude  and if it says it cannot find any 
packages, it may reference packages with nano in its description. You can then 
paste those in your next apt-get or aptitude. Otherwise, a more drastic step 
would be useing a question mark, as in
aptitude install nano?
You would probably need to completely become root, but you may also get alot of 
extra packages.
Chime

re: working with nano

[Linux for blind general discussion]

Nope, it didn't pull anything down.  Said no packages will be upgraded installed or removed.  Did as root, too.  Note here that I am not using Vinux.
this is debian.


Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!

On Thu, 15 Jun 2017, Linux for blind general discussion wrote:

> Actually Mark, if you were to run aptitude  and if it says it cannot find any
> packages, it may reference packages with nano in its description. You can then
> paste those in your next apt-get or aptitude. Otherwise, a more drastic step
> would be useing a question mark, as in
> aptitude install nano?
> You would probably need to completely become root, but you may also get alot
> of extra packages.
> Chime
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

Re: working with nano

[Linux for blind general discussion]

I don't know which version of Debian you're running, but I just did
some quick checks, and:
Debian oldstable(Wheezy?) and Debian Stable(still Jessie for now
though I believe Stretch is in Release Candidate) both offer a 2.2.6
version of nano.
Debian Testing, which is what I'm running, has a 2.7 version of Nano.

I don't really follow Nano development, so I have no idea whey the
version number changed so little during the previous Debian release
cycle compared to the current one or what changed between 2.2 and 2.7.

-- 
Sincerely,

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

Re: working with nano

[Linux for blind general discussion]

Mark Peveto here,
 As far as I know I'm running Jessie.


Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!

On Thu, 15 Jun 2017, Linux for blind general discussion wrote:

> I don't know which version of Debian you're running, but I just did
> some quick checks, and:
> Debian oldstable(Wheezy?) and Debian Stable(still Jessie for now
> though I believe Stretch is in Release Candidate) both offer a 2.2.6
> version of nano.
> Debian Testing, which is what I'm running, has a 2.7 version of Nano.
>
> I don't really follow Nano development, so I have no idea whey the
> version number changed so little during the previous Debian release
> cycle compared to the current one or what changed between 2.2 and 2.7.
>
> --
> Sincerely,
>
> Jeffery Wright
> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
> Former Secretary, Student Government Association, College of the Albemarle.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

re: working with nano

[Linux for blind general discussion]

I forgot I haven't used debian for a while.
First sudo apt-get update<cr> then
sudo apt-get upgrade<cr>
The update step updates your local file caches then apt-get with the 
upgrade step can figure out what's available for upgrade and get it done 
for you.

On Thu, 15 Jun 2017, Linux for blind general discussion wrote:

> Date: Thu, 15 Jun 2017 09:20:39
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: Linux for blind general discussion <blinux-list@redhat.com>
> Subject: re: working with nano
> 
> Mark here,
> Sorry, but taht's not getting it.
> It says there are no packages to upgrade.
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Thu, 15 Jun 2017, Linux for blind general discussion wrote:
>
>> sudo apt-get upgrade <cr>
>> if you didn't set a root password.
>>
>> Linux for blind general discussion wrote:
>>
>>> Date: Wed, 14 Jun 2017 22:08:09
>>> From: Linux for blind general discussion <blinux-list@redhat.com>
>>> To: Linux for blind general discussion <blinux-list@redhat.com>
>>> Subject: re: working with nano
>>>
>>> Mark Peveto here.
>>> apt-get upgrade <cr> returned errors.  Unexpected tokin and all that.
>>> Didn't work.
>>>
>>>
>>>
>>> Mark Peveto
>>> Registered Linux user number 600552
>>> Everything happens after coffee!
>>>
>>> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>>>
>>>> If you're using debian:
>>>> apt-get upgrade <cr>
>>>> or aptitude --safe-upgrade <cr>
>>>> Fedora:
>>>> man dnf and use that to do the upgrades.
>>>>
>>>> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>>>>
>>>>> Date: Wed, 14 Jun 2017 17:27:05
>>>>> From: Linux for blind general discussion <blinux-list@redhat.com>
>>>>> To: Linux for blind general discussion <blinux-list@redhat.com>
>>>>> Subject: re: working with nano
>>>>>
>>>>> Mark here,
>>>>> How do i get a newer one?
>>>>>
>>>>>
>>>>> Mark Peveto
>>>>> Registered Linux user number 600552
>>>>> Everything happens after coffee!
>>>>>
>>>>> On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
>>>>>
>>>>>> the nano Mark has is probably pretty old.  Put a # in front of line 12
>>>>>> that
>>>>>> says set linenumbers for now and you should get past that line.
>>>>>> line numbers do work in the current nano archlinux version.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> _______________________________________________
>>>>>> Blinux-list mailing list
>>>>>> Blinux-list@redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Blinux-list mailing list
>>>>> Blinux-list@redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>>
>>>>
>>>> --
>>>>
>>>> _______________________________________________
>>>> Blinux-list mailing list
>>>> Blinux-list@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>
>> --
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

-- 

Re: working with nano

[Linux for blind general discussion]

archlinux has nano version 2.84 on it now.
Syntax for aptitude is first
aptitude update<cr> then
aptitude safe-upgrade<cr>
That should get you updates without breaking anything and will let you 
know which packages were held back.
If you want to find out why packages were held back
aptitude why packagename<cr> ought to get that done.
On Thu, 15 Jun 2017, 
Linux for 
blind general discussion wrote:

> Date: Thu, 15 Jun 2017 10:11:58
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Re: working with nano
> 
> I don't know which version of Debian you're running, but I just did
> some quick checks, and:
> Debian oldstable(Wheezy?) and Debian Stable(still Jessie for now
> though I believe Stretch is in Release Candidate) both offer a 2.2.6
> version of nano.
> Debian Testing, which is what I'm running, has a 2.7 version of Nano.
>
> I don't really follow Nano development, so I have no idea whey the
> version number changed so little during the previous Debian release
> cycle compared to the current one or what changed between 2.2 and 2.7.
>
>

-- 

Re: working with nano

[Linux for blind general discussion]

	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

Re: working with nano

[Linux for blind general discussion]

Yes, this thread is interesting.  I think I'll try some of what people 
have suggested.  I've tried nano a few times, but I clearly didn't find 
all the places where I could learn to make it do more of what I wanted.

In 1979, the only thing I knew about computers was that I didn't have 
one.  I was in school for another line of work.  My serious time on 
computers began in the spring of 1989, and I got at least half-seriously 
into Linux in around 2005.  At that time, such editing as I did was 
using emacs, but mostly I've used vim.

Anyway, I appreciate the info on this thread.

Al

On 06/16/2017 11:24 AM, Linux for blind general discussion wrote:
> 	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@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

Re: working with nano

[Linux for blind general discussion]

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.

Re: working with nano

[Linux for blind general discussion]

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@redhat.com>
> To: blinux-list@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@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

-- 

Re: working with nano

[Linux for blind general discussion]

I bet you still remember how to write kermit scripts too.  That kermit 
sure ate xtalk's lunch for accessibility in dos.

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@redhat.com>
> To: blinux-list@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@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

-- 

Re: working with nano

[Linux for blind general discussion]

I learned to touch type on something that never had electricity running 
through it, a Royal 440 typewriter.  I had a little computer exposure 
before 1986 but got my first computer in that year and that was a CP/M 
machine too.  In 1987 due to college study requirements I went over to 
the dark side with an IBM XT with a 32mb hard drive.  Formal unix 
classes started in 1989 when I started working for the Navy and started 
using the learn utility on bsd systems.  Then in 2001 Windows '98 had to 
be reinstalled by me without any sight using a sheet of brailled 
instructions every two weeks since a kernel file kept getting corrupted 
and that started me on a 1 year long journey with the penguin club of 
Southern Maryland to get linux installed and accessible.  First time 
that happened it was with a copy of redhat 5.0 I bought at Staples. 
Unfortunately Staples doesn't sell Linux any more so I minimize my 
purchases in those stores.
For those that tried vim and ran into trouble with it, you might try ex 
and ex is a line-oriented part of vim with all the power vi part of vim 
is a subset of ex.  If you knew how to use edlin on dos and liked it 
you'll like ex.  Another part of vim and this is really good if less 
isn't available is view that does much of what less does.

On Fri, 16 Jun 2017, Linux for blind general discussion wrote:

> Date: Fri, 16 Jun 2017 12:51:45
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Re: working with nano
> 
> 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.
>
>

-- 

Re: working with nano

[Linux for blind general discussion]

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@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@redhat.com>
>> To: blinux-list@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@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> --
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@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.

Re: working with nano

[Linux for blind general discussion]

Tim here.  Hey, Martin, I love the tales of yore.  I too cut my Unix
teeth on DEC Ultrix machines, have used elvis/stevie as VI clones on
DOS (as well as "ed" on Unixlikes and "edlin" on DOS), played with a
Votrax Apple II hardware speech synthesizer, and also walked to school
up-hill both ways in the snow. (grins)

The round hockey-puck mice on those DEC Ultrix machines had
cutting-edge laser-tracking but were marred by the horrible user
interface where you couldn't tell the mouse orientation by feel
alone.

Guess it's time for this old geezer to go shake my cane at the kids
and tell them to get offa my lawn.

-tim

On June 16, 2017, Linux for blind general discussion wrote:
> 	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@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

Re: working with nano

[Linux for blind general discussion]

Yes I was introduced to pilot, a good file management program.  I still use
it in the terminal.

When an update to a mac port of alpine is available pilot still is included
in the package for alpine.

Btw, the most recent version for nano is 2.8.4 in a mac port.
On Sat, 17 Jun 2017, Linux for blind general discussion wrote:

> Were you also introduced to pilot another one of alpine's extras as
> well?  If anyone used dos earlier in their lives and liked nswp you'll
> also like pilot.
>
> On Sat, 17 Jun 2017, Linux for blind general discussion wrote:
>
>> Date: Sat, 17 Jun 2017 09:28:22
>> From: Linux for blind general discussion <blinux-list@redhat.com>
>> To: Linux for blind general discussion <blinux-list@redhat.com>
>> Subject: Re: working with nano
>>
>> I was introduced to nano by pico the default editor with the alpine mail
>> client loaded when composing or replying to mail.  It was part of the
>> alpine package and could be used indenpendently as a text editor.
>>
>> Nano is a much improved pico and can be substituted for use in alpine.
>>
>> In the '90's I used dial up to a shell acount to use alpine and used pico and
>> later nano as my text editor.
>>
>> Currently I use both in the terminal of a mac.
>>
>> The key to making best use of nano is to configure the features one wants in
>> the nanorc file.  This includes key mapping for each option with ctrl+letter.
>>
>> The port for the mac comes with a text nanorc.sample file which notates all
>> the options.
>>
>> If this is not available in other distributions I would be happy to send it
>> as an attachment.
>>
>> On Fri, 16 Jun 2017, Linux for blind general discussion wrote:
>>
>>> Yes, this thread is interesting.  I think I'll try some of what people
>>> have suggested.  I've tried nano a few times, but I clearly didn't find
>>> all the places where I could learn to make it do more of what I wanted.
>>>
>>> In 1979, the only thing I knew about computers was that I didn't have
>>> one.  I was in school for another line of work.  My serious time on
>>> computers began in the spring of 1989, and I got at least half-seriously
>>> into Linux in around 2005.  At that time, such editing as I did was
>>> using emacs, but mostly I've used vim.
>>>
>>> Anyway, I appreciate the info on this thread.
>>>
>>> Al
>>>
>>> On 06/16/2017 11:24 AM, Linux for blind general discussion wrote:
>>>> 	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@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>
>> XB
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> -- 
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

XB

Re: working with nano

[Linux for blind general discussion]

Were you also introduced to pilot another one of alpine's extras as 
well?  If anyone used dos earlier in their lives and liked nswp you'll 
also like pilot.

On Sat, 17 Jun 2017, Linux for blind general discussion wrote:

> Date: Sat, 17 Jun 2017 09:28:22
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: Linux for blind general discussion <blinux-list@redhat.com>
> Subject: Re: working with nano
> 
> I was introduced to nano by pico the default editor with the alpine mail
> client loaded when composing or replying to mail.  It was part of the
> alpine package and could be used indenpendently as a text editor.
>
> Nano is a much improved pico and can be substituted for use in alpine.
>
> In the '90's I used dial up to a shell acount to use alpine and used pico and 
> later nano as my text editor.
>
> Currently I use both in the terminal of a mac.
>
> The key to making best use of nano is to configure the features one wants in 
> the nanorc file.  This includes key mapping for each option with ctrl+letter.
>
> The port for the mac comes with a text nanorc.sample file which notates all
> the options.
>
> If this is not available in other distributions I would be happy to send it 
> as an attachment.
>
> On Fri, 16 Jun 2017, Linux for blind general discussion wrote:
>
>> Yes, this thread is interesting.  I think I'll try some of what people
>> have suggested.  I've tried nano a few times, but I clearly didn't find
>> all the places where I could learn to make it do more of what I wanted.
>> 
>> In 1979, the only thing I knew about computers was that I didn't have
>> one.  I was in school for another line of work.  My serious time on
>> computers began in the spring of 1989, and I got at least half-seriously
>> into Linux in around 2005.  At that time, such editing as I did was
>> using emacs, but mostly I've used vim.
>> 
>> Anyway, I appreciate the info on this thread.
>> 
>> Al
>> 
>> On 06/16/2017 11:24 AM, Linux for blind general discussion wrote:
>>> 	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@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>> 
>> 
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>> 
>
> XB
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

-- 

Re: working with nano

[Linux for blind general discussion]

I was introduced to nano by pico the default editor with the alpine mail
client loaded when composing or replying to mail.  It was part of the
alpine package and could be used indenpendently as a text editor.

Nano is a much improved pico and can be substituted for use in alpine.

In the '90's I used dial up to a shell acount to use alpine and used pico 
and later nano as my text editor.

Currently I use both in the terminal of a mac.

The key to making best use of nano is to configure the features one wants 
in the nanorc file.  This includes key mapping for each option with 
ctrl+letter.

The port for the mac comes with a text nanorc.sample file which notates all
the options.

If this is not available in other distributions I would be happy to send it 
as an attachment.

On Fri, 16 Jun 2017, Linux for blind general discussion wrote:

> Yes, this thread is interesting.  I think I'll try some of what people
> have suggested.  I've tried nano a few times, but I clearly didn't find
> all the places where I could learn to make it do more of what I wanted.
>
> In 1979, the only thing I knew about computers was that I didn't have
> one.  I was in school for another line of work.  My serious time on
> computers began in the spring of 1989, and I got at least half-seriously
> into Linux in around 2005.  At that time, such editing as I did was
> using emacs, but mostly I've used vim.
>
> Anyway, I appreciate the info on this thread.
>
> Al
>
> On 06/16/2017 11:24 AM, Linux for blind general discussion wrote:
>> 	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@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

XB

re: working with nano

[Linux for blind general discussion]

also comment out line 15 where it says references mouse and comment out 
line 25 where it references show cursor.


--

Re: working with nano

[Linux for blind general discussion]

Tim here.  Depending on the behavior you want, use one of the
following in your ~/.nanorc file.

If you want soft-wrapping where long lines display as wrapped but the
lines remain as individually long lines in the saved file, add

  set softwrap

If you want hard-wrapping where it will automatically insert
line-breaks when you exceed the maximum line-length, you can

  unset nowrap

(I find that double-negative is a bit weird).  If it's doing that and
you *don't* want it to wrap, you can add

  set nowrap

to your file.

Additionally, you can also specify where you want it to wrap, either
at a particular offset such as 75 characters per line:

  set fill 75

or at an offset from your right-margin based on your screen-size,
such as

  set fill -5

(the two commands should produce the same results on a standard
80-column terminal)

You should be able to read more about each of these options in

  man nanorc

Hope this helps,

-tim
(for whom this is all a bit foreign since I'm a vi/vim/ed sorta guy
and only keep nano around for testing things just like this)




On June 14, 2017, Linux for blind general discussion wrote:
> Hi folks, Mark peveto here.
> Normally, seems I'd set this in my nanorc, but I can't find it.
> What i'm trying to do is make sure long line wrapping is on by
> default, so I don't hafta remember to hit alt l every time I start
> nano. There's a way to do it, but I dunno wha tit is. Can anyone
> help me out?
> 
> 
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

re: working with nano

[Linux for blind general discussion]

Hi, Mark Peveto here,
I tried to use that nanorc file, but nano threw a fit.  No real reason why it should've, because I cut and pasted directly from the email.
Thanks for the shot, though.



Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!

On Wed, 14 Jun 2017, Linux for blind general discussion wrote:

> Hi Mark, below find my .nanorc file.
> cut here.
> set autoindent
> set backup
> set backupdir "/home/jude/nano"
> set backwards
> set matchbrackets "(<[{)>]}"
> set brackets ""')>]}"
> unset casesensitive
> set cut
> set fill -8
> set historylog
> set justifytrim
> set linenumbers
> set locking
> set morespace
> unset mouse
> unset multibuffer
> unset noconvert
> unset nohelp
> unset nonewlines
> unset nowrap
> set positionlog
> set punct "(<[{)>]}"
> unset quickblank
> set regexp
> set showcursor
> set smarthome
> set softwrap
> set speller aspell
> set suspend
> set tabsize 4
> set tempfile
> set unix
> set wordbounds
>
> --
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

re: working with nano

[Linux for blind general discussion]

Hi Mark, below find my .nanorc file.
cut here.
set autoindent
set backup
set backupdir "/home/jude/nano"
set backwards
set matchbrackets "(<[{)>]}"
set brackets ""')>]}"
unset casesensitive
set cut
set fill -8
set historylog
set justifytrim
set linenumbers
set locking
set morespace
unset mouse
unset multibuffer
unset noconvert
unset nohelp
unset nonewlines
unset nowrap
set positionlog
set punct "(<[{)>]}"
unset quickblank
set regexp
set showcursor
set smarthome
set softwrap
set speller aspell
set suspend
set tabsize 4
set tempfile
set unix
set wordbounds

-- 

working with nano

[Linux for blind general discussion]

Hi folks, Mark peveto here.
Normally, seems I'd set this in my nanorc, but I can't find it.  What i'm trying to do is make sure long line wrapping is on by default, so I don't
hafta remember to hit alt l every time I start nano.
There's a way to do it, but I dunno wha tit is.
Can anyone help me out?


Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!