Bug 25289

Summary: 'mq>' in mutt
Product: [Retired] Red Hat Linux Reporter: Tim Waugh <twaugh>
Component: screenAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED DEFERRED QA Contact: David Lawrence <dkl>
Severity: low Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-02-06 18:12:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Tim Waugh 2001-01-30 10:41:57 UTC
Send yourself mail, and reply to the mail.  Read your mail in mutt, in 
threaded mode.  You get an arrow from the first message to the second 
message.  Good.

Now try it within screen: instead of an arrow you get 'mq>'.  I could 
_swear_ this used to be an arrow.

Comment 1 Tim Waugh 2001-01-30 21:47:36 UTC
Or at least, this happens on a beta 1 machine.  Can't get it to happen on a 
beta 3 machine.

Comment 2 Bill Nottingham 2001-01-31 17:40:48 UTC
What font are you using?

Comment 3 Tim Waugh 2001-01-31 17:50:13 UTC
This also happens in a ssh session to devserv.devel.  mutt shows threads fine
until I try it inside a screen session.

This is through the eyes of a gnome-terminal, font 'fixed'.

Comment 4 Tim Waugh 2001-01-31 17:50:33 UTC
(and I'm on a beta 3 machine now)

Comment 5 Tim Waugh 2001-02-03 13:25:59 UTC
It happens on the beta 3 machine I'm using now.  Additionally, it only happens
with gnome-terminal; rxvt, xterm, konsole don't show the problem.

I'm using font 'fixed'.  Which should I try?

Comment 6 Bill Nottingham 2001-02-06 00:55:58 UTC
If it works with a normal gnome-term, nothing. Just checking.

I'm assuming running something like:

TERM=xterm mutt

produces a normal display?

Comment 7 Tim Waugh 2001-02-06 18:12:05 UTC
You assume incorrectly. ;-)

Can't you reproduce this?

Comment 8 Crutcher Dunnavant 2001-06-26 22:27:43 UTC
I've reproduced it. I have no idea how to fix it.