From: ian martins <email@example.com> To: Kyle Meyer <firstname.lastname@example.org> Cc: Org-Mode mailing list <Emacsemail@example.com> Subject: Re: org-babel support for haxe Date: Wed, 30 Sep 2020 06:08:01 -0400 [thread overview] Message-ID: <CAC=rjb4HaHFbRmYjro=z2WC2yyeRi4MnnGUHSWKWpZfKyTSM=Q@mail.gmail.com> (raw) In-Reply-To: <CAC=rjb5+1ZqZwWsFomMPS1Y3AEcN=DZEvFJ84nVUmcDCkeTJtg@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1666 bytes --] I wrote the ob-core patch I mentioned before but white writing the commit message I realized there's probably no need to modify ob-core at all. I was doing it in order to allow haxe and java to create subdirectories in the babel temp directory since both languages require class names to match file names and directory structures to match the class' package (which is like namespace in C). But for executing babel code blocks from the temp directory all that is needed is the output; the source file doesn't matter. I'll try updating the haxe and java patches to build and run directly from the babel temp directory. On Thu, Sep 24, 2020 at 5:17 PM ian martins <firstname.lastname@example.org> wrote: > with ob-java I assumed I shouldn't change ob-core, so I advised/overrode > ob-core instead of changing it. But it would be much better to change > ob-core. I'll submit those changes as a separate patch that modifies > ob-core. > > On Sun, Sep 13, 2020 at 4:04 PM Kyle Meyer <email@example.com> wrote: > >> ian martins writes: >> >> > ob-haxe and ob-java both involve a few changes to ob-core to allow temp >> > directories instead of just temp files. Should I submit that as a >> separate >> > patch? >> >> It looks like that change is included with your ob-java patch , which >> will be considered after 9.4 is released , so I think it's fine as >> is. (In my opinion, splitting up that patch would have been nice, but I >> don't think it's worth a reroll, at least until some initial comments >> come in.) >> >>  >> https://orgmode.org/list/CAC=rjb7AhmnRQ9Nc4Ao07qK3QZF4LVaTmU_R1fWqr+97NpnRJQ@mail.gmail.com >>  https://firstname.lastname@example.org >> > [-- Attachment #2: Type: text/html, Size: 2542 bytes --]
prev parent reply other threads:[~2020-09-30 10:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-12 4:37 ian martins 2020-09-05 7:24 ` Bastien 2020-09-05 11:48 ` ian martins 2020-09-06 15:24 ` Kyle Meyer 2020-09-12 15:18 ` ian martins 2020-09-13 20:04 ` Kyle Meyer 2020-09-24 21:17 ` ian martins 2020-09-30 10:08 ` ian martins [this message]
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 \ --in-reply-to='CAC=rjb4HaHFbRmYjro=z2WC2yyeRi4MnnGUHSWKWpZfKyTSM=Q@mail.gmail.com' \ --email@example.com \ --cc=Emacsfirstname.lastname@example.org \ --email@example.com \ --subject='Re: org-babel support for haxe' \ /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).