From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from www523.your-server.de (www523.your-server.de [159.69.224.22]) by sourceware.org (Postfix) with ESMTPS id 101BA3858D33 for ; Thu, 28 Jul 2022 19:49:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 101BA3858D33 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tim-lange.me Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tim-lange.me DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tim-lange.me; s=default2108; h=Content-Type:MIME-Version:References: In-Reply-To:Message-Id:Cc:To:Subject:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=8Cn5Ba+Lulj4dIYKS2/gmy5UOYrbliQZZWRsxayX9UI=; b=ionrGBbqi4X5RNRgeJtLIOWKUY CDR7HY3nEeRxaXOqAmA4IJAo13swd2iecbJFgkQQ4t6JaO/xfGgZlbOXt5GvJKiC/XQbrRnt7/RAq nSyISgY4IRIMkwBrwDyA3MT3Gt5FOiSws74VGcndASrIkSVX0fd1M7svJPTw5I79T2ybnACC6ExwP /gELaRwXopZkEZ9awfAali+DRUEYFGho+6v6uX2HSEhkr8w149rWXsio7fq/BEcAq2y3Yt/QH2NUI cKSb5QWaGqtJ304WRUf52Lyd3Hln/k6JC36x6mvjID8jOw/IslwddzAekBEVycfCdNZuWvPhC1Sui RrfyBvHg==; Received: from sslproxy01.your-server.de ([78.46.139.224]) by www523.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1oH9VX-000D7N-Vm; Thu, 28 Jul 2022 21:49:20 +0200 Received: from [2001:41b8:83c:fa00:6614:184a:362a:2909] (helo=fedora) by sslproxy01.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oH9VX-000DFB-RS; Thu, 28 Jul 2022 21:49:19 +0200 Date: Thu, 28 Jul 2022 21:49:14 +0200 From: Tim Lange Subject: Re: Setting up editors for the GNU/GCC coding style? To: David Malcolm Cc: gcc@gcc.gnu.org Message-Id: <2QXQFR.JX7MU9S88TL03@tim-lange.me> In-Reply-To: References: X-Mailer: geary/40.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed X-Authenticated-Sender: mail@tim-lange.me X-Virus-Scanned: Clear (ClamAV 0.103.6/26615/Thu Jul 28 09:58:07 2022) X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_INFOUSMEBIZ, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2022 19:49:25 -0000 On Thu, Jul 28 2022 at 02:46:58 PM -0400, David Malcolm via Gcc wrote: > Is there documentation on setting up text editors to work with our > coding style? A lot of the next generation of developers aren't using > vi or emacs; they's using VS Code, CLion, and other editors. Does > anyone have docs on e.g. how to set up VS Code, CLion, etc (IntelliJ > ?) > to work well on GCC's own code base. FWIW I use Emacs; I've dabbed > with VS Code but haven't used it "for real". I did prepare my first patch(es) with vscode. For debugging, I set up vscode to launch gcc with gdbserver as wrapper and then let the vscode debugger to connect to the gdbserver. At first, I tried to get the gnu coding style to work in the hacky way by using tabSize=8 and rebinding tab to 2 spaces but later ditched that because it bothered me more than doing just spaces and replacing 8 spaces with 1 tab before sending the patch. That still wastes time because all files that I didn't touch look ugly unless I temporarily change the tabSize and some comments don't use tabs so I can't just replace all 8 spaces with 1 tab. For reference, my config files for gcc are available at [0]. - Tim [0] https://gist.github.com/timll/1c4c542c7c98e3610c14aec19cdf7e91 > > I'm hoping to add this to my newbies guide. > > Thanks > Dave >