Bug 238883 - Konsole's Scrollback only clears instead of resets when using the 'reset' command.
Summary: Konsole's Scrollback only clears instead of resets when using the 'reset' com...
Status: RESOLVED NOT A BUG
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.4.3
Platform: Slackware Linux
: NOR minor
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-26 14:20 UTC by fatcandle
Modified: 2011-02-28 01:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fatcandle 2010-05-26 14:20:09 UTC
Version:           2.4.3 (using KDE 4.4.3) 
OS:                Linux

Using the reset command only clears the terminal. Is it wrong to think the desired output of reset is the same as choosing 
Scrollback -> Clear scrollback & Reset

Reproducible: Always

Steps to Reproduce:
Execute 'reset' on the command line

Actual Results:  
Scrollback clears.

Expected Results:  
Scrollback clears and resets.
Comment 1 Robert Knight 2010-05-26 15:08:17 UTC
> Steps to Reproduce:
> Execute 'reset' on the command line

> Actual Results:  
> Scrollback clears.

I don't see this.  The expected behavior when typing 'reset' on the command line is that the state of the terminal emulation is reset but the scrollback remains - which is what I see.
Comment 2 fatcandle 2010-05-28 13:24:33 UTC
Hmm. I thought the purpose of reset was to remove the ScrollBack buffer from the terminal.
Comment 3 Robert Knight 2010-05-28 13:43:13 UTC
> Hmm. I thought the purpose of reset was to remove the
> ScrollBack buffer from the terminal.

No.  The terminal emulator has a set of state information - such as the background/foreground colours, the position of the cursor, whether mouse input is enabled and what effect some of the keys have.  'reset' puts all this back to the state of the terminal when it was first started.

The main reason you'd have to use reset is if the terminal starts behaving strangely.