public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
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: Wed, 14 Jun 2017 14:49:06 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1.1706141447410.3169@southernprince> (raw)
In-Reply-To: <alpine.NEB.2.20.1706141539340.13849@panix1.panix.com>

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
>

  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 [this message]
  -- 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
     ` 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
               ` 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.DEB.2.21.1.1706141447410.3169@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).