From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 29918@debbugs.gnu.org, gazally@runbox.com, larsi@gnus.org
Subject: bug#29918: 26.0.90; serial-term error in process filter
Date: Thu, 18 Jul 2019 14:33:57 +0300 [thread overview]
Message-ID: <83d0i7y3tm.fsf@gnu.org> (raw)
In-Reply-To: <874l3jzixp.fsf@gmail.com> (message from Noam Postavsky on Thu, 18 Jul 2019 07:22:10 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: 29918@debbugs.gnu.org, gazally@runbox.com, larsi@gnus.org
> Date: Thu, 18 Jul 2019 07:22:10 -0400
>
> >> there is a possibility it prevents correct decoding in case the
> >> terminal receives a utf-8 character in single byte chunks (though
> >> I'm not sure if it's even valid for a program to emit single bytes
> >> like that).
> >
> > I agree.
>
> I thought of limiting partial to 4, to avoid this possibility, since
> utf-8 characters can be 4 bytes at most (not sure about other encodings
> though).
I don't understand why limit, if we assume that no program will write
UTF-8 encoded sequences byte-byte. What am I missing?
In general, I'd prefer the simplest fix, as this is going to be pushed
to the release branch, yes?
next prev parent reply other threads:[~2019-07-18 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 20:57 bug#29918: 26.0.90; serial-term error in process filter Gemini Lasswell
2019-07-14 17:52 ` Lars Ingebrigtsen
2019-07-15 21:45 ` Gemini Lasswell
2019-07-17 10:58 ` Lars Ingebrigtsen
2019-07-17 11:36 ` Noam Postavsky
2019-07-18 8:45 ` Eli Zaretskii
2019-07-18 11:22 ` Noam Postavsky
2019-07-18 11:33 ` Eli Zaretskii [this message]
2019-07-19 0:15 ` Noam Postavsky
2019-07-20 12:49 ` Gemini Lasswell
2019-07-21 2:32 ` Noam Postavsky
2019-07-21 13:49 ` Stefan Monnier
2019-07-21 14:38 ` Eli Zaretskii
2019-07-21 14:45 ` Lars Ingebrigtsen
2019-07-21 14:47 ` Eli Zaretskii
2019-07-21 13:52 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d0i7y3tm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29918@debbugs.gnu.org \
--cc=gazally@runbox.com \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.