From: stardiviner <numbchild@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [ORG] [FEATURE] ob-js.el support :session for all existing JS packages
Date: Tue, 13 Mar 2018 11:19:42 +0800 [thread overview]
Message-ID: <3e3169d5-3edd-cee7-4858-9adedc081fda@gmail.com> (raw)
In-Reply-To: <87tvtli3h6.fsf@alphaville.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
Aha, I see now. thanks for your answer. @Nick
On 03/13/2018 01:54 AM, Nick Dokos wrote:
> "numbchild@gmail.com" <numbchild@gmail.com> writes:
>
>> After add more code, not it supports `js-comint`, `skewer-mode`, `Indium`.
>>
>> Waited many days, still no response. Anyone want to review this code?
>>
>> Recently view Org-mode mailing list, many threads has response. Why my post does not have any response?
>>
> Because reviewing code is hard: in this case, one needs some expertise
> in org, but also in JS and its supporting packages in emacs. Speaking
> for myself, I have some (rather rusty at this point) expertise in org,
> but none in the other areas; I also have no time. I suspect that one
> or more of these reasons are shared by most people on the list. The
> wonder of it is that many questions *do* get answered, but in many
> cases, they tend to be a short question-answer sequence. OTOH, there
> are topics that go on for years with no resolution in sight despite
> extended discussion. And there are certainly lots that fall by the
> wayside.
>
> So do not expect miracles, but if after a sufficient period of time,
> things seem to have fallen into the cracks and forgotten, then a bump
> might be warranted. But patience is a virtue!
>
[-- Attachment #2: Type: text/html, Size: 1981 bytes --]
prev parent reply other threads:[~2018-03-13 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 3:41 [ORG] [FEATURE] ob-js.el support :session for all existing JS packages numbchild
2018-03-12 17:54 ` Nick Dokos
2018-03-13 3:19 ` stardiviner [this message]
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=3e3169d5-3edd-cee7-4858-9adedc081fda@gmail.com \
--to=numbchild@gmail.com \
--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).