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.
This is a common issue in software, not limited to scripting. Software are getting more and more layers of wrappers/adapter code, like a Russian doll. It contributes to dependency hell, as each layer brings new dependencies.
Developers often find it easier to wrap existing apps and software, and add another layer on top, rather than improving or replacing what exists.
That sounds like you don’t know what you’re going. No offense.
Fuck man, I don’t know what I’m going either.
Damn autocorrect…
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 a few minutes. To do this, the only way is to run a batch file that executes the .ps1 script. Du verstehst?
Ich verstehe. Ich würde aber auch einfach nicht Fenster benutzen lül
lach
I have to run the .ps1 script in a new Command Prompt because the compilation takes a few minutes
I don’t follow this reasoning. Is it because you don’t want to take over the VSCode terminal with a long command? Couldn’t you can open multiple tabs, or run in the background, or use screen/tmux, etc.?
Yeah I use my terminal to run other things, as it stays compiling for around 5-6 min. I could open another tab like you mention but Instead I automated all so it only takes 1 alias (ex cc) to compile my shit.
The compilation also requires several inputs and “Key Presses”, so I automated all of that in the Batch file.
All of those inputs would likely be much better built into the ps1 file. PowerShell is meant as a sucessor to vbscript which was meant as a successor to windows batch.
Selecting options? Make them parameters that you just set when calling the script: ./build.ps1 -Arch 64 -CompressSplines
Needing someone to manually confirm something completed? Add a while loop to wait 5 seconds while whatever spawned process is still running.
Etc.
Also, you can have multiple terminals open in VSCode.
You’ve not listed any requirements that aren’t more easily solved with existing features in the tools you’ve listed. Learn the tools your work expects you to use before you start blaming them for shit.
Or… His hacked system is working, let’s not duck with it. 🤣
That’s absolutely acceptable. Don’t fix what ain’t broke.
But please don’t publicly post a joke/rant about how your only option to accomplish something was through absurd hacky workarounds, when the issue is that you refused to learn the tools you have.
What we have here is the slightly more tech literate version of printing out a Word Doc so you can re-arrange, remove, and add pages physically before scanning it back in as a PDF to email someone, then complaining about it being so difficult, rather than just using one of the many many print to PDF and PDF editing/splicing tools.
That doesn’t make any sense. Why not just use PowerShell directly then? Why use Bash or even command line and a batch file? It sounds to me like you’re over-complicating things for nothing and putting the blame on Microsoft for some reason.
I’m a heavy Bash user myself and often find myself struggling a bit with PowerShell trying to look for equivalent commands. (commandlets?) But, the more I use it, the more I understand how it works and the more I improve my skills at using it.
I know a lot of people like to shit on Microsoft, but seriously give their PowerShell a chance. It has its strengths. It’s especially nice with Oh My Posh running in Windows Terminal.
Since you added a question mark, commands is the correct general term. However there are two types that can be a command. Functions: which are written in pure powershell and cmdlets: which are commands provided by dotnet classes. (Also exes and a bunch of other stuff common to other shells can be a command, but that’s not important.)
The reason they have different names is early on functions didn’t support some of the features available to cmdlets, such as pipeline input. There was later a way to add this support to functions.
In practice call them any of the 3 and people will know that you mean.
The oola hoops I have to do to optimize my workflow at work is simply legendary, I fkn hate windows.
The hula hoops are of your own choice/design, I’m sorry to say.
It sounds like your hate in this instance is misplaced, because “someone” set things up in that stupid way.
You work a job that uses PowerShell and you refuse to learn or use it. You are creating problems for yourself.
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.
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 a few minutes. 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. Instead of opening several windows, I automated all so it only takes one alias.
Why not just launch it directly but background the process so it doesn’t hang up your terminal?
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.
I feel your pain
Therapist: Young Willem Dafoe isn’t real, he can’t hurt you.
Young Willem Dafoe:
U can probably add a couple more layers by sshing into a vm
Got to at least wrap it up in some python.
Good idea perhaps we can route over tor as well just to maximise latency
Don’t forget to run some docker container on that VM, to encapsulate the workload, so it will be: SSH to VM -> open a shell into the container -> run the rest
I use Cygwin in my build system so I don’t have to rewrite commands for different systems.
Command prompt is CMD and batch script, Powershell is Pwsh and .ps1, then bash is .sh.
You’ve confused a few things here…
FYI, open a powershell terminal separately, to the path of your script (powershell in file Explorer path) and run your script.
Do rest of Work in Vscode
Done.
I use Ansible on WSL to run Powershell scripts on Windows using VSCode. I’m surprised it works as well as it does.
You use Linux to run Ansible to run ps1 on Windows, exactly how it’s meant to be used!
I just threw up while crying
My work someone made a robust automated build script, and they left so someone else made a wrapper around it to make it easier to work with, they’re gone now and someone wrote a wrapper around that to extend functionality in a backwards compatible way, but it’s overly complicated for my minimal use cases so I wrote a batch file to call it with my default settings…
pOwErShEll
How many of them are there in windows nowadays, cmd, pOwershell versions, shell if you use git, …
That pic of Willem Dafoe is patently false… no dong hanging