|
From: Bob R. <bo...@br...> - 2009-07-25 23:52:25
|
On Tue, Jan 20, 2009 at 06:54:05PM +0800, Kuang He wrote: > On Wed, Dec 17, 2008 at 10:14 AM, Bob Rossi <bo...@br...> wrote: > > On Fri, Sep 26, 2008 at 01:03:10PM -0400, Kuang He wrote: > >> By the way, when I press CTRL-L in the gdb window, it does not clear > >> the screen, but rather generates a new input line. Is this intended, > >> or a bug? > > > > I just fixed this upstream. Hopefully I'll be able to get a release out > > soon. There is still a few more bug fixes I need to get done. > > > > If you type CTRL-L in CGDB, it now clears the entire GDB window with > > newlines. > > Hi Bob, > > I've tested the feature, and it works OK! > > One small problem though: each time I press Ctrl+L, it would generate > a chunk of empty lines in the command history (shown using > PageUp/PageDn). This is no big problem, but I feel that I should point > it out. Maybe it is due to the design that texts are shown at the > bottom rather than at the top of the screen after clearing the screen. Hi, I'm trying to prepare a release of CGDB, and I didn't like the way I implemented this feature, so I'm working on fixing it. My patch has the gdb prompt starting at the top of the gdb window and it moves down, like it would if you use gdb from the terminal directly. Also, I made it so that when you hit Ctrl+l, that the prompt goes back to the top. My question is this, currently, my patch clears the history in the gdb window, so that if you hit Ctrl+l, you can't see the previous history anymore with page up. Is this desirable? I could alternatively move the gdb prompt to the top of the window, and keep the history. That would be a little more work for me... Anyone care? Bob Rossi |
