[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17497: 24.4.50; TTY menu glitches
From: |
Stefan Monnier |
Subject: |
bug#17497: 24.4.50; TTY menu glitches |
Date: |
Thu, 05 Jun 2014 09:44:45 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
> You could cut the discussion short by making the check that I suggested:
> logging the decoded character/special-key values to look for instances
> where the decoding returns individual bytes.
No we cut it short by noticing that Emacs's internal state is the one we
expect and the display is completely wrong, which is something that
cannot happen due to some weird input sequence.
Please believe us, we *really* know that the problem is not in Emacs's
misunderstanding/misdecoding of the input stream (yes, it does have
bugs there, of course, but they're unrelated).
To repeat: replaying the termscript results in a different display (not
only that, it results in the display we want)!
This can't be due to Emacs's input processing.
Stefan
- bug#17497: 24.4.50; TTY menu glitches, (continued)
- bug#17497: 24.4.50; TTY menu glitches, Stefan Monnier, 2014/06/04
- bug#17497: 24.4.50; TTY menu glitches, Thomas Dickey, 2014/06/04
- bug#17497: 24.4.50; TTY menu glitches, Stefan Monnier, 2014/06/04
- bug#17497: 24.4.50; TTY menu glitches, Thomas Dickey, 2014/06/05
- bug#17497: 24.4.50; TTY menu glitches, Andreas Schwab, 2014/06/05
- bug#17497: 24.4.50; TTY menu glitches, Eli Zaretskii, 2014/06/05
- bug#17497: 24.4.50; TTY menu glitches,
Stefan Monnier <=
- bug#17497: 24.4.50; TTY menu glitches, Stefan Monnier, 2014/06/05
- bug#17497: 24.4.50; TTY menu glitches, Eli Zaretskii, 2014/06/05
- bug#17497: 24.4.50; TTY menu glitches, Eli Zaretskii, 2014/06/01