From: Kyle Meyer <firstname.lastname@example.org> To: Juri Linkov <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH] ob-ruby.el: allow specification of ruby command w/header arg Date: Sat, 14 Nov 2020 16:19:23 -0500 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Juri Linkov writes: > Thanks, this is a much needed change. But currently it is limited only > to non-session code execution. Here is an additional patch that also > supports the same feature for session code execution as well: > > ob-ruby.el: allow specification of session ruby command w/header arg > > * lisp/ob-ruby.el (org-babel-ruby-initiate-session): Use a header argument > to get ruby command. Thanks. I see you applied this today in the Emacs repo (844e82f5a8). I've ported it to the Org repo, but please avoid doing this in the future. The preferred method is for development to happen through Org's list and repo. I apologize because my word choice in bug#32676 may have caused confusion: Kyle Meyer writes: > Kévin Le Gouguec writes: > > That said... > >> IIUC, Org maintainers prefer for changes to be submitted to >> email@example.com; they only occasionally dive into >> firstname.lastname@example.org to look for open Org issues. > > ...submitting patches on the Org list is of course appreciated, > particularly for things that target Org rather than being part of a > tree-wide cleanup. I think "appreciated" understates how strong the preference is on Org's side.
next prev parent reply other threads:[~2020-11-14 21:20 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-20 8:49 Aaron Madlon-Kay 2020-10-20 8:49 ` [PATCH] ob-ruby.el: allow specification of ruby command w/header arg Aaron Madlon-Kay 2020-10-24 11:39 ` Bastien 2020-10-25 1:21 ` Aaron Madlon-Kay 2020-11-10 19:34 ` Juri Linkov 2020-11-14 21:19 ` Kyle Meyer [this message] 2020-11-25 19:41 ` Juri Linkov 2020-11-27 6:42 ` [PATCH] ob-ruby.el: Don't reuse the same buffer among different named Kyle Meyer 2020-11-28 22:23 ` Kyle Meyer 2020-12-11 7:23 ` Aaron Madlon-Kay 2020-12-13 4:03 ` Kyle Meyer 2020-12-13 19:22 ` Juri Linkov 2020-12-13 20:00 ` Kyle Meyer 2020-12-14 0:52 ` Aaron Madlon-Kay
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://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 \ /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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ email@example.com public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git