From: Monstara <monstara@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: ob-powershell fixes, looking for original author
Date: Fri, 18 Feb 2022 14:28:08 +0200 [thread overview]
Message-ID: <CAPvEROLCYXSrfF2ZhyQWLRv_k0NxtXO4NP3iGpEKFXMX7DV=+g@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETot_0k=Sm=dkKDd_obG9VKrfSZVNRgSXDdzD4zfOpZi0A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
I already made a pull request. The repo has not been touched for about five
years, though.
On Fri, Feb 18, 2022 at 1:56 PM John Kitchin <jkitchin@andrew.cmu.edu>
wrote:
> Try posting an issue on the original repo?
>
> On Fri, Feb 18, 2022 at 2:02 AM Monstara <monstara@gmail.com> wrote:
>
>> Hello, I found an incomplete implementation
>> <https://github.com/rkiggen/ob-powershell> of ob-powershell and fixed it
>> <https://github.com/MoisMoshev/ob-powershell>.
>> However, the original did not have a license, so it is not possible to
>> proceed further, e.g. put it up on melpa.
>> Is the original author here on the list? I think they do not have a
>> contact address on github. Also posted on reddit to no avail.
>>
>> Regards,
>> Mois
>>
> --
> John
>
> -----------------------------------
> Professor John Kitchin (he/him/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
[-- Attachment #2: Type: text/html, Size: 1886 bytes --]
next prev parent reply other threads:[~2022-02-18 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 7:00 ob-powershell fixes, looking for original author Monstara
2022-02-18 11:55 ` John Kitchin
2022-02-18 12:28 ` Monstara [this message]
2022-02-18 14:13 ` John Kitchin
2022-02-18 21:24 ` Monstara
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPvEROLCYXSrfF2ZhyQWLRv_k0NxtXO4NP3iGpEKFXMX7DV=+g@mail.gmail.com' \
--to=monstara@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.