public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sloppy sterm screen update over ssh
Date: Wed, 2 Oct 2013 19:06:51 -0400	[thread overview]
Message-ID: <20131002230651.GA29368@waltdnes.org> (raw)
In-Reply-To: <CAEH5T2O5ek+BC1c0yY-CirZ4LoA9BQKjkXYJJFOdwJ3EKqrzHw@mail.gmail.com>

On Wed, Oct 02, 2013 at 11:33:19AM -0500, Paul Hartman wrote
> On Mon, Sep 30, 2013 at 7:10 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> >   I've recently noticed when ssh'ing into another machine that the xterm
> > display doesn't fully update.  I.e. there are "holes" where an app
> > updates over a previous screen.  I've tried Google, but any mention of
> > "screen" is interpreted as the "screen" utility.
> 
> Hi,
> 
> Are you running xterm over ssh (X11 forwarding) or are you running an
> ssh session inside of an xterm? If the latter I have experienced
> something similar when my TERM variable was not set correctly and
> things like Midnight Commander would not fill in the blue background
> (for example) or fail to blank the screen on updates.

  Another Midnight Commander user!  Yes, I fire up an xterm locally, and
then ssh to another machine.  I notice this especially with mc and vim.
Thanks for the pointer.  Now that I know what I should be looking for, a
Google search indicates I should have...

TERM="xterm"

  Is that correct?  It seems to solve my problem.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


  reply	other threads:[~2013-10-02 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01  0:10 [gentoo-user] Sloppy sterm screen update over ssh Walter Dnes
2013-10-02 16:33 ` Paul Hartman
2013-10-02 23:06   ` Walter Dnes [this message]
2013-10-03  7:59     ` Dragostin Yanev

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=20131002230651.GA29368@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox