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: Sat, 27 Nov 2004 04:53:36 +1300 Message-ID: <16807.20864.538433.624364@farnswood.snap.net.nz> References: <16805.16406.567084.398496@farnswood.snap.net.nz> <87hdndapae.fsf-monnier+emacs@gnu.org> <16806.29150.178158.7827@farnswood.snap.net.nz> <87d5y1gsmk.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 1101484772 26237 80.91.229.6 (26 Nov 2004 15:59:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 26 Nov 2004 15:59:32 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 26 16:59:29 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 1CXiVM-0004XC-00 for ; Fri, 26 Nov 2004 16:59:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CXiec-0001nM-GK for ged-emacs-devel@m.gmane.org; Fri, 26 Nov 2004 11:09:02 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CXieS-0001ly-5k for emacs-devel@gnu.org; Fri, 26 Nov 2004 11:08:52 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CXieR-0001lL-7j for emacs-devel@gnu.org; Fri, 26 Nov 2004 11:08:51 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CXieQ-0001l8-SK for emacs-devel@gnu.org; Fri, 26 Nov 2004 11:08:50 -0500 Original-Received: from [202.124.108.240] (helo=farnswood.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CXiV6-0006ru-MW for emacs-devel@gnu.org; Fri, 26 Nov 2004 10:59:13 -0500 Original-Received: by farnswood.snap.net.nz (Postfix, from userid 501) id 79711627EE; Fri, 26 Nov 2004 15:53:37 +0000 (GMT) Original-To: Stefan Monnier In-Reply-To: <87d5y1gsmk.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:30395 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30395 > Well, I know what it does. My question had to do with the end goal: > "protect the contents of a window" is not very clear. Which scenario are > you trying to avoid? I'm thinking of two modes of operation. Firstly the gdb buffers in separate frame which I think was working OK. Secondly the gdb buffers in one frame (either using gdb-many windows or invoking the commands gdb-display-breakpoints etc separately) which was not so good. I've tried to get rid of gdb-display-buffer as much as possible so that it only executes when explicitly invoked through the gdb-display-breakpoints family. I've got rid of gdb-view-source etc. The machine code is not juggled with the source but appears as an unrelated buffer. I don't know what I was thinking of but there was only one overlay arrow available at the time. I've only tested it very quickly, its probably a bit flakey. Nick