Re: buster, ekiga.

From	Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups	linux.debian.user
Subject	Re: buster, ekiga.
Date	2019-07-24 23:20 +0200
Message-ID	<ynwQ1-7hl-3@gated-at.bofh.it> (permalink)
References	(4 earlier) <ynt5L-4Pg-1@gated-at.bofh.it> <yntfr-4Uj-5@gated-at.bofh.it> <yntIu-55k-5@gated-at.bofh.it> <ynwwG-6Tf-5@gated-at.bofh.it> <ynwGl-7cF-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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.

Thread

Re: buster, ekiga. peter@easthope.ca - 2019-07-23 17:00 +0200
  Re: buster, ekiga. Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-23 17:10 +0200
    Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-23 18:40 +0200
    Odd character, was Re: buster, ekiga. David Wright <deblis@lionunicorn.co.uk> - 2019-07-23 21:20 +0200
      Re: Odd character, was Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-23 21:30 +0200
      Re: Odd character, was Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-23 21:40 +0200
        Re: Odd character, was Re: buster, ekiga. Michael Stone <mstone@debian.org> - 2019-07-23 23:00 +0200
      Re: Odd character, was Re: buster, ekiga. Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-23 21:40 +0200
        Re: Odd character, was Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-23 22:10 +0200
      Re: Odd character, was Re: buster, ekiga. Michael Stone <mstone@debian.org> - 2019-07-23 21:40 +0200
        Re: Odd character, was Re: buster, ekiga. David Wright <deblis@lionunicorn.co.uk> - 2019-07-25 18:40 +0200
    Re: buster, ekiga. rhkramer@gmail.com - 2019-07-24 13:20 +0200
      Re: buster, ekiga. David Wright <deblis@lionunicorn.co.uk> - 2019-07-24 16:40 +0200
        Re: buster, ekiga. Michael Stone <mstone@debian.org> - 2019-07-24 19:20 +0200
          Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-24 19:30 +0200
            Re: buster, ekiga. Michael Stone <mstone@debian.org> - 2019-07-24 20:00 +0200
              Re: buster, ekiga. Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-24 23:00 +0200
              Re: buster, ekiga. Sven Joachim <svenjoac@gmx.de> - 2019-07-24 23:00 +0200
                Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-24 23:10 +0200
              Re: buster, ekiga. David Wright <deblis@lionunicorn.co.uk> - 2019-07-24 23:00 +0200
                Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-24 23:10 +0200
                Re: buster, ekiga. Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-24 23:20 +0200
                Re: buster, ekiga. <tomas@tuxteam.de> - 2019-07-24 23:30 +0200
                Re: buster, ekiga. David Wright <deblis@lionunicorn.co.uk> - 2019-07-25 18:40 +0200
                Re: buster, ekiga. Michael Stone <mstone@debian.org> - 2019-07-25 13:40 +0200
  Re: buster, ekiga. Brad Rogers <brad@fineby.me.uk> - 2019-07-23 17:30 +0200

csiph-web