| Summary: | Typing 'reset' in Konsole should clear scrollback history | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | SiegeLord <siegelords_abode> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | adaptee |
| Priority: | NOR | ||
| Version: | 2.7.2 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
Thanks for your report. I think the same problem is also reported in bug 171598. I'm not sure whether the current behavior should be changed, since the current behavior has been there for quite a long time. As a workaround for your example, use the "Clear Scrollback and Reset" action (default shortcut is Ctrl+Shift+X) to accomplish what 'reset' does in xterm. BTW, AFAIK, some terminal emulators do not clear history upon 'reset'. Try mlterm and putty/pterm . *** This bug has been marked as a duplicate of bug 171598 *** |
Version: 2.7.2 (using KDE 4.7.2) OS: Linux Issuing the command 'reset' in Konsole does not clear the scrollback buffer like it does in virtually every terminal emulator I can think of (the exceptions are rxvt and its forks). Terminals where that does work include terminator, gnome-terminal, xcfe4-terminal, xterm. Reproducible: Always Steps to Reproduce: Issue the following commands in the Konsole window: for i in {0..500}; do echo $i; done #fill up the scrollback buffer reset Then try scrolling up (e.g. by pressing Shift+PgUp). Actual Results: You will see the numbers printed by the first line. Expected Results: You shouldn't be able to scroll up, as the command prompt shown after the 'reset' command should be the first line in the scroll buffer. The motivation behind this request is the following workflow: $ gcc buggy_program.c <gcc shows thousands of errors> Fix some of the initial errors $ gcc buggy_program.c <gcc shows thousands of errors> Because of the large number of errors gcc is prone to showing, it is hard to find where the first error is after the second invocation of gcc because they are somewhere in the middle of the scroll buffer. With a working reset command, this becomes easier, as you can discard the first set of errors by issuing it before you invoke gcc again.