From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: editing a file in /sys/accessibility/speakup/i18n
Date: Wed, 14 Jun 2017 10:15:09 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1706141014140.3019@southernprince> (raw)
In-Reply-To: <Pine.LNX.4.64.1706140743240.16124@server2.shellworld.net>
Mark Peveto here,
What I ended up having to do is disable the backup file option in the nanorc file. wasn't my favorite choice, but it did solve the problem!
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> Well Mark, while I really don't know why that is not working for you, I can
> say, I usually run
> nano -tzk
> so it doesn't prompt. Also, what happens if you became root as
> su -m
> Chime
>
> _______________________________________________
> 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: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` 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.DEB.2.21.1.1706141014140.3019@southernprince \
--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).