(*** This bug was imported into bugs.kde.org ***) Package: konsole Version: Latest (using KDE 3.0.6 CVS/CVSup/Snapshot) Severity: wishlist Installed from: Compiled sources Compiler: Not Specified OS: Not Specified OS/Compiler notes: Not Specified Hello I really enjoy working with Konsole which is an almost perfect terminal emulator especially the possibility of having several terminals in the same window makes it unique. There are two things lacking though: 1 - a logging possibility of the output of each terminal. The log file could be named by default for a terminal named "Terminal1" "Terminal1.log". 2 - a simple search command like the one in Kate with which one could search for occurences of a word (or even a regex !) in the current Terminal and/or highlight them. This is sometimes useful for some large outputs. (Submitted via bugs.kde.org)
> 1 - a logging possibility of the output of each terminal. The log file tee? Do you really want to log every output of every window everytime? > 2 - a simple search command like the one in Kate with which one could > search for occurences of a word (or even a regex !) in the current What's wrong with Edit/Find in History...?
Stephan Binner wrote: >>1 - a logging possibility of the output of each terminal. The log file >> >> > >tee? Do you really want to log every output of every window everytime? > > I don't feel it's necessary either. You can always use "tee logfile" to dump standard I/O to log file. > > >>2 - a simple search command like the one in Kate with which one could >>search for occurences of a word (or even a regex !) in the current >> >> > >What's wrong with Edit/Find in History...? > > I thought he was talking about searching in the historic output (or screen buffer) not command history. I could be wrong ... But this sounds like a very useful feature for lazy people like me :) >(Complete bug history is available at http://bugs.kde.org/db/45/45612.html) >_______________________________________________ >konsole-devel mailing list >konsole-devel@mail.kde.org >http://mail.kde.org/mailman/listinfo/konsole-devel > > >
Le Lundi 22 Juillet 2002 20:45 Stephan Binner a écrit : > > 1 - a logging possibility of the output of each terminal. The log file > > tee? Do you really want to log every output of every window everytime? > No but it is often useful to log the output of a particular window. We program here in Nortel Networks very large executables (50 Mb or more) that are imbedded in electronic cards for wireless networks. So there is no GUI only textual output. Those executables are the product of several teams and they produce large amounts of data traces onscreen that need to be logged when we run them for later examination. We sometimes run those executables overnight and we can then examine the result on the next day. The output log usually is several tens of Mb. This way of working is quite common in the industry. So a logging facility is necessary. Every major terminal has one so it's a pity Konsole doesn't although on every other aspect it betters the other terminals IMHO. So I'd rather not have to resort to xterm or dtterm for this. > > 2 - a simple search command like the one in Kate with which one could > > search for occurences of a word (or even a regex !) in the current > > What's wrong with Edit/Find in History...? > Oh sorry ! I didn't see it !!! Thanx for everything (and especially for your wonderful software) !
> > 1 - a logging possibility of the output of each terminal. The log file > > tee? Do you really want to log every output of every window everytime? > No but it is often useful to log the output of a particular window. We program here in Nortel Networks very large executables (over 200Mb of running execs in real time) that are imbedded in electronic cards for networks. There is no GUI only textual output. Those executables are the product of several teams and they produce large amounts of data traces onscreen that need to be logged when we run them for later examination. We often run those executables overnight for testing and we can then examine the result on the next day. The output log usually is several tens of Mb. This way of working is quite common in the industry. So a logging facility is necessary. Every major terminal has one so it's a pity Konsole doesn't although on every other aspect it betters the other terminals IMHO. So I'd rather not have to resort to xterm or dtterm for this. > > 2 - a simple search command like the one in Kate with which one could > > search for occurences of a word (or even a regex !) in the current > > What's wrong with Edit/Find in History...? > Oh sorry ! I didn't see it !!! Thanx for everything (and especially for your wonderful software) ! Le Mardi 23 Juillet 2002 00:56 Try KDE a écrit : > Stephan Binner wrote: > >>1 - a logging possibility of the output of each terminal. The log file > > > >tee? Do you really want to log every output of every window everytime? > > I don't feel it's necessary either. You can always use "tee logfile" to > dump standard I/O to log file. > > >>2 - a simple search command like the one in Kate with which one could > >>search for occurences of a word (or even a regex !) in the current > > > >What's wrong with Edit/Find in History...? > > I thought he was talking about searching in the historic output (or > screen buffer) not command history. I could be wrong ... But this > sounds like a very useful feature for lazy people like me :) > Well yes. This is what I was requesting. A search command for the screen buffer. But it seems that there is one already in the Edit menu. I didn't see it simply because I like to have the menu bar turned off and the search command doesn't appear in the contextual menu. You can understand why it is especially useful in our business with the explanations above although for very large data I use the search command of my text editor. > >(Complete bug history is available at > > http://bugs.kde.org/db/45/45612.html) > > _______________________________________________ > >konsole-devel mailing list > >konsole-devel@mail.kde.org > >http://mail.kde.org/mailman/listinfo/konsole-devel > > (Complete bug history is available at http://bugs.kde.org/db/45/45612.html) -- ------------------------------- Nicolas JaninNortel Networks OA&M01 69 55 41 05
Edit->Find in History... Edit->Save History...
May I add a wish to the search output feature (it sounds difficult to implement in my ears so consider me impressed if you manage!:) ) Would it be possible to have a button with something like "reprint lines". Given that you search for a term "warning" hit reprint, and all lines from output history with the term gets reprinted in the terminal. This is basically the same as "save output" and then cat output.txt | grep warning, just faster and you don't need to delete output.txt afterwards.