unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christopher Howard <christopher@librehacker.com>
Cc: 51877@debbugs.gnu.org
Subject: bug#51877: 27.2; term: error in process filter
Date: Mon, 15 Nov 2021 21:19:54 +0200	[thread overview]
Message-ID: <835yst2plx.fsf@gnu.org> (raw)
In-Reply-To: <263fffec7d58e1851940ace4655fe5b913248b2a.camel@librehacker.com> (message from Christopher Howard on Mon, 15 Nov 2021 10:10:38 -0900)

> From: Christopher Howard <christopher@librehacker.com>
> Date: Mon, 15 Nov 2021 10:10:38 -0900
> 
> Conditions: Computer with a /dev/ttyUSB0 character source which
> generates
> garbage output characters in the form of a long list of \371 bytes. In
> my case, was connected via sterm to an ESP8266 microcontroller.
> 
> 1) M-x term (leave it in char mode)
> 2) sterm -n /dev/ttyUSB0 -s 115200
> 3) cause the garbage output to be generated
> 4) while the cursor is still at the end of the garbage line, try to
> type
> in a normal character.
> 
> The character will get sent to sterm, but the echoed back character
> will
> not appear in the emacs terminal, and an error will appear containing
> the character (see below).
> 
> Pressing enter to begin a new line will clear the error.
> 
> Perhaps this error could be duplicated by those not having my
> microcontroller setup, but filling a file with some \371 or other
> garbage characters, and cat'ing that file into the emacs terminal. The
> issue is that garbage characters somehow confuses the process filter,
> whatever that is.

What is the value of process-coding-system in this case?  If a process
generates binary garbage, its output should be decoded as raw-text,
whereas the Emacs defaults are set for a program which sends
human-readable text.  So Emacs tries to decode your garbage as if it
were UTF-8, and chokes.

IOW, I think this is a cockpit error.





  parent reply	other threads:[~2021-11-15 19:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 19:10 bug#51877: 27.2; term: error in process filter Christopher Howard
2021-11-15 19:14 ` Christopher Howard
2021-11-15 19:19 ` Eli Zaretskii [this message]
2021-11-15 19:33   ` Christopher Howard
2021-11-15 22:36   ` Christopher Howard
2021-11-16  3:23     ` Eli Zaretskii
2022-01-15 13:12       ` Lars Ingebrigtsen
2022-01-16  6:14         ` Christopher Howard
2022-01-17 19:30         ` Christopher Howard
2022-01-20  9:39           ` Lars Ingebrigtsen
2022-01-20 17:39             ` Christopher Howard
2022-01-20 17:46               ` Lars Ingebrigtsen
2022-01-20 17:54               ` Eli Zaretskii
2022-01-20 19:06                 ` Christopher Howard
2022-01-20 20:02                   ` Eli Zaretskii
2022-01-20 22:01                     ` Christopher Howard
2022-01-21  8:04                       ` Eli Zaretskii
2022-02-19 12:58                         ` Lars Ingebrigtsen

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=835yst2plx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51877@debbugs.gnu.org \
    --cc=christopher@librehacker.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 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).