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

[Antonio Diaz Diaz]

Benno Schulenberg wrote:
> 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.

This is in fact an unfortunate situation, but I have the hope that 
lzma-alone and xz will be eventually abandoned in favor of lzip.


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

Yes. Moe edits them almost as if they were just a single file. Searching 
and replacing globally, and moving freely from one file to any other is 
the only way to make sure that a complex patch for a large project is 
reasonably complete.


> > 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?

Are you using moe on an utf-8 terminal? You need to select some ISO-8859 
variant for moe to work, specially when editing a binary file that does 
not contain valid utf-8 data.


> > $ busybox xz -cd fox.xz
> > The quick brown fox jumps over the lazy fog.
>
> So busybox has a bug.  Surely that can be fixed?

Well, this is not a bug in a strict sense. This behavior is allowed by 
the xz format specification.

The problem is that xz files must be created for a given purpose. For 
example, the xz man page states that "you  must  use --check=none or 
--check=crc32 when creating files for embedded systems".

Of course, nobody follows the advice and they create xz files using the 
default settings. The result is that for xz-embedded (busybox) users, xz 
is unsafer than lzma-alone or the old compress.


> > 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.

But moe is not their editor. It is My Own Editor. ;-)

Really, I am not interested in increasing the number of users of moe. I 
am interested in making it as useful as possible for my own use (and for 
those that use it as I do). An editor is a very personal tool.


> > 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.

Backwards compatibility is important. This is why I need to investigate 
this further.


> > 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.

Thanks. I'll download the latest version and try. My current version of 
nano is 2.0.6.


Best regards,
Antonio.