emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Gustav Wikström" <gustav@whil.se>
To: Russell Adams <RLAdams@AdamsInfoServ.Com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	"stanislaw_lem@tutanota.com" <stanislaw_lem@tutanota.com>
Subject: RE: FWD: Org-Babel Support for Powershell
Date: Sat, 6 Jun 2020 23:38:38 +0000	[thread overview]
Message-ID: <HE1PR0201MB23468C856DC6002756D3B7EDDA870@HE1PR0201MB2346.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20200606104300.GH23478@volibear>


Org babel support for Powershell is a great idea!

Powershell is very ...*ahem*... powerful, and it would likely benefit many users if it was usable and executable from within Org mode!

> -----Original Message-----
> From: Emacs-orgmode <emacs-orgmode-bounces+gustav=whil.se@gnu.org> On Behalf
> Of Russell Adams
> Sent: den 6 juni 2020 12:43
> To: emacs-orgmode@gnu.org
> Subject: Re: FWD: Org-Babel Support for Powershell
> On Fri, Jun 05, 2020 at 11:32:45PM +0200, stanislaw_lem--- via General
> discussions about Org-mode. wrote:
> > With Powershell 7 we got now a cross-platform scripting language for Windows
> > and Linux OS.
> Can you provide an example script you would run, and the example output?
> Basically a minimum working example, except the part where Babel would run it
> for you?

I know the question wasn't for me. But since I'm answering to your mail I can just as well provide an example anyhow:

#+begin_src powershell

: 4

> I think Org-Babel working with many languages is a noble goal, but I expect
> there would be difficulty getting Powershell support added to the core
> distribution. It might be limited to a separate package as it is very specific
> to a Windows only non-free language from a vendor with a long and sordid
> history
> of anti-OSS practices.

There should be zero issues in including it into core. Powershell is MIT-licensed and works across all platforms.

> My opinion is I would never consider using Powershell on Linux, despite your
> positive impression.

And I say the opposite. I would certainly use it!

/of topic
It's safe to say the free software movement has gained a strong footing in the software world. If it's "enemies" from the past are starting to walk in the same direction it would serve the free software advocates well to embrace and further encourage those steps. It would in my opinion be signs of maturity and true, good intentions. Judge not from where one comes, but for where one is heading.

Kind regards

  reply	other threads:[~2020-06-06 23:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <M90MAnN--3-2@tutanota.com>
2020-06-05 21:32 ` FWD: Org-Babel Support for Powershell stanislaw_lem--- via General discussions about Org-mode.
2020-06-06 10:43   ` Russell Adams
2020-06-06 23:38     ` Gustav Wikström [this message]
2020-06-07 11:47       ` Russell Adams
2020-06-07 12:01         ` tomas
2020-06-06 14:01   ` stardiviner
2020-06-09 13:08     ` Neil Cherry
     [not found]       ` <M9PnDEh--3-2@tutanota.com>
2020-06-09 20:45         ` FWD: " stanislaw_lem--- via General discussions about Org-mode.
2020-09-05  7:49   ` Bastien

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=HE1PR0201MB23468C856DC6002756D3B7EDDA870@HE1PR0201MB2346.eurprd02.prod.outlook.com \
    --to=gustav@whil.se \
    --cc=RLAdams@AdamsInfoServ.Com \
    --cc=emacs-orgmode@gnu.org \
    --cc=stanislaw_lem@tutanota.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).