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

Re: [MiNT] Toswin and null-bytes

To: mint@gfanrend.fishpool.fi (MiNT mailing list)
Subject: Re: [MiNT] Toswin and null-bytes
From: Guido Flohr <gufl0000@stud.uni-sb.de>
Date: Sat, 13 Nov 1999 14:09:46 +0100
In-reply-to: <19991108230915.A5834@hrzpub.tu-darmstadt.de>; from Thomas Binder on Mon, Nov 08, 1999 at 11:09:15PM +0100
Mail-followup-to: mint@fishpool.com (MiNT mailing list)
References: <19991102204634.A24@stud> <19991108230915.A5834@hrzpub.tu-darmstadt.de>
Sender: owner-mint@gfanrend.fishpool.fi

Hi,

On Mon, Nov 08, 1999 at 11:09:15PM +0100, Thomas Binder wrote:
> Hi!
> 
> On Tue, Nov 02, 1999 at 08:46:34PM +0100, Guido Flohr wrote:
> > Can this annoying behavior be changed with an stty command? Or is it a bug
> > in Toswin?
> 
> I'd say this is a bug in TosWin, which I assume simply uses v_gtext() to
> print lines, without replacing \0 with e.g. space in the internal buffer
> upon receiving characters.

I think the right behavior would be to simply discard the null-bytes.
That is what the console driver for MiNT and all drivers for other systems
I know of do.

Ciao

Guido
-- 
http://stud.uni-sb.de/~gufl0000/
mailto:gufl0000@stud.uni-sb.de

References:
- [MiNT] Toswin and null-bytes
  - From: Guido Flohr <gufl0000@stud.uni-sb.de>
- Re: [MiNT] Toswin and null-bytes
  - From: Thomas Binder <gryf@hrzpub.tu-darmstadt.de>

Prev by Date: RE: [MiNT] Was: /proc, will be: /sys
Next by Date: Re: [MiNT] Beta kernel 1.15.4 with X11
Previous by thread: Re: [MiNT] Toswin and null-bytes
Next by thread: [MiNT] Beta kernel 1.15.4 with X11
Index(es):
- Date
- Thread