[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-moe] keycodes are entered into buffer

From: Benno Schulenberg
Subject: Re: [Bug-moe] keycodes are entered into buffer
Date: Wed, 07 Sep 2016 21:32:09 +0200

On Wed, Sep 7, 2016, at 19:18, Antonio Diaz Diaz wrote:
> Sorry for the inconvenience. I hope that as a xz user, at least it 
> brings something positive to you.

Oh, I am not a "happy" xz user.  I just use it by necessity.  I just
wish there was one format, and not three different ones that are
vaguely or strongly similar and I have to study what the heck is
going on there.

> BTW, I find moe more convenient than nano to edit large projects. For 
> example, just now I am editing 54126 files of linux 4.7 with moe.

Well, it's called "nano" for a reason.  :)  It will do fine for editing
a handful of files of a few hundred lines each, and maybe up to a tenfold
of that, but don't expect it to handle much more.

But do you mean to say you have those fifty thousand files open at
the same time?

> $ echo 'The quick brown fox jumps over the lazy dog.' | xz > fox.xz
> Open fox.xz with an hex editor (moe will do) and modify any character in 
> the sentence above,

Ehm... that is hard.  Just doing 'moe fox.xz' and then moving the
cursor with <Right> to the first letter of lazy and typing h, the
line suddenly changes to read "...the hthe lazy dog."  Huh?

When I use nano, things work fine.  (At least on a Gnome Terminal;
on a Linux console things get misaligned one character.  The second
character after the ^D is a zero-width character, but the console
doesn't seem to know about such things.)

> $ busybox xz -cd fox.xz
> The quick brown fox jumps over the lazy fog.

So busybox has a bug.  Surely that can be fixed?

> The question is that I use moe almost exclusively on a VGA text console, 
> and I would prefer not to add functions that do not work there.

I see.  Understandable.  But... as a developer you would have to
consider where /most/ people use their editor.  Not on Ctrl+Alt+F1
to Ctrl+Alt+F6.  Most people stay forever on Ctrl+Alt+F7.

> Another problem is that ncurses.h (5.6 and 5.9) only provides key codes 
> for Shift+Left and Shift+Right. I need to investigate this further.

Oh, I wouldn't bother any more.  Most people will be on ncurses6.0
by now, and every day more of them.

> > Konsole is another deficient terminal.  I pray for its users that
> > those key combos can be reassigned.
> How curious. Another user said something similar about Gnome Terminal.

Yes, terminal emulators are curious things.  Each of them has
different keys that it swallows and uses for its own purposes.
Some days ago I was on Peppermint, using a terminal that is
called Sakura, apparently, and it were Shift+Ctrl+Left/Right that
moved between Tabs.  I'm used to using Ctrl+PageUp/PageDown
for that, in Firefox, Thunderbird, and in Gnome Terminal -- I
wish it would work everywhere, or at least that there were a
global setting for this.

> It seems that Ctrl+Left/Right only works on a Gnome Terminal, which I do 
> not use nor have installed. Nano does not recognize Ctrl+Left/Right 
> neither on a VGA text console nor on Konsole.

You will have to use a recent nano for that to work.  2.7.0 should do it.



http://www.fastmail.com - Send your email first class

reply via email to

[Prev in Thread] Current Thread [Next in Thread]