From: Brandon Guttersohn <email@example.com> To: "Kévin Le Gouguec" <firstname.lastname@example.org> Cc: Bastien <email@example.com>, firstname.lastname@example.org Subject: Re: Possible fix for :includes header argument in org-babel C source blocks Date: Sat, 30 May 2020 12:29:17 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> > <rant> > 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.
next prev parent reply other threads:[~2020-05-30 17:29 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> [not found] ` <firstname.lastname@example.org> 2020-05-27 22:20 ` Kévin Le Gouguec 2020-05-28 2:30 ` Kyle Meyer 2020-05-28 8:25 ` Kévin Le Gouguec 2020-05-28 10:09 ` Kévin Le Gouguec 2020-05-29 2:47 ` Kyle Meyer 2020-05-29 12:41 ` Failing tests (was: Possible fix for :includes header argument in org-babel C source blocks) Kévin Le Gouguec 2020-05-31 4:59 ` Kyle Meyer 2020-06-01 14:48 ` Failing tests Kévin Le Gouguec 2020-06-01 14:56 ` Kévin Le Gouguec 2020-06-03 4:20 ` Kyle Meyer 2020-06-01 13:54 ` Bastien 2020-05-29 3:37 ` Possible fix for :includes header argument in org-babel C source blocks Brandon Guttersohn 2020-05-29 9:57 ` Kévin Le Gouguec 2020-05-30 17:29 ` Brandon Guttersohn [this message] 2020-06-01 13:55 ` Bastien 2020-06-01 20:17 ` Kévin Le Gouguec 2020-06-02 0:02 ` Brandon Guttersohn 2020-05-29 2:45 ` Kyle Meyer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Possible fix for :includes header argument in org-babel C source blocks' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).