emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daryl Manning <dwm+orgmode@wakatara.com>
To: emacs-orgmode@gnu.org
Cc: George Mauer <gmauer@gmail.com>
Subject: Re: Improving Org Mode for VSCode - Thinking Aloud
Date: Fri, 3 Apr 2020 02:25:32 +0800	[thread overview]
Message-ID: <CAL9aZkuAm8u1Qe3L2G8i4X3ts+hmj18Rg-=2FOEneWF-iGHh+A@mail.gmail.com> (raw)
In-Reply-To: <mailman.53.1585843207.3581.emacs-orgmode@gnu.org>

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

I think this is a great idea. I actually looked at the two org-mode
implementations on VS Code a long while back and was impressed they'd
gotten as far as they had. Besides the basic support they already have, for
me the big win for them would be able to take advantage of the emacs plugin
ecosystem somehow (though I have no idea how you'd run some sort of in-VSC
lisp interpreter to make some of the plugins work). I know, however, that
the big org-mode boon for me is having packages like deft,
org-super-agenda, org-journal etc as well and being able to have
org-agenda/todos and org-contacts working in there.

What did you have in mind, exactly?  (cuz strangely I am using VS Code more
and more for coding, and emacs more as a note, journaling, organization,
and GTD app... 8-/ )


On Fri, Apr 3, 2020 at 12:01 AM <emacs-orgmode-request@gnu.org> wrote:

> Send Emacs-orgmode mailing list submissions to
>         emacs-orgmode@gnu.org
> ------------------------------
> Message: 4
> Date: Wed, 1 Apr 2020 12:55:27 -0500
> From: George Mauer <gmauer@gmail.com>
> To: emacs-orgmode <emacs-orgmode@gnu.org>
> Subject: Improving Org Mode for VSCode - Thinking Aloud
> Message-ID:
>         <
> CA+pajWK0_jiVdFwrHepxLU21vL+iVpAYN8zArVUDvVMpPdjV0Q@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 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?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20200401/2f8e3466/attachment.html
> >
> ------------------------------

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

       reply	other threads:[~2020-04-02 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.53.1585843207.3581.emacs-orgmode@gnu.org>
2020-04-02 18:25 ` Daryl Manning [this message]
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
2020-05-27 11:11     ` Matt Price

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='CAL9aZkuAm8u1Qe3L2G8i4X3ts+hmj18Rg-=2FOEneWF-iGHh+A@mail.gmail.com' \
    --to=dwm+orgmode@wakatara.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gmauer@gmail.com \


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