public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Paul Maier" <svn-user@web.de>
To: <cygwin-xfree@cygwin.com>
Cc: <dickey@his.com>
Subject: "xterm -si" doesn't hold the line
Date: Sat, 28 Jul 2012 12:51:00 -0000	[thread overview]
Message-ID: <000001cd6cbf$6a0c8090$3e2581b0$@de> (raw)

Hi,

xterm -si doesn't work as expected.

To reproduce (think of a "tail -f" instead of xev):

1. xterm -si -e /bin/xev
2. move the mouse in the xev window to produce some lines
3. scroll the xterm up half way and remember the visible lines
4. while looking at the xterm, again move the mouse in the xev window

You see: xterm scrolls slowly down.

I would expect xterm to hold the current view while xev produces more lines at the end.


Suppose you have a "tail -f" running and scroll the xterm up to view a specific line.
I would expect that line to stay visible until I scroll somewhere else.
But it's not: as the "tail -f" produces output, the xterm scrolls slowly down.
To clarify: xterm does not scroll down to the very end but it scrolls down line by line,
as if xterm would try to keep the same distance between the current scrolling position and the most recent line.

I would expect xterm to keep the same distance between the current scrolling position and the *FIRST* line.


In case above behaviour is the desired behaviour, I wanted to suggest another command line option like "-si-top"
for my use case.

Regards,
  Paul



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


             reply	other threads:[~2012-07-28 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28 12:51 Paul Maier [this message]
2012-07-28 15:57 ` 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:
  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='000001cd6cbf$6a0c8090$3e2581b0$@de' \
    --to=svn-user@web.de \
    --cc=cygwin-xfree@cygwin.com \
    --cc=dickey@his.com \
    /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.
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).