Bug 41650 - irc output doesn't scroll into term
Summary: irc output doesn't scroll into term
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ircii
Version: 7.1
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-05-21 17:13 UTC by Bernhard Ege
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-05-28 14:46:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Bernhard Ege 2001-05-21 17:13:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.3-2.14.14 i686)

Description of problem:
In RedHat 7.0, ircii caused every line that was scrolled out in the top of
the terminal to be scrolled into the xterm holding the ircii session. Now,
the linies are erased (only on screen scrolling). It is therefore not
possible to use the terminals scrollbar to scroll back in the previous
output. I really liked the previous (RedHat 7.0) way better.

How reproducible:
Always

Steps to Reproduce:
1. start irc.
2. cause enough output to make the text scroll.
3. try to see previous lines.
	

Actual Results:  Terminal does not remember lines scrolled out of irc.

Expected Results:  I tried a remote server that had another version of the
same irc program installed and the terminal did remember the lines that
were scrolled out at the top of the terminal.

Additional info:

package is: ircii-4.4Z-4

Comment 1 Bernhard Ege 2001-05-28 14:46:28 UTC
I installed the ircii-4.4M-4 irc client from RedHat 7.0 and now the xterm
scrollback works just fine. I couldn't determine wether it was intentional or
not, but I prefer the 4.4M scroll method over the 4.4Z.

Comment 2 Preston Brown 2001-07-19 17:43:46 UTC
this was intentional on the part of the IRC II authors.
If you need an IRC client with history, we suggest xchat, a graphical IRC 
client that we do ship.



Note You need to log in before you can comment on or make changes to this bug.