From: Robert Park <robru@gottengeography.ca>
To: Chong Yidong <cyd@gnu.org>
Cc: 12398@debbugs.gnu.org
Subject: bug#12398: 23.4; Disabling fringes causes term to garble certain text output.
Date: Sat, 13 Oct 2012 13:15:44 -0500 [thread overview]
Message-ID: <CAL3PwKxzgv=+JBpSRbks-29POg0pBKiu_ZR_5JRG7D7gUEDvBA@mail.gmail.com> (raw)
In-Reply-To: <87a9vqrbkt.fsf@gnu.org>
On Sat, Oct 13, 2012 at 4:00 AM, Chong Yidong <cyd@gnu.org> wrote:
> Thanks for the bug report. This bug has been fixed in Emacs 24.
Was it only *just* fixed? Because I can still reproduce it in Emacs 24.1.1.
1. eval this elisp:
(set-fringe-mode (cons 0 0))
2. Run any command that outputs long lines in term-mode:
$ echo `seq 100`
Expected output:
robru ~
$ echo `seq 100`
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27 28 29 30 31 32
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55
56 57 58 59 60 61
62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84
85 86 87 88 89 90
91 92 93 94 95 96 97 98 99 100
Actual output:
$ bru ~4 95 96 97 98 99 100 72 73 74 75 76 77 78 79 80 81 82 83 84 85
86 87 88 89 90 91
Note that I have a two-line $PS1 set, and the output appears to be the
second line of my prompt ('$ ') laid over the first line of my prompt
('robru ~') laid over the third line of the output (the numbers).
Further, once this condition is triggered, *all* further output
regardless of line length just overwrites this same one line, until
C-l is typed, then everything goes back to normal (at least until
another long line is printed).
The workaround is to enable the fringe on just one side:
(set-fringe-mode (cons 0 1))
And then everything works fine.
--
http://gottengeography.ca
next prev parent reply other threads:[~2012-10-13 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 22:35 bug#12398: 23.4; Disabling fringes causes term to garble certain text output Robert Park
2012-10-13 9:00 ` Chong Yidong
2012-10-13 18:15 ` Robert Park [this message]
2012-10-18 17:14 ` Chong Yidong
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='CAL3PwKxzgv=+JBpSRbks-29POg0pBKiu_ZR_5JRG7D7gUEDvBA@mail.gmail.com' \
--to=robru@gottengeography.ca \
--cc=12398@debbugs.gnu.org \
--cc=cyd@gnu.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).