From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: Re: Window/buffer management in gdb-ui Date: Fri, 26 Nov 2004 12:59:26 +1300 Message-ID: <16806.29150.178158.7827@farnswood.snap.net.nz> References: <16805.16406.567084.398496@farnswood.snap.net.nz> <87hdndapae.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1101427572 8612 80.91.229.6 (26 Nov 2004 00:06:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 26 Nov 2004 00:06:12 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 26 01:05:57 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CXTca-0001M3-00 for ; Fri, 26 Nov 2004 01:05:56 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CXTln-0004QR-Re for ged-emacs-devel@m.gmane.org; Thu, 25 Nov 2004 19:15:27 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CXTlD-0004QL-Co for emacs-devel@gnu.org; Thu, 25 Nov 2004 19:14:51 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CXTlB-0004PC-V2 for emacs-devel@gnu.org; Thu, 25 Nov 2004 19:14:50 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CXTlB-0004P3-Ps for emacs-devel@gnu.org; Thu, 25 Nov 2004 19:14:49 -0500 Original-Received: from [202.124.110.160] (helo=farnswood.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CXTbg-0003Vj-Tg for emacs-devel@gnu.org; Thu, 25 Nov 2004 19:05:01 -0500 Original-Received: by farnswood.snap.net.nz (Postfix, from userid 501) id E1D92627EE; Thu, 25 Nov 2004 23:59:26 +0000 (GMT) Original-To: Stefan Monnier In-Reply-To: <87hdndapae.fsf-monnier+emacs@gnu.org> X-Mailer: VM 6.97 under Emacs 21.2.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:30367 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30367 > > gdb-display-buffer was part of gdba.el. It did extra things like not > > replace the window with the GUD buffer with new content. Perhaps > > display-buffer could be used but now I make new gdb-related windows > > dedicated here > > Why do you make the window dedicated. I think a window should only be made > dedicated when it's created. If you take a preexisting window that > potentially shows any buffer (even unrelated to GDB-UI) and make it > dedicated it'll screw things up sooner or later. Its the only way, that I know of, to protect the contents of a window. I think I only make the windows dedicated *after* I put the gdb-related stuff in them. I take your point that dedicated windows can be a nuisance. Thats why I try to undedicate any source buffers left after a debug session. The special-frames-regexp seems to make the window dedicated indirectly and so, to be honest, I can't see how this differs, in practice, from what I had before. > > It doesn't seem to interfere with the setups that I'm thinking of, so I've > > installed these changes. I don't really know what the change below does > > but gdb-frame-breakpoints-buffer is one of a family of commands accessible > > from the menubar (GUD->GDB Frames->...) so should these be changed also? > > I think so, yes. > What it does is that it allows users to specify the behavior they want in > special-display-regexp or special-display-buffer-names. I've changed these (apart from gdb-frame-gdb-buffer because the gud buffer is covered by same-window-regexps). I've removed the menubar and minibuffer from the resulting frames using special-display-frame-alist (maybe this make no difference with your setup). I tried not to select the buffer by using display-buffer instead of pop-to-buffer but it still seems to select it anyway (Is this a bug in Emacs?). Nick