The Geek have been converted, hallelujah, pass the cmdlets. The Geek was a self-proclaimed expert at Windows Batch files. I could get them to sing, dance and tell jokes. The writing on the wall and Microsoft’s recent lapse in sanity have resulted in PowerShell is available on both Windows and Linux, image that. This means the Geek uses PowerShell whenever possible so that sometime soon I can get to the level where “I don’t suck at that anymore.”
The Geek also uses ASCIIDoctor for all of the technical document he generates. I can use Visual Studio Code with a bunch of plugins and rapidly create documentation, research notes, and general ramblings. ASCIIDocFX is an open-source, multi-platform, extensible editor for ASCIIDoctor files. For a long time, it was somewhat unstable and had a limited support and community. Recently I revisited it and it has recovered from whatever was ailing it.
ASCIIDocFX Terminal Mode
- So you click on the Terminal button on the bottom of the page
- The window opens, and it’s got the Windows Command Processor, in it, how sad.
ASCIIDocFX Setting Mode
How difficult can this be? Opps, I just recited the magical black spell on this whole thing.
- Click on Settings on the right sidebar
- Click on Terminal Settings
- Scroll down to the Terminal Starter (Windows) entry, there is the culprit cmd.exe.
Let’s change this to Powershell.exe
- I also like colors, so I changed my background color to blue and foreground color to yellow, this is my standard PowerShell colors.
- Then scroll down to the bottom of the page and click on the Save button.
Then I closed down ASCIIDocFX and reopened it. clicked on that
- Clicked on that Terminal button again.
- I’m still stuck in Windows command line hell, what the hell!
So with great confidence, I closed ASCIIDocFX and reopened, just in case.
- Then I mashed down on the Terminal button again
- I’m still sad but, now add frustratation to this.
So what do I do, the same thing we all do….
Test Powershell in ASCIIDocFX
All this gets me is more frustration, so I wonder “… Does ASCIIDocFX even know if Powershell exist?”
At the Windows Command Prompt I type Powershell, it works, that’s a good sign
When I do a simple test with a PowerShell cmdlet, at the PowerShell PS prompt I enter write-output “GeekMustHave Powershell”, that works, another good sign. I like good signs but, I’d like PowerShell even better.