Re: buster, ekiga.

[David Wright <deblis@lionunicorn.co.uk>]

On Wed 24 Jul 2019 at 17:12:39 (-0400), Greg Wooledge wrote:
> On Wed, Jul 24, 2019 at 11:02:33PM +0200, tomas@tuxteam.de wrote:
> > On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
> > 
> > [...]
> > 
> > > If I read a file that has an embedded NUL into an editor, I would
> > > consider it suboptimal if the editor ceased reading any more of the
> > > file when it hit a NUL.
> > 
> > Vim and Emacs both qualify. Are there other editors? (yes, a bit
> > tongue-in-cheek ;-P
> 
> I was curious, so I generated a "text" file with a NUL in it, and opened
> it in nano.  To my surprise, nano actually handled it extremely well.
> The NUL was rendered as the two characters ^@ in the terminal, and
> the cursor only "rested" on one of the two characters when moving
> left-to-right across that line.  Ctrl-D (with the cursor on one of the ^@
> characters) removed both characters from the terminal display, and after
> saving, the NUL byte was gone from the file.
> 
> It was basically identical to how vim handles it, just with different
> key bindings.

Yes, it's a good editor, and it's the only one I use as root. However,
it does have its failings with some characters, generally in the more
distant parts of the character code chart.

For example, you can't see anything special about NO-BREAK SPACE 0xa0,
whereas emacs marks it in various ways (cyan underscore when windowed,
purple block when non-windowed). And its behaviour with SOFT HYPHEN 0xad
is really odd, particularly when at the beginning of a line. (Soft
hyphens are coloured cyan in emacs. These colours may depend on themes
and suchlike in DEs.)

Cheers,
David.