From: Ryan Johnson <ryanjohn@ece.cmu.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7117@debbugs.gnu.org
Subject: bug#7117: 23.2.2 mangles terminal escape sequences
Date: Tue, 28 Sep 2010 06:53:46 +0200 [thread overview]
Message-ID: <4CA174DA.701@ece.cmu.edu> (raw)
In-Reply-To: <jwv4odaykp4.fsf-monnier+emacs@gnu.org>
On 9/27/2010 10:52 PM, Stefan Monnier wrote:
>> Steps to reproduce:
>> 1. ssh to a machine with emacs-23 installed (I suspect slower
>> networks would expose this more, but the bug bites me even over
>> intranet)
>> 2. compile tee-input.c (see below) into a shared library (on solaris:
>> `cc -g -G -xcode=pic13 -ldl -hlibtee-input.so tee-input.c -g -o
>> libtee-input.so')
>> 3. invoke `LD_PRELOAD=libtee-input.so emacs -nw -Q 2>input.txt'
>> 4. M-x xterm-mouse-mode
>> 5. flick the mouse scroll wheel hard, so it generates many ticks in
>> quick succession (note the garbage that results)
>> 6. M-x show-lossage (note the mangled escape sequences)
>> 7. C-x C-c
>> 8. Examine input.txt (note the intact escape sequences)
> Does (set-keyboard-coding-system 'binary) circumvent the problem?
No. In fact, the solaris machine which I ran the example on defaults to
`no-conversion' (an alias of binary iirc) for some reason. Sorry, I
forgot to mention before.
This matches my expectations, since bug #6920 arises before any coding
system touches the input.
Ryan
next prev parent reply other threads:[~2010-09-28 4:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 12:10 bug#7117: 23.2.2 mangles terminal escape sequences Ryan Johnson
2010-09-27 20:52 ` Stefan Monnier
2010-09-28 4:53 ` Ryan Johnson [this message]
2010-09-30 11:37 ` Ryan Johnson
2010-09-30 14:39 ` Ryan Johnson
2010-09-30 14:59 ` Eli Zaretskii
2010-09-30 15:14 ` Ryan Johnson
2010-09-30 15:44 ` Eli Zaretskii
2010-09-30 16:11 ` Ryan Johnson
2022-02-07 0:33 ` Lars Ingebrigtsen
2022-03-07 2:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CA174DA.701@ece.cmu.edu \
--to=ryanjohn@ece.cmu.edu \
--cc=7117@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.