From: "Kévin Le Gouguec" <firstname.lastname@example.org> To: Brandon Guttersohn <email@example.com> Cc: Bastien <firstname.lastname@example.org>, email@example.com Subject: Re: Possible fix for :includes header argument in org-babel C source blocks Date: Fri, 29 May 2020 11:57:29 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Brandon Guttersohn's message of "Thu, 28 May 2020 22:37:32 -0500") Brandon Guttersohn <firstname.lastname@example.org> writes: > Apologies for the regression, and thank you for fixing it. I neglected > to run the tests before suggesting that fix -- I'll try not to do that > again.. No biggie, that got me to finally try out Babel ;) <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… I find the "make-test-before-commit" discipline easy enough to adhere to at $DAYJOB; it's not as straightforward when contributing to free software, when I'm frequently pressed for time, running on battery on a low-end laptop… Running a few unit tests is not a big deal, but it's not trivial to anticipate which ones to run; test-foo.el is rarely enough to catch regressions introduced by tweaking foo.el. Having something (e.g. emba.gnu.org) pick up patches sent to the mailing list and report new test failures would be very helpful, for contributors if not for maintainers. </rant> > I can at least confirm that the patch wasn't intended to change how > C-header-files are specified in the org-babel-block-header. The goal > was only to change how the headers are formatted in the generated > C-language file during execution, and only for headers which were not > wrapped in <>'s. 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.
next prev parent reply other threads:[~2020-05-29 9:57 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 [this message] 2020-05-30 17:29 ` Brandon Guttersohn 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).