emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-orgmode@gnu.org, Aaron Madlon-Kay <aaron@madlon-kay.com>
Subject: Re: [PATCH] ob-ruby.el: Don't reuse the same buffer among different named
Date: Sun, 13 Dec 2020 20:00:50 GMT	[thread overview]
Message-ID: <87v9d5tr0v.fsf@kyleam.com> (raw)
In-Reply-To: <875z55fr3p.fsf@mail.linkov.net>

Juri Linkov writes:

> Thanks for notifying me.  I completely agree that the most suitable
> place to fix would be in org-babel-ruby-initiate-session.  So here
> is a patch that I tested with different org header args:
> Subject: [PATCH] ob-ruby.el: Funcall command if it's a function from
>  inf-ruby-implementations
> * lisp/ob-ruby.el (org-babel-ruby-initiate-session): When 'command'
> is a function from 'inf-ruby-implementations', use 'funcall' to get
> a command string for the first arg of 'run-ruby-or-pop-to-buffer'.
> This is like what 'run-ruby' does.

Thanks.  Pushed (57a70d505), tacking on a Reported-by trailer to the
commit message.

  reply	other threads:[~2020-12-13 20:01 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
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 [this message]
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:

  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=87v9d5tr0v.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=aaron@madlon-kay.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=juri@linkov.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).