From: Eric Schulte <schulte.eric@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: R code block produces only partial output
Date: Wed, 06 Aug 2014 07:30:24 -0400 [thread overview]
Message-ID: <8761i5kg8f.fsf@gmail.com> (raw)
In-Reply-To: <87r40uwavs.fsf@gmail.com> (Aaron Ecay's message of "Tue, 05 Aug 2014 23:32:55 -0400")
Aaron Ecay <aaronecay@gmail.com> writes:
> Hi Eric,
>
> 2014ko abuztuak 5an, Eric Schulte-ek idatzi zuen:
>>
>
> [...]
>
>> I don't know.
>>
>> The Babel R support needs a dedicated maintainer. This was a role Dan
>> Davison originally filled. I've partially filled in since, but as a
>> *very* light R user I'm not the best person.
>
> I use babel’s R support (almost) every day for my work, and I know
> enough elisp to be getting along. I’ve not had tons of time for
> org/emacs development lately, but I think I can make enough time to
> maintain ob-R.el.
>
That would be great, and a personal relief. Perhaps you could begin
with a patch for the regexp issue in this thread?
>
> There are others who could probably do just as good (if not indeed
> better) a job. Rainer’s name springs to mind as someone who has
> submitted several patches for ob-R lately, but there are probably
> others who I’m not calling to mind immediately. I’d be happy to
> share with other willing volunteers, either as a joint maintainership
> or (perhaps preferably) alternating the position in a 3- to 6-month
> rota.
Yes, and some form of sharing would of course be great. Multiple active
maintainers is better than just one. I think the main thing is to have
someone who, in threads like this one with many good suggestions, will
take the initiative to move from discussion to a proposed patch, and
then to apply that patch down the line.
Thanks!
Eric
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)
next prev parent reply other threads:[~2014-08-06 11:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 11:18 R code block produces only partial output Andreas Kiermeier
2014-08-04 11:53 ` Eric Schulte
2014-08-04 12:23 ` Andreas Kiermeier
2014-08-04 13:10 ` Eric Schulte
2014-08-05 0:46 ` Andreas Kiermeier
2014-08-05 4:00 ` John Hendy
2014-08-05 4:31 ` Andreas Kiermeier
2014-08-05 18:05 ` Charles Berry
2014-08-05 19:02 ` Eric Schulte
2014-08-05 19:11 ` John Hendy
2014-08-05 19:57 ` Nick Dokos
2014-08-05 20:10 ` Nick Dokos
2014-08-05 22:21 ` Charles C. Berry
2014-08-06 3:32 ` Aaron Ecay
2014-08-06 11:30 ` Eric Schulte [this message]
2014-08-07 6:00 ` Aaron Ecay
2014-08-07 17:42 ` Charles C. Berry
2014-08-07 18:06 ` Aaron Ecay
2014-08-07 18:42 ` Charles C. Berry
2014-08-07 19:06 ` Thomas S. Dye
2014-08-09 8:54 ` Rainer M Krug
2014-08-16 5:05 ` Aaron Ecay
2014-08-16 18:50 ` Charles C. Berry
2014-08-16 20:58 ` Aaron Ecay
2014-08-17 6:03 ` Achim Gratz
2014-08-19 0:13 ` Aaron Ecay
2014-08-19 5:36 ` Achim Gratz
2014-08-23 8:32 ` Aaron Ecay
2014-08-23 9:24 ` Andreas Kiermeier
2014-08-23 17:10 ` Aaron Ecay
2014-08-23 18:35 ` Thomas S. Dye
2014-08-23 19:37 ` Ista Zahn
2014-08-24 0:10 ` Charles C. Berry
2014-08-28 5:24 ` Aaron Ecay
2014-09-01 5:00 ` Aaron Ecay
2014-09-01 16:08 ` Charles C. Berry
2014-08-09 8:48 ` Rainer M Krug
2014-08-06 1:11 ` Andreas Kiermeier
2014-08-06 2:21 ` Charles C. Berry
2014-08-06 3:24 ` Aaron Ecay
2014-08-06 15:59 ` Charles C. Berry
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=8761i5kg8f.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.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
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
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).