From: Alberto Ramos <email@example.com>
To: Bastien <firstname.lastname@example.org>
Subject: Re: Please help by becoming a maintainer for an Org Babel file
Date: Tue, 27 Oct 2020 10:30:23 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
Dear Bastien, all
I would be very happy to:
1) Include ob-julia.el At this moment this is in a separate git repo
and is unmantained. I made some small changes myself, since this
outdated version does not work with current julia versions.
2) Help with ob-fortran.el In fact I submitted a patch some time ago:
That never made it to the org code.
The problem with all this is that I am a very poor elisp programmer. I
do not feel confident of being able to resolve all issues...
Please, let me know what you think... Maybe you think that it is
better to have someone trying to take care of this, even if maybe not
all issues are going to be resolved. Maybe you feel that it is better
to leave it as it is.
Please, let me know what you think.
Many thanks for the great work!
<#secure method=pgpmime mode=signencrypt>
Bastien <firstname.lastname@example.org> writes:
> Dear all,
> we are looking for more maintainers of individual Org Babel files.
> Jack and Ian are already in, I added myself to ob-clojure.el.
> If you feel like proposing yourself for maintaining an Org Babel
> language, that would be super helpful.
> Thanks a lot!
next prev parent reply other threads:[~2020-10-27 9:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 8:07 Please help by becoming a maintainer for an Org Babel file Bastien
2020-10-26 8:26 ` Tim Cross
2020-10-26 8:57 ` Bastien
2020-10-26 9:32 ` Jeremie Juste
2020-10-26 9:52 ` Bastien
2020-10-26 21:18 ` Jeremie Juste
2020-10-26 10:32 ` stardiviner
2020-10-26 13:41 ` Palak Mathur
2020-10-26 21:43 ` Bastien
2020-10-26 19:04 ` Palak Mathur
2020-10-27 8:52 ` Bastien
2020-11-04 2:53 ` Palak Mathur
2020-11-04 11:46 ` Bastien
2020-10-26 22:16 ` Justin Abrahms
2020-10-27 9:30 ` Alberto Ramos [this message]
2020-10-27 9:48 ` Eric S Fraga
2020-10-27 10:01 ` Alberto Ramos
2020-10-27 10:13 ` Eric S Fraga
2020-10-27 13:49 ` stardiviner
2020-10-28 8:55 ` Bastien
2020-10-28 11:44 ` stardiviner
2020-10-27 13:53 ` stardiviner
2020-10-28 8:54 ` Bastien
2020-10-27 18:16 ` Ken Mankoff
2020-10-28 8:56 ` Bastien
2020-11-01 1:59 ` Corwin Brust
2020-11-01 14:12 ` Bastien
2020-12-14 5:26 ` Bastien
2020-12-14 5:29 ` Corwin Brust
2020-12-14 5:43 ` Bastien
2021-02-25 15:01 ` Andy Klock
2021-02-26 5:58 ` Kyle Meyer
2021-03-02 7:23 ` Bastien
2021-03-02 14:21 ` Andy Klock
2021-03-02 14:16 ` Andy Klock
2021-04-25 12:19 ` Bastien
2021-03-03 1:23 ` Nick Savage
2021-04-25 12:18 ` Bastien
2021-05-07 0:59 ` Tyler Smith
2021-05-08 7:42 ` Bastien
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 \
* 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).