unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 20:15:58 -0400	[thread overview]
Message-ID: <87o91qyj41.fsf@gmail.com> (raw)
In-Reply-To: <83d0i7y3tm.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Jul 2019 14:33:57 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I don't understand why limit, if we assume that no program will write
> UTF-8 encoded sequences byte-byte.  What am I missing?

I wasn't assuming that, I was wondering whether it was true or not.

> In general, I'd prefer the simplest fix, as this is going to be pushed
> to the release branch, yes?

I wasn't sure about pushing to the release branch either, but yes, I
think my first patch is safer for the release branch (since it only
affects cases where we are currently signaling an error).

Gemini, could you try it and confirm that it fixes your problem please?






  reply	other threads:[~2019-07-19  0:15 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
2019-07-19  0:15               ` Noam Postavsky [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o91qyj41.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=29918@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gazally@runbox.com \
    --cc=larsi@gnus.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).