Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211711
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: buster, ekiga. |
| Date | 2019-07-24 23:00 +0200 |
| Message-ID | <ynwwF-6Tf-3@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <ynqAW-35l-3@gated-at.bofh.it> <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> |
| Organization | linux.* mail to news gateway |
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. > > In the same way, I expect mutt and its pager to behave much the > likewise. The only debate would be how/whether to display the NUL > itself. It could just ignore it entirely, as if it wasn't there, or > it could escape it in various ways. Having no indication of the > *existence* of the characters following the NUL is suboptimal in > my book. > > Where is the definition of NUL as "ignore everything following this > character"? AFAICT the mutt manual says nothing about NUL at all. If you feel strongly about this issue, then you probably need to take it up with the mutt maintainers, on their mailing list or however they track bugs and problems. I don't want to speak for the Debian developers here, but this seems like the kind of bug report that would just get forwarded upstream anyway.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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