[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] Konsole, changing history size.
From:       Martijn Klingens <mklingens () yahoo ! com>
Date:       2001-07-23 22:41:11
[Download RAW message or body]

On Tuesday 24 July 2001 00:00, Guillaume Laurent wrote:
> On Monday 23 July 2001 22:23, Waldo Bastian wrote:
> > Well, either that or you just stop reading the output of the shell.
>
> Won't that ultimately block the running program or lose some input ?

Likely the latter, because I experienced a make session to continue until the 
end after a sigsegv in konsole a while ago. I noticed that the process kept 
on running as long as I didn't press the close button, so I became curious. 
Make ran until the end...

> > Anyway,
> > the current situation is a major step back from previous releases where
> > you were able to look at e.g. the output of a compile while you were
> > compiling. With the current code this isn't possible any more because it
> > keeps scrolling.
>
> I agree it's not convenient but on the other hand konsole history has been
> broken for quite a few releases already.
>
> I suggest we re-enable infinite, file-based history as an option along with
> the memory-based one we have right now, but either not use a pre-deleted
> temp file or issue a big fat warning telling the user about it.

Would be nice. It is likely that that is post-2.2 work because it probably 
adds strings, so I'd like to have the scrollbar scroll along with the history 
scrolling, so at least the scrollbar doesn't move until the data is _forced_ 
out of the history because the length is exceeded. Currently the scrollbar is 
completely useless as soon as the history buffer is full, even if the data is 
allowed to move zillions of lines before actually being removed...

Martijn

[prev in list] [next in list] [prev in thread] [next in thread]