From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id KFTnKBOY0l4kMAAA0tVLHw (envelope-from ) for ; Sat, 30 May 2020 17:29:55 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id sHvSJBOY0l6CYQAAB5/wlQ (envelope-from ) for ; Sat, 30 May 2020 17:29:55 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 02654940667 for ; Sat, 30 May 2020 17:29:55 +0000 (UTC) Received: from localhost ([::1]:47168 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jf5Iw-0006k6-0j for larch@yhetil.org; Sat, 30 May 2020 13:29:54 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58352) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jf5Ia-0006jj-M9 for emacs-orgmode@gnu.org; Sat, 30 May 2020 13:29:32 -0400 Received: from mout-p-101.mailbox.org ([2001:67c:2050::465:101]:31666) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1jf5IY-0001S6-Cp; Sat, 30 May 2020 13:29:31 -0400 Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mout-p-101.mailbox.org (Postfix) with ESMTPS id 49Z7j05rLgzKmVn; Sat, 30 May 2020 19:29:24 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter06.heinlein-hosting.de (spamfilter06.heinlein-hosting.de [80.241.56.125]) (amavisd-new, port 10030) with ESMTP id 4dD5r21RF6yp; Sat, 30 May 2020 19:29:21 +0200 (CEST) Subject: Re: Possible fix for :includes header argument in org-babel C source blocks To: =?UTF-8?Q?K=c3=a9vin_Le_Gouguec?= References: <21b0cd85-d678-2fe6-3c22-e41abc6cf242@guttersohn.org> <87wo51jo5w.fsf@gnu.org> <875zchyq7y.fsf@gmail.com> <87imggx045.fsf@kyleam.com> <875zcgwjo7.fsf@gmail.com> <87blm8v09s.fsf@gmail.com> <87tuzzukqe.fsf@gmail.com> From: Brandon Guttersohn Message-ID: <1821ea63-9168-bc02-377a-5429cbbf2f7c@guttersohn.org> Date: Sat, 30 May 2020 12:29:17 -0500 MIME-Version: 1.0 In-Reply-To: <87tuzzukqe.fsf@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 838521693 X-Rspamd-Score: -3.02 / 15.00 / 15.00 Received-SPF: pass client-ip=2001:67c:2050::465:101; envelope-from=brandon@guttersohn.org; helo=mout-p-101.mailbox.org X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Bastien , emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.01 X-TUID: RyCKq13epdLx > > I don't know if it's been mentioned in the "issue tracker?" thread, but > if I could pick just *one* feature off web-based forges, it'd be > automated testing with CI… > [...] Automated testing has been a massive time-saver everywhere I've seen it used, though I'm not sure I've ever seen it combined with the mailing-list-workflow that GNU and (off the top of my head) Gnome use. I guess a bot could just individually cherry-pick patches onto master, and it would usually be the correct thing to do? > OK; IIUC, before the patch it was not possible to generate double-quoted > includes short of backslash-escaping the double quotes; that's why I > assumed that the goal of the patch was to make it easier to use > double-quoted includes, which I thought worth advertising in ORG-NEWS. Yeah, I believe you understand correctly. Ori found that you could get it to work if you escape the double quotes, /and/ place that string literal inside a quoted form, but that was more of a happy accident than a design choice as far as I can tell. So this patch is sort of a new feature, but a trivial one.