Since people are curious Ill explain why:

I need to build our project from the remote repo using a PowerShell script (.ps1). I’m using Bash in the VSCode terminal, I have to run the .ps1 script in a new Command Prompt because the compilation takes around 5 minutes and I need my terminal for other things. To do this, the only way is to run a batch file that executes the .ps1 script.

Its an automation so I dont need to touch powershell whatsover and remain in bash terminal. Instead of opening several windows, I automated all so it only takes 1 alias to compile my shit.

The compilation also requires several inputs and “Key Presses”, so I automated all of that in the Batch file.

  • ArchAengelus@lemmy.dbzer0.com
    cake
    link
    fedilink
    arrow-up
    44
    ·
    7 months ago

    Please explain why you don’t open powershell and run cmd.exe instead of running bash? This is a strange workaround and doesn’t really make sense.

      • wizardbeard@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        15
        ·
        7 months ago

        Why not just open another terminal in VSCode?

        You can open as many as you want, and as many types as you want. Bash, PowerShell, Command Prompt… there’s zero need to chain multiple just to keep your main one free.