From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: jonetsu Newsgroups: gmane.emacs.help Subject: Re: Using gdb (windows popping up) Date: Mon, 10 Jun 2019 09:33:24 -0400 Message-ID: <20190610093324.2c71fc44@mistral> References: <20190609115246.41281b50@mistral> <83ftoibofg.fsf@gnu.org> <20190609145921.0fc60f3c@mistral> <83ef42bmij.fsf@gnu.org> <20190609152705.705c806b@mistral> <20190609154856.7d20feea@mistral> <20190609171036.18a89cb0@mistral> <87tvcymlba.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="130035"; mail-complaints-to="usenet@blaine.gmane.org" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jun 10 15:34:04 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1haKR2-000Xhm-9g for geh-help-gnu-emacs@m.gmane.org; Mon, 10 Jun 2019 15:34:04 +0200 Original-Received: from localhost ([::1]:46474 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1haKR1-0006MI-8V for geh-help-gnu-emacs@m.gmane.org; Mon, 10 Jun 2019 09:34:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46728) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1haKQV-0006Iu-6G for help-gnu-emacs@gnu.org; Mon, 10 Jun 2019 09:33:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1haKQT-0007Kt-Lp for help-gnu-emacs@gnu.org; Mon, 10 Jun 2019 09:33:30 -0400 Original-Received: from pmta11.teksavvy.com ([76.10.157.34]:33629) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1haKQQ-0007J6-DG for help-gnu-emacs@gnu.org; Mon, 10 Jun 2019 09:33:27 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2HbBgDyWv5c/0Tb1BhlH4NaL4FuKIQVi?= =?us-ascii?q?HuMBTUBjiARi3QJAQEBOgECAQGEOgICAQECgnQkOBMBAwEBAQQBAQEBBAICaSi?= =?us-ascii?q?FTAEEASMzKAsIAwkRAgUhAgIPSBkbhHIDDg+nJYExh3shSYFGImooi3SBP0CEI?= =?us-ascii?q?z6FEYI9glgEqScJghGBaYkxiBwnDIxgii+lWyKBWHAVgyeQbiYwgQIBBgEBARU?= =?us-ascii?q?IEwUFAQGOWwEB?= X-IPAS-Result: =?us-ascii?q?A2HbBgDyWv5c/0Tb1BhlH4NaL4FuKIQViHuMBTUBjiARi3Q?= =?us-ascii?q?JAQEBOgECAQGEOgICAQECgnQkOBMBAwEBAQQBAQEBBAICaSiFTAEEASMzKAsIA?= =?us-ascii?q?wkRAgUhAgIPSBkbhHIDDg+nJYExh3shSYFGImooi3SBP0CEIz6FEYI9glgEqSc?= =?us-ascii?q?JghGBaYkxiBwnDIxgii+lWyKBWHAVgyeQbiYwgQIBBgEBARUIEwUFAQGOWwEB?= X-IronPort-AV: E=Sophos;i="5.60,575,1549947600"; d="scan'208";a="96717469" Original-Received: from 24-212-219-68.cable.teksavvy.com (HELO mistral) ([24.212.219.68]) by smtp.teksavvy.com with ESMTP; 10 Jun 2019 09:33:24 -0400 In-Reply-To: <87tvcymlba.fsf@telefonica.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 76.10.157.34 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120892 Archived-At: On Mon, 10 Jun 2019 00:36:08 +0200 =C3=93scar Fuentes wrote: > There is a huge difference. A new Emacs instance does not share state > with other instances. >=20 > A frame is just what in modern GUI terminology is known as a toplevel > window, or what most users call a window. An Emacs instance can have > multiple frames, just like the same Firefox or LibreOffice instance > can have multiple windows. Yes, but for all user/practical purposes it is another instance in the sense that another 'app' is popping up showing the source code, hiding the other emacs beneath it, while the gdb interactive buffer remains in this 'other app' underneath. The effect wished by the user is one of having the gdb interactive buffer side-by-side with the source code as the debugging execution is made. Which is fairly normal, if not totally useful. New frame or new instance, the user effect remains the same: the source code is no longer beside the debugging session. As a summary, setting gdb-display-io-nopopup to non-nil adds a lot of stability to what was otherwise termed as an "aggressive" approach of popping up a frame. =20 It adds a lot of stability, which is a way of saying that there's still a bit of jitter at the beginning of a M-x gdb session, when the gdb input/output window is brought up. At that moment there's still a bit of a brawl as emacs insists to order windows contrary to what the user normally expects from emacs, but that can be dealt with and from there on a stability is assured for the debugging session and the user has a good amount of freedom in placing windows and buffers as they are deemed to be: the usual emacs way. gdb-display-io-nopopup (since emacs 25) seems to be the best solution to a problem that perhaps should not have been there from the start.