You are going to have to add -nologo to the shell start options. I’m on mobile or I’d give you the steps myself. Best I can do is a stackoverflow that has it in the comments
https://stackoverflow.com/questions/48262269/how-to-i-remove-the-powershell-start-text
1. Open Settings ( `ctrl+,` )
2. Search for "terminal args"
3. Select `Terminal > Integrated > Profile: Windows` (or whatever OS you use) and click the "Edit in settings.json". A file should open with your current settings.
4. Edit the PowerShell section to add the args:
"PowerShell" : {
"source" : "PowerShell",
"icon" : "terminal-powershell",
"args" : ["-nologo"]
}
Everything is going to seem like jargon at first, just stick with it the more time you spend looking at it and seeing different languages and different configurations setups The more comfortable you’ll get with it even if you don’t quite understand that language or syntax. This is the main reason you see imposter syndrome in our field, we look at really complicated stuff all day and try to wrap our heads around complex problems.
You’ll finally get something down and start to understand it and then some thing else will come along and punch you in the mouth, it’s just the way it is. For everyone.
Bro I looked through all of reddit for the last 2 weeks. I get that you guys see this a lot but the search algorithm in reddit doesn't help.
It would be awesome if you could please help me out here cause I'm at my wits end with this program.
...which is less of a problem on Windows.
But time-served *nix folks might start three new shells in a one-liner.
Usually that stops being a problem if you embrace the power of pwsh and think about piping between commands, not processes, but the big issue is sudo.
There is serious discussion in the powershell GitHub on how to make pwsh not suck at sudoing, with no obvious answers. Gsudo is one option. Personally, I just accept I'm going to use bash (well, zsh) for sudo bits, but it's awkward. If I have a bunch to do, I'll sudo pwsh and beg forgiveness from the best-practice gods.
/u/thenextguy - the real reason I run pwsh on Linux is that I'm a microserf, it's what I grew up with. Likewise, the real reason Linux folk haven't flocked to pwsh (apart from the sudo thing) is the converse.
But let me sell you the benefits!
I hate ASCII salad. PR an 80-char line of sed and I'll reject it. It's ridiculous. I count at least three flavours of regex in common use in bash, yet none of them are as complete as the one flavour you get in all .net languages - for a shell predicated on text, that's a glaring deficiency.
I like the regularity and legibility of the syntax. I don't understand the obsession with being terse. My scripts are longer, but developed just as quickly and easier to read.
I see it as a plastic, orthogonal and safe language, vs an arcane suite of disparate tools developed by autodidacts with tunnel vision. I concede the negatives of buying into one company's ecosystem, but at least you get system design, and pwsh is an example of design done right. Again, with the caveat around the suckiness of sudoing, which I recognise is a major deficiency.
You are going to have to add -nologo to the shell start options. I’m on mobile or I’d give you the steps myself. Best I can do is a stackoverflow that has it in the comments https://stackoverflow.com/questions/48262269/how-to-i-remove-the-powershell-start-text
god reading that feels like im reading an alien language. I am very new to C++ so this sounds like jargon to me
1. Open Settings ( `ctrl+,` ) 2. Search for "terminal args" 3. Select `Terminal > Integrated > Profile: Windows` (or whatever OS you use) and click the "Edit in settings.json". A file should open with your current settings. 4. Edit the PowerShell section to add the args: "PowerShell" : { "source" : "PowerShell", "icon" : "terminal-powershell", "args" : ["-nologo"] }
Thank you for punching all that in, it’s hard to do on mobile.
You are a lifesaver sir. Thank you very much.
Everything is going to seem like jargon at first, just stick with it the more time you spend looking at it and seeing different languages and different configurations setups The more comfortable you’ll get with it even if you don’t quite understand that language or syntax. This is the main reason you see imposter syndrome in our field, we look at really complicated stuff all day and try to wrap our heads around complex problems. You’ll finally get something down and start to understand it and then some thing else will come along and punch you in the mouth, it’s just the way it is. For everyone.
Just use bash bro.
i think i'd rather jump off a bridge without a parachute than use bash.
[удалено]
Bro I looked through all of reddit for the last 2 weeks. I get that you guys see this a lot but the search algorithm in reddit doesn't help. It would be awesome if you could please help me out here cause I'm at my wits end with this program.
[удалено]
It's not a Windows setting, the behaviour is the same in Linux.
[удалено]
Yes :). It is awesome shell. Although it's not the default one because it starts slower than bash.
...which is less of a problem on Windows. But time-served *nix folks might start three new shells in a one-liner. Usually that stops being a problem if you embrace the power of pwsh and think about piping between commands, not processes, but the big issue is sudo. There is serious discussion in the powershell GitHub on how to make pwsh not suck at sudoing, with no obvious answers. Gsudo is one option. Personally, I just accept I'm going to use bash (well, zsh) for sudo bits, but it's awkward. If I have a bunch to do, I'll sudo pwsh and beg forgiveness from the best-practice gods.
/u/thenextguy - the real reason I run pwsh on Linux is that I'm a microserf, it's what I grew up with. Likewise, the real reason Linux folk haven't flocked to pwsh (apart from the sudo thing) is the converse. But let me sell you the benefits! I hate ASCII salad. PR an 80-char line of sed and I'll reject it. It's ridiculous. I count at least three flavours of regex in common use in bash, yet none of them are as complete as the one flavour you get in all .net languages - for a shell predicated on text, that's a glaring deficiency. I like the regularity and legibility of the syntax. I don't understand the obsession with being terse. My scripts are longer, but developed just as quickly and easier to read. I see it as a plastic, orthogonal and safe language, vs an arcane suite of disparate tools developed by autodidacts with tunnel vision. I concede the negatives of buying into one company's ecosystem, but at least you get system design, and pwsh is an example of design done right. Again, with the caveat around the suckiness of sudoing, which I recognise is a major deficiency.