Matt writes:
> On Sat, 13 Jan 2024 19:00:16 +0100 Ihor Radchenko wrote ---
>
> > Since posh is POSIX-compliant, generic PS1/PS2 variables should work, and
> we
> > do not need a special entry in `org-babel-shell-set-prompt-commands' -
> > we can remove "posh" record from there.
>
On Sat, 13 Jan 2024 19:00:16 +0100 Ihor Radchenko wrote ---
> Since posh is POSIX-compliant, generic PS1/PS2 variables should work, and we
> do not need a special entry in `org-babel-shell-set-prompt-commands' -
> we can remove "posh" record from there.
>
> I'd rather keep the
Matt writes:
> There was discussion about different shells, Eric asked for others, "posh"
> was mentioned as "specially for POSIX compatibility checks", and then a
> "posh" was added to ob-shell.el by Eric (fb09863f).
>
On Thu, 11 Jan 2024 21:30:59 +0100 Matt wrote ---
> The change on August 26, 2022 should have caused a breaking error for
> someone using the "Policy-compliant Ordinary SHell." The prompt for "posh"
> in "org-babel-shell-set-prompt-commands" is valid PowerShell syntax (AFAIKT)
On Fri, 12 Jan 2024 11:04:33 +0100 Morgan Willcock wrote ---
> As I understand it, the code for the cmd.exe shell is not released
> anywhere.
Ah, okay. I clearly didn't search too hard for it.
> That said, I imagine Wine does contain its own implementation of
> cmd.exe, although
Matt writes:
> AFAIKT, both PowerShell and cmd are MIT licensed:
> - https://github.com/microsoft/terminal
> - https://github.com/PowerShell/PowerShell
>
> The thought of compiling either for a GNU system is...ugh. But maybe someone
> else has gotten them working? Otherwise, it looks like
Hi,
I would like people's thoughts on removing the "posh" language header.
ob-shell.el supports a "posh" shell. What is "posh?"
* Posh is not PowerShell
"posh" was added to =ob-shell= in fb09863f with no commit message on December
13, 2013 (Friday the 13th!).
