Re: GDB-UI and multiple frames

[Nick Roberts]

 > In the latter cases it's usually a very bad idea to delete the gdb command
 > window.  gdb-ui used to do this fairly often; nowdays it seems better but
 > still does so occasionally (usually when one of the `minor windows' like
 > program I/O, pops up).

The gdb command window should always remain visible unless it is explicitly
deleted by the user. This is done using set-window-dedicated-p in
gdb-display-buffer. Can you give an example of where gdb-ui deletes this
window?

 > > > Can some windows be made more important than others/hard to delete/easy 
 > > > to
 > > > redisplay contents when deleted etc?
 > > 
 > > Why?  Which concrete problems are you thinking of?
 > 
 > I think that might be handy: For instance, for command-line users, the
 > command-line window should be `important'.  Now that program I/O has it's own
 > buffer, sometimes I get that buffer popping up (and hiding the command line
 > window!) for programs where I don't care about the program I/O, and I'd
 > really like to be able to tell gud-mode `I/O is not important, don't bother
 > to pop up its window'.

Perhaps, I should make it an option as to whether gdb-ui displays program output
in its own buffer or in the command window.

Nick