Bug 146286 - Making history / scrollback search available in the KPart
Summary: Making history / scrollback search available in the KPart
Status: RESOLVED DUPLICATE of bug 162319
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-02 13:36 UTC by Alessandro Re
Modified: 2008-05-22 03:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Re 2007-06-02 13:36:51 UTC
Version:           2.7.5 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          gcc 4.1.1 
OS:                Linux

I use unlimited (or very very long) history size in yakuake, but it gets hard to read it if you need something specific (i.e. a keyword). So, why don't make history even more userful adding some kind of search/find tool? or (even better) a "grep in history"? or the possibility to save the whole history in a separate file? (so one could find using grep or his favourite tool)

To me, this is an important issue: many terminals don't give history search tool, and i often need to search in terminal history.

Thanks for the great job, anyway ;)
Comment 1 Bram Schoenmakers 2007-06-02 15:19:47 UTC
For the time being you can use screen(1) which allows you to search.
Comment 2 Eike Hein 2007-06-02 15:27:47 UTC
Unfortunately the Konsole KPart which Yakuake is based around presently doesn't implement the required interfaces.
Comment 3 Philip Rodrigues 2007-06-03 14:25:50 UTC
Eike, should this be moved to konsole then?
Comment 4 Eike Hein 2008-03-18 19:33:13 UTC
Moving to Konsole, indeed.

For the record, the KPart context menu does offer the option to save the scrollback to a file these days (i.e., in KDE 4 / Yakuake 2.9).
Comment 5 Eike Hein 2008-03-18 19:33:40 UTC
Renaming bug for clarity.
Comment 6 Eric@Helsinki 2008-04-21 06:55:09 UTC
More practically, I always wondered why when using the up arrow to scroll back into history, it doesn't filter with what is already in the command line.

The typical example case is when I type a long command line and then use many whatever commands afterwards. Suddenly, I happen to need again that first long command line. I naturally, start typing it (the first few characters) then remembers that I typed it already and scroll up in the history. Since I type the first few characters, Konsole should grep the history accordingly and show me only the commands I used that started in the same way.

Well, it felt so natural to me this way that I get annoyed when I realize I have to move up 25 commands in the history to find again the command I wanted which is only 20 characters long.
Comment 7 Robert Knight 2008-04-21 14:41:56 UTC
Eric, the command history is provided by the shell, probably 'bash', not Konsole.

If you want to search the history for commands beginning with text then press Ctrl+R and type the first few characters of the command.  Pres Ctrl+R to cycle through matches.  Search for "bash tips and tricks" for more information.  
Comment 8 Robert Knight 2008-05-22 03:05:01 UTC

*** This bug has been marked as a duplicate of 162319 ***