Nano 2.4.0 problem

Jude DaShiell jdashiel at
Sun Jun 7 15:25:10 UTC 2015

No I haven't, and as a result of work done with accessibility I learned 
and know about interface latency problems.  I don't use nano or pico 
which is nano's parent but do use emacs and ex which is a command line 
version of vim.  You might try starting nano up with -s it may make life 
possible for you.

On Sat, 6 Jun 2015, Christopher Chaltain wrote:

> Date: Sat, 6 Jun 2015 16:04:25
> From: Christopher Chaltain <chaltain at>
> Reply-To: Linux for blind general discussion <blinux-list at>
> To: Linux for blind general discussion <blinux-list at>
> Subject: Re: Nano 2.4.0 problem
> I'm curious, have you designed and written an editor yourself? If so, could 
> you let me know how to get my hands on it? It might be a good alternative to 
> the editors I'm currently using.
> On 06/06/2015 02:43 PM, Jude DaShiell wrote:
>> Talk about inefficient and brain dead design!
>> On Sun, 26 Apr 2015, Kyle wrote:
>>> Date: Sun, 26 Apr 2015 09:06:16
>>> From: Kyle <kyle4jesus at>
>>> Reply-To: Linux for blind general discussion <blinux-list at>
>>> To: blinux-list at
>>> Subject: Re: Nano 2.4.0 problem
>>> So far, the only thing I know works flawlessly with the new version of
>>> Nano is Orca+gnome-terminal, and possibly mate-terminal as well. My best
>>> guess is that Nano is redrawing the screen on each character in a text
>>> console, which would cause the problem, although using it over ssh seems
>>> to work just as well in gnome-terminal as running it locally. Many of us
>>> are seeing it, but none of us have yet found the setting in question.
>>> Since I use Orca pretty much exclusively for everyday use, I don't
>>> notice it here, and nano in fact works better than Vim, as Vim has a
>>> funny habit of repeating words in gnome-terminal, both running locally
>>> and over ssh. Getting information from the TalkingArch community
>>> certainly helps here, as we use Nano a lot in the text console when
>>> installing the system, and have largely had to get used to Vim commands
>>> recently, although Vim has been my editor of choice, with the exception
>>> of the autio tutorial I made, in which I made extensive use of Nano, as
>>> it is installed by default on the live image. Rest assured that I will
>>> share whatever makes Nano work properly again as soon as someone in
>>> #talkingarch finds it, or I stumble upon it somewhere else, whichever
>>> comes first.
>>> Sent from my bouncing rubber ball


More information about the Blinux-list mailing list