emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: George Mauer <gmauer@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Improving Org Mode for VSCode - Thinking Aloud
Date: Wed, 1 Apr 2020 12:55:27 -0500	[thread overview]
Message-ID: <CA+pajWK0_jiVdFwrHepxLU21vL+iVpAYN8zArVUDvVMpPdjV0Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

With VSCode becoming ever-popular it seems like there might be some value
in getting org mode working there simply as a way of promoting org as an
excellent literate coding notebook.

VSCode already has a halfway decent org-mode but it doesn’t support
anything from Babel. I’m trying to think of relatively easy ways of adding
that ability. Here’s a thought: Most of babel that technically works
against the document itself, it doesn’t really need much document
integration with the editor. So could you get it working in vscode so long
as someone has a properly configured version of emacs installed locally?
“Evaluate/Export/etc” would just write the document, then use emacs to run
the appropriate commands on it and refresh the document view.

Of course features like the separate editor for src blocks and
folding #results would be nice too, but if the basics could work that would
be a huge win for org.

Any thoughts on the feasibility of this?

[-- Attachment #2: Type: text/html, Size: 1080 bytes --]

             reply	other threads:[~2020-04-01 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 17:55 George Mauer [this message]
2020-05-23 15:52 ` Improving Org Mode for VSCode - Thinking Aloud 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
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:

  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=CA+pajWK0_jiVdFwrHepxLU21vL+iVpAYN8zArVUDvVMpPdjV0Q@mail.gmail.com \
    --to=gmauer@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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