Sed "invalid command code ."
tabacitu opened this issue · 3 comments
I tried the script, like it A LOT, had one small issue with the BackupManager and LogManager install and said I’d get back to debug it and… that never happened 😅 Maybe you can provide some insight:
This is super weird because yes I do have sed installed:
And the command itself looks… fine! But yeah this sed command errors for me, even when run separately in the terminal:
Any idea why? Never used sed 🤷♂️
Cheers!
PS. Mac OS 11.3.1 (Big Sur) on Apple M1. iTerm & oh-my-zsh
Well... let me make this even more difficult to debug... 😅
Ran it a second time, same machine, but this time I ran the one installed with homebrew. And now... it works... 😅🥳🤷♂️ Look what I have:
And the command-line output was so nice, it really looked like it knew what it was doing 😅
Excellent work @shinokada !
When you use Homebrew, Homebrew installs dependencies gsed
which is GNU sed. macOS ships FreeBSD sed and has fewer functionalities.
That's why when you install it with Homebrew it works.
In the requirements, you can find gsed
listed.
I will add the details to the README file.
P.S.
Since you used Homebrew installation, you have gsed
now, so you should be able to install it using the first method you did.
Thank you for trying it out.
Close this for now.
Let me know if you want to reopen.