What is the point of Stackoverflow? It is full of clues retards with severe platform fanticism. They can't answer any question beyond "how do I add 2+2". Usually they just close harder questions, because they are too stupid to even understand the it. Here I asked a brain dead question about Unix sed behavior, expecting some people actually familiar with Unix to give a clue: https://superuser.com/questions/1525958/sed-pollutes-output-with-cr
They didn't even got what it is about. I.e. they don't know there are several different sed versions, believing that the broken gnu crap is the light and the way.
Name:
Anonymous2020-02-17 15:36
And going back to 2+2, they will likely give the wrong answer, or the reasoning behind the answer will be incorrect.
Name:
Anonymous2020-02-17 16:20
Useless pajeets. Admit your role, streetshiters.
Name:
!L33tUKZj5I2020-02-18 2:37
bug only happens on OSX
Maybe you should try a heterosexual operating system
>>5 sed : The term 'sed' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + `sed --version` + ~~~~ + CategoryInfo : ObjectNotFound: (sed:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
Name:
Anonymous2020-02-18 16:44
>>6 Slightly surprised that powershell doesn't include sed, given all the aliased posix commands it comes with.
Name:
Anonymous2020-02-18 21:10
>>5 $ sed --version sed: illegal option -- - usage: sed script [-Ealn] [-i extension] [file ...] sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...] $
Name:
!L33tUKZj5I2020-02-19 1:26
If you want posix on Windows, use Cygwin. The sed and awk on it have worked since 1995