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: Sun, 9 Jun 2019 17:10:36 -0400 Message-ID: <20190609171036.18a89cb0@mistral> References: <20190609115246.41281b50@mistral> <83ftoibofg.fsf@gnu.org> <20190609145921.0fc60f3c@mistral> <83ef42bmij.fsf@gnu.org> <20190609152705.705c806b@mistral> <20190609154856.7d20feea@mistral> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="219484"; mail-complaints-to="usenet@blaine.gmane.org" To: Help Gnu Emacs mailing list Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Jun 09 23:10:54 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 1ha55Z-000uua-G8 for geh-help-gnu-emacs@m.gmane.org; Sun, 09 Jun 2019 23:10:53 +0200 Original-Received: from localhost ([::1]:38448 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha55X-0003qG-Rq for geh-help-gnu-emacs@m.gmane.org; Sun, 09 Jun 2019 17:10:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53485) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha55L-0003of-9V for help-gnu-emacs@gnu.org; Sun, 09 Jun 2019 17:10:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ha55K-0002zF-6x for help-gnu-emacs@gnu.org; Sun, 09 Jun 2019 17:10:39 -0400 Original-Received: from pmta21.teksavvy.com ([76.10.157.36]:56744) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1ha55K-0002xV-1u for help-gnu-emacs@gnu.org; Sun, 09 Jun 2019 17:10:38 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FUBwD2dP1c/0Tb1BhmHQEBBQEHBQGBZ?= =?us-ascii?q?YIRRyMFTCESKI0QjAM1AYkNhROMBQkBAQExCQECAQECgUmCbwICAQECgmokOBM?= =?us-ascii?q?BAwEBAQQBAQEBBAICaRwMgnhNawEBAQEBASMCDWQBBAE6HCgLCAMJGCUPEjYGE?= =?us-ascii?q?4MjgWoDDg8Pp2yHeQ1dgUAGIoESi3SBP0CEIz6CGkcDh0IElAiUYT4JghGBaY1?= =?us-ascii?q?ug18nDIIZikc5iXaWCY9SIoFYcBWDJ4sThVsmMAGBAQEGAQEBFQgTBQUBAY8tA?= =?us-ascii?q?QE?= X-IPAS-Result: =?us-ascii?q?A2FUBwD2dP1c/0Tb1BhmHQEBBQEHBQGBZYIRRyMFTCESKI0?= =?us-ascii?q?QjAM1AYkNhROMBQkBAQExCQECAQECgUmCbwICAQECgmokOBMBAwEBAQQBAQEBB?= =?us-ascii?q?AICaRwMgnhNawEBAQEBASMCDWQBBAE6HCgLCAMJGCUPEjYGE4MjgWoDDg8Pp2y?= =?us-ascii?q?HeQ1dgUAGIoESi3SBP0CEIz6CGkcDh0IElAiUYT4JghGBaY1ug18nDIIZikc5i?= =?us-ascii?q?XaWCY9SIoFYcBWDJ4sThVsmMAGBAQEGAQEBFQgTBQUBAY8tAQE?= X-IronPort-AV: E=Sophos;i="5.60,572,1549947600"; d="scan'208";a="94501670" Original-Received: from 24-212-219-68.cable.teksavvy.com (HELO mistral) ([24.212.219.68]) by smtp.teksavvy.com with ESMTP; 09 Jun 2019 17:10:36 -0400 In-Reply-To: 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.36 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:120890 Archived-At: On Sun, 9 Jun 2019 16:15:17 -0400 Noam Postavsky wrote: > The thing containing the windows. See also (info "(emacs) Frames"). > > https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html I see. Although, without have read everything, and I'm certain there are a lot of possibilities. it resumes itself for all practical purposes much like another emacs instance, apart from sharing the same underlying buffers. In this case here, that M-x gdb shows the source code (gdb-main-window non-nil) in another frame when the code starts running, while keeping gdb interactive in the original frame, is the same as another instance. Lost is the capability of seeing side-by-side gdb interactive and source. Of course the new frame can be tailored to show both, but what's the point in doing that every time gdb starts running code ? This is why I prefer so far the fix that fixes this automatic frame generation mentioned earlier. It enables free placement of buffers, just like in regular single-frame emacs operation, while running gdb.