GNU bug report logs - #51877
27.2; term: error in process filter

Previous Next

Package: emacs;

Reported by: Christopher Howard <christopher <at> librehacker.com>

Date: Mon, 15 Nov 2021 19:11:02 UTC

Severity: normal

Tags: moreinfo

Found in version 27.2

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Christopher Howard <christopher <at> librehacker.com>
Cc: larsi <at> gnus.org, 51877 <at> debbugs.gnu.org
Subject: bug#51877: 27.2; term: error in process filter
Date: Thu, 20 Jan 2022 19:54:46 +0200
> Date: Thu, 20 Jan 2022 08:39:47 -0900
> From: Christopher Howard <christopher <at> librehacker.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 51877 <at> debbugs.gnu.org
> 
> The package emacs-next-28.0.50-0.2ea3466 is available in my current checkout of Guix. I seem to get the same results:
> 
> ```
> Debugger entered--Lisp error: (args-out-of-range "$ \2\220\22\33nN\4\216" 0 -42)
>   term-emulate-terminal(#<process terminal> "l\0l\234\236|\0\214l\340|\2\f\f\f\204\4l\354\4#|\216\203\3\344\22\262\337|\33b\204\fb\214\362oo\337lNo\234\343\344\f#\34p...")
> ```
> 
> Is that new enough?

No, that is from 1.5 years ago.

Can you tell how you set the encoding to raw-text?  I see that the
process filter function which barfs use locale-coding-system to decode
the process output -- did you change that to use 'raw-text' by
modifying the code of term.el?  If not, what did you do?




This bug report was last modified 3 years and 184 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.