Date: Thu, 14 Feb 2008 08:18:05 +0100 From: Ed Schouten <ed@fxq.nl> To: Marcel Moolenaar <xcllnt@mac.com> Cc: FreeBSD Arch <freebsd-arch@freebsd.org> Subject: Re: Proposal for redesigning the TTY layer Message-ID: <20080214071805.GP1340@hoeg.nl> In-Reply-To: <2672DC03-9293-4A92-969B-074CAB55176B@mac.com> References: <20080213150500.GH1340@hoeg.nl> <A86365DD-5D15-42F2-A810-493B9F9E7AA3@mac.com> <20080213192808.GL1340@hoeg.nl> <2672DC03-9293-4A92-969B-074CAB55176B@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--5xr6Gr0irOxp3+3c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Marcel Moolenaar <xcllnt@mac.com> wrote: > The problem with doing it that way is that insertion of control > characters, like XON/XOFF or STOP may happen right in the middle > of UTF-8 sequences. This may be problematic... This is one of the things that doesn't worry me much, because if the application takes care to write the entire UTF-8 character at once, it will enter the clist in the proper order, except when: - the TTY hits its watermarks during the write - traffic enters the TTY inwards, which has to be echoed (even though this will probably be caught by locking as well), while an UTF-8 character is entering the TTY outwards. --=20 Ed Schouten <ed@fxq.nl> WWW: http://g-rave.nl/ --5xr6Gr0irOxp3+3c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkez6y0ACgkQ52SDGA2eCwW66wCeKVDoNKsDOOO63NjKONqqeY1v kuUAnRq1yJpWRBV4VisntIOzWsZpcgRE =zONr -----END PGP SIGNATURE----- --5xr6Gr0irOxp3+3c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080214071805.GP1340>