screen redraw problems
Kurt Lieber
use Mutt 1.4 with ncurses support (no slang). When ssh'd in to the server,
I consistently have problems with certain messages being displayed
improperly on the screen. Lines are garbled, remnants from other mutt
screens are displayed and its a general mess. This seems to happen most
often with pgp-signed messages. I don't have console access on this
particular server, so I can't say if it only happens over remote
connections.
I can hit ctrl-l to redraw the screen and that always solves the issue.
However, I'm curious if there's something that can be done to solve it on a
more permanent basis. Is this a mutt problem?
--kurt
Bruno Lustosa
--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Kurt Lieber [mu...@kirpatrick.com] wrote:
> I'm not sure if this is a mutt problem or something else, but I currently
> use Mutt 1.4 with ncurses support (no slang). When ssh'd in to the serve=
r,
> I consistently have problems with certain messages being displayed
> improperly on the screen. Lines are garbled, remnants from other mutt
> screens are displayed and its a general mess. This seems to happen most
> often with pgp-signed messages. I don't have console access on this
> particular server, so I can't say if it only happens over remote
> connections.
>=20
> I can hit ctrl-l to redraw the screen and that always solves the issue.
> However, I'm curious if there's something that can be done to solve it on=
a
> more permanent basis. Is this a mutt problem?
Most probably, a terminal problem.
Try to fiddle with your terminal settings (which ssh client do you
use?).
--=20
Bruno Lustosa, aka Lofofora | Email: br...@lustosa.net
Network Administrator/Web Programmer | ICQ UIN: 1406477
Rio de Janeiro - Brazil |
--W/nzBZO5zC0uMSeA
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9wEaRiNfNvfQ8L5IRAmz5AJ9XgO0HL1O9OxuMQm+btHs8MMoWDwCfY8PR
ksgIPmFyjV3Hl4pysLCcu7k=
=JbTY
-----END PGP SIGNATURE-----
--W/nzBZO5zC0uMSeA--
Bob Phan
> On Wed, Oct 30, 2002 at 05:52:33PM -0300 or thereabouts, Bruno Lustosa wrote:
> > Most probably, a terminal problem. Try to fiddle with your terminal
> > settings (which ssh client do you use?).
>
> identical in frequency and symptoms on both clients.
What terminal are they emulating (echo $TERM)? ncurses tries to be
clever depending on the features of the various terms that it supports.
You may have better luck switching to a more capable terminal setting.
I've always had good luck with 'xterm' and 'vt220'.
Also, what OS is the server running?
--
/*
* Bob Phan <b...@endlessrecursion.net,rp...@nrgn.com>
* Computational Chemistry Informatics
* Neurogen Corporation
* (203)488-8201 x4645
*
* To understand recursion, you must first understand recursion.
* http://www.endlessrecursion.net/
*/
Kurt Lieber
> Most probably, a terminal problem.
> Try to fiddle with your terminal settings (which ssh client do you
> use?).
On windows, I use PuTTY and on Linux, I use OpenSSH. The problem is
identical in frequency and symptoms on both clients.
--kurt
Keith R. John Warno
Putty is broken in this respect. I've seen some wild term issues with
it + mutt. However I haven't seen any problems using xterm+openssh+mutt
on a Linux box. Am doing just this at this moment. Which term emulator
are you using on Linux? xterm/rxvt/...? And what is the value of
$TERM? IIRC I had to tweak a few terminfo things to make a few keyboard
problems go away but I've *never* had the screen get garbled up.
Regards,
Keith.
JeeBak Kim
[snip]
> > On windows, I use PuTTY and on Linux, I use OpenSSH. The problem is
> > identical in frequency and symptoms on both clients.
>
> Putty is broken in this respect. I've seen some wild term issues with
> it + mutt. However I haven't seen any problems using xterm+openssh+mutt
> on a Linux box. Am doing just this at this moment. Which term emulator
> are you using on Linux? xterm/rxvt/...? And what is the value of
> $TERM? IIRC I had to tweak a few terminfo things to make a few keyboard
> problems go away but I've *never* had the screen get garbled up.
Mutt works fine with PuTTY (using it right now ;) if you set TERM to
xterm-xfree86 (maybe my previous post hasn't reached the list yet.)
>
> Regards,
> Keith.
Will Yardley
> - On Wed, 30.Oct.2002, 16:10EST, Kurt Lieber uttered:
> > On Wed, Oct 30, 2002 at 05:52:33PM -0300 or thereabouts, Bruno Lustosa wrote:
> > > Most probably, a terminal problem.
> > > Try to fiddle with your terminal settings (which ssh client do you
> > > use?).
> > On windows, I use PuTTY and on Linux, I use OpenSSH. The problem is
> > identical in frequency and symptoms on both clients.
> Putty is broken in this respect. I've seen some wild term issues with
> it + mutt. However I haven't seen any problems using
> xterm+openssh+mutt on a Linux box.
What terminal setting are you using with PuTTY? There is a putty
terminfo definition that works pretty well in my experience.
--
Will Yardley
input: william < @ hq . newdream . net . >
John Buttery
--XWOWbaMNXpFDWE00
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* JeeBak Kim <jb...@cs.pdx.edu> [2002-10-30 16:56:35 -0800]:
> * Keith R. John Warno (kr...@optonline.net) [021030 16:47]:
> [snip]
> > > On windows, I use PuTTY and on Linux, I use OpenSSH. The problem is
> > > identical in frequency and symptoms on both clients.
> >=20
> > Putty is broken in this respect. I've seen some wild term issues with
> > it + mutt. However I haven't seen any problems using xterm+openssh+mutt
> > on a Linux box. Am doing just this at this moment. Which term emulator
> > are you using on Linux? xterm/rxvt/...? And what is the value of
> > $TERM? IIRC I had to tweak a few terminfo things to make a few keyboard
> > problems go away but I've *never* had the screen get garbled up.
>=20
> Mutt works fine with PuTTY (using it right now ;) if you set TERM to
> xterm-xfree86 (maybe my previous post hasn't reached the list yet.)
>=20
> >=20
> > Regards,
> > Keith.
I use TERM=3Dlinux with much success with PuTTY and OpenSSH for Linux
and Cygwin, as well as locally in console and X11.=20
--=20
------------------------------------------------------------------------
John Buttery
(Web page temporarily unavailable)
------------------------------------------------------------------------
--XWOWbaMNXpFDWE00
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9wMzsWH8M1wI2iFcRAvYzAJ9TW3B6akw9HsOpEYML1NeId/seBwCfZWgH
LC4gpx2l3n4wf/XAeFBLbNE=
=+7tI
-----END PGP SIGNATURE-----
--XWOWbaMNXpFDWE00--
Bob Phan
> On Wed, Oct 30, 2002 at 06:00:46PM -0500 or thereabouts, Bob Phan wrote:
> > What terminal are they emulating (echo $TERM)?
>
> > Also, what OS is the server running?
I ssh from a gentoo box at work to another at home using both
multi-gnome-terminal and xfree xterm (xterm is the only one that
displays the tree-view characters correctly). With little to no
fiddling at all it seems to work perfectly for me.
Ken Weingold
> I ssh from a gentoo box at work to another at home using both
> multi-gnome-terminal and xfree xterm (xterm is the only one that
> displays the tree-view characters correctly). With little to no
> fiddling at all it seems to work perfectly for me.
The two that always worked well for me for trees and colors, assuming
you have a full terminfo definition file, are rxvt and dtterm. rxvt
when exiting from programs like less will actually totally wipe the
program from the screen when you exit, putting you back into the
console as if it had never been run. dtterm will leave whatever is
left from the program. Usually I prefer the way dtterm handles it,
but in Mac OS X's Terminal, dtterm always leaves the right parentheses
when starting mutt. A refresh will kill it. Annoying, though.
Anyone know technically what the difference is between the ways that
programs exit, clearing itself from the screen or leaving it?
-Ken
Robert Ian Smit
> On windows, I use PuTTY and on Linux, I use OpenSSH. The problem is
> identical in frequency and symptoms on both clients.
I have had screen problems with Putty myself using Mutt. I changed a
setting and now everything works great. It was called something like
"use background colour to clear screen" (I don't use Putty at home
for obvious reasons, so look around in the configuration panel for
something _like_ that).
I just wiped my Gentoo installation so I can't confirm the problem.
Can you install Mutt locally and use the same .muttrc?
I would look for a solution on the client side first. All problems I
ever had, had to do with the client.
Bob
Keith R. John Warno
> Keith R. John Warno wrote:
> > it + mutt. However I haven't seen any problems using
> > xterm+openssh+mutt on a Linux box.
>
> terminfo definition that works pretty well in my experience.
Ah yes most excellent. Thanks for the info; I just found the putty
terminfo via the wishlist section at putty's home page.
<http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/terminfo.html>
Quoting that page as the reason to having a putty terminfo: "...as an
alternative to having PuTTY claim to be an xterm and hoping everybody's
xterms behave similarly." Very true, especially in an environment with
many different Unix variants, distros, etc.
$TERM had been set to ``xterm'', and I've been using the xterm terminfo
entries that are distributed with XFree86 4.2.x, with minor tweaks for
keyboard issues. The oddities I had been seeing were only related to
color in mutt 1.4, for example the status bar in my setup is supposed to
have a solid blue background but with putty && [ "$TERM" = "xterm" ],
there'd be a "gap" where the default color (black in this case) would be
used instead. Weird. Hmm seems that gap is right in the place where I
use '%> ' in $status_format. I don't use color attributes in many other
mutt areas so I don't know if this "gap" happens elsewhere.
The putty terminfo entry works fine. Thanks again.
Keith.
Thomas Dickey
> - On Wed, 30.Oct.2002, 19:51EST, Will Yardley uttered:
> > Keith R. John Warno wrote:
> > > Putty is broken in this respect. I've seen some wild term issues with
> > > it + mutt. However I haven't seen any problems using
> > > xterm+openssh+mutt on a Linux box.
> >
> > What terminal setting are you using with PuTTY? There is a putty
> > terminfo definition that works pretty well in my experience.
>
> Ah yes most excellent. Thanks for the info; I just found the putty
> terminfo via the wishlist section at putty's home page.
> <http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/terminfo.html>
> The putty terminfo entry works fine. Thanks again.
The first one on that page has some typographical errors in the cursor movement.
(There are other differences which I don't have the time to check - ymmv)
This is one that I wrote for ncurses last year:
# Reconstructed via infocmp from file: /usr/lib/terminfo/p/putty
putty|xterm clone (win32),
am, bw, ccc, km, mir, msgr, xenl,
colors#8, cols#80, it#8, lines#24, pairs#64,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m, bold=\E[1m, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM, dl1=\E[M,
ech=\E[%p1%dX, ed=\E[J, el=\E[K, enacs=\E)0, home=\E[H,
hpa=\E[%i%p1%dG, ht=^I, hts=\EH, il=\E[%p1%dL, il1=\E[L,
ind=^J,
initc=\E]P%?%p1%{9}%>%t%p1%{10}%-%'a'%+%c%e%p1%d%;%p2%{255}%&%Pr%gr%{16}%/%Px%?%gx%{9}%>%t%gx%{10}%-%'A'%+%c%e%gx%d%;%gr%{15}%&%Px%?%gx%{9}%>%t%gx%{10}%-%'A'%+%c%e%gx%d%;%p3%{255}%&%Pr%gr%{16}%/%Px%?%gx%{9}%>%t%gx%{10}%-%'A'%+%c%e%gx%d%;%gr%{15}%&%Px%?%gx%{9}%>%t%gx%{10}%-%'A'%+%c%e%gx%d%;%p4%{255}%&%Pr%gr%{16}%/%Px%?%gx%{9}%>%t%gx%{10}%-%'A'%+%c%e%gx%d%;%gr%{15}%&%Px%?%gx%{9}%>%t%gx%{10}%-%'A'%+%c%e%gx%d%;,
is2=\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4l\E8\E>,
kbs=\177, kcbt=\E[Z, kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC,
kcuu1=\EOA, kdch1=\E[3~, kf1=\E[11~, kf10=\E[21~,
kf11=\E[23~, kf12=\E[24~, kf13=\E[25~, kf14=\E[26~,
kf15=\E[28~, kf16=\E[29~, kf17=\E[31~, kf18=\E[32~,
kf19=\E[33~, kf2=\E[12~, kf20=\E[34~, kf3=\E[13~,
kf4=\E[14~, kf5=\E[15~, kf6=\E[17~, kf7=\E[18~, kf8=\E[19~,
kf9=\E[20~, kfnd=\E[1~, kich1=\E[2~, kmous=\E[M, knp=\E[6~,
kpp=\E[5~, kslt=\E[4~, oc=\E]R, op=\E[39;49m, rc=\E8,
rev=\E[7m, ri=\EM, rmacs=^O, rmam=\E[?7l,
rmcup=\E[2J\E[?47l\E8, rmir=\E[4l, rmkx=\E[?1l\E>,
rmso=\E[27m, rmul=\E[24m,
rs2=\E7\E[r\E8\E[m\E[?7h\E[?1;3;4;6l\E[4l\E>, sc=\E7,
setab=\E[4%p1%dm, setaf=\E[3%p1%dm,
sgr=\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;m%?%p9%t\016%e\017%;,
sgr0=\E[m, smacs=^N, smam=\E[?7h, smcup=\E7\E[?47h,
smir=\E[4h, smkx=\E[?1h\E=, smso=\E[7m, smul=\E[4m,
tbc=\E[3g, u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?1;2c, u9=\E[c,
vpa=\E[%i%p1%dd,
--
Thomas E. Dickey <dic...@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net