public inbox for
help / color / mirror / Atom feed
From: Jim Reisert AD1C <>
Subject: Strange xterm scrolling problem introduced in XTerm(289)
Date: Tue, 12 Feb 2013 21:54:00 -0000	[thread overview]
Message-ID: <> (raw)

A strange scrolling problem seems to have been introduced in XTerm(289)

I have a large scrollback buffer.  Now when I scroll back my xterm,
anything that was previously "above" the top of the current screen
appears indented about 20 spaces:

                                                - r w x - - - - - - +
 1   r e i s e r t   D o m a i n   U s e rs 424739 Feb 12
                                                - r w x - - - - - - +
 1   r e i s e r t   D o m a i n   U s e rs 424740 Feb 12
-rwx------+ 1 reisert Domain Users 424749 Feb 12 14:43 callsigns.csv.~29~
-rwx------+ 1 reisert Domain Users 424749 Feb 12 14:44 callsigns.csv

Can anyone duplicate this?  Note that when I copied/pasted the above
lines into gmail, the first two lines (in the scrollback buffer)
appeared in a different font than the two lines that were not in the

Jim Reisert AD1C, <>,

Unsubscribe info:
Problem reports:

             reply	other threads:[~2013-02-12 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 21:54 Jim Reisert AD1C [this message]
2013-02-12 23:01 ` Thomas Dickey
2013-02-12 23:22   ` Jim Reisert AD1C
2013-02-12 23:51     ` Thomas Dickey
2013-02-13  0:41       ` Thomas Dickey

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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.
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).