From: rey-coyrehourcq <sebastien.rey-coyrehourcq@univ-rouen.fr>
To: Jack Kamm <jackkamm@gmail.com>,
gmauer@gmail.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Improving Org Mode for VSCode - Thinking Aloud
Date: Sun, 24 May 2020 22:19:50 +0200 [thread overview]
Message-ID: <5ba46d6ef7ce5be02b024c6f3b8632a5a806fcb3.camel@univ-rouen.fr> (raw)
In-Reply-To: <87v9kltrcv.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
Hi,
Really cool discussion here.
My two cents, Jupyter & Kernel on various langage, which have a very
large community, could be an interesting backend for org-babel on
VSCode or anyeditoryouwantusehere.
Lot of things start to appear to collaborate online around
online/scientific cnotebook/literate programing this last year, and that continue, for example i discover recently :
Stencila : https://github.com/stencila=
org-babel / org-mode outside of emacs has a great potential to lead an
alternative to other markdown (RStudio / Jupyter) solution.
Best regards
Le dimanche 24 mai 2020 à 06:06 -0700, Jack Kamm a écrit :
> It would be very good indeed for org-babel if it could be ported to
> other editors. One of the biggest drawbacks of org-babel notebooks is
> that I can't collaborate with my colleagues on them, since I can't
> expect them to use Emacs.
>
> Aside from VSCode, I think RStudio would be an excellent target for a
> few reasons:
>
> - Literate programming is already popular among R users (see also:
> knitr, sweave, Rmarkdown)
> - There is a strong ob-R community here
> - There are some prominent Emacs users among the Rstudio developers
> (e.g. Lionel Henry, who I think is both an Rstudio and ESS
> developer)
>
> However, this would be a massive undertaking, and ultimately would
> need
> a volunteer to step up to the plate. I don't have any bandwidth to do
> this in the foreseeable future but dream of working on it one day.
> The
> biggest downside -- it would require spending considerable time
> outside
> Emacs!
>
--
Sébastien Rey-Coyrehourcq
Research Engineer UMR IDEES
02.35.14.69.30
{Stronger security for your email, follow EFF tutorial :
https://ssd.eff.org/}
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-24 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 17:55 Improving Org Mode for VSCode - Thinking Aloud George Mauer
2020-05-23 15:52 ` Bastien
2020-05-23 23:41 ` stardiviner
2020-05-24 4:14 ` Tim Cross
2020-05-24 11:39 ` Bastien
2020-05-24 11:38 ` Bastien
2020-05-24 12:39 ` stardiviner
2020-05-24 13:06 ` Jack Kamm
2020-05-24 13:12 ` Fabrice Popineau
2020-05-24 20:19 ` rey-coyrehourcq [this message]
2020-05-27 11:11 ` Matt Price
[not found] <mailman.53.1585843207.3581.emacs-orgmode@gnu.org>
2020-04-02 18:25 ` Daryl Manning
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=5ba46d6ef7ce5be02b024c6f3b8632a5a806fcb3.camel@univ-rouen.fr \
--to=sebastien.rey-coyrehourcq@univ-rouen.fr \
--cc=emacs-orgmode@gnu.org \
--cc=gmauer@gmail.com \
--cc=jackkamm@gmail.com \
/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).