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
Date: Thu, 15 Jun 2017 08:50:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1706150848240.20545@panix1.panix.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1706142107150.2697@southernprince>
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
>
--
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 [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
` 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
-- 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=alpine.NEB.2.20.1706150848240.20545@panix1.panix.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).