From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux <blinux-list@redhat.com>
Subject: If you've ever used alpine, then you've probably seen this.
Date: Wed, 14 Jun 2017 14:36:43 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1706141431050.3024@southernprince> (raw)
Hi all,
Mark Peveto here.
I'm working on ironing out a problem in Alpine. If you've ever used it,
then I imagine you've seen the problem I'm about to describe.
Unless I change the editor during my initial setup, the editor that ships
with alpine won't read characters that are backspaced out. Seems someone
told me there's a fix for this, but I'll be darned if I remember what it
is. this problem only happens when using speakup. If i'd choose to use
fenrir, then I'd not have that problem. As far as I know, though, fenrir
isn't working with debian yet, and I'm not sure it'd support my hardware
synths.
Does anyone know the fix for this? Using nano can be problematic, since
it doesn't seem to want to leave the alt l option of long line wrapping on
by default anymore.
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1706141431050.3024@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).