A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
IIRC on mac sed -i behaves differently - The default is not GNU sed. I believe you can brew it to get the good one
sed -i
brew
Hi. I have never used any mac. Would you kindly provide details of sed -i behavior so I can update this article accordingly?
BSD sed expects -i to take a file extension so it can save a backup.
-i
Instead of using this:
sed -i YOUR_COMMANDS_HERE foo.txt
you can use something like the following, which will make a backup file and then immediately delete it if the command succeeded:
sed -i.bak YOUR_COMMANDS_HERE -- foo.txt && rm -- "foo.txt.bak"
That looks a little nasty, but it's portable; GNU sed's -i also takes a file extension as an optional argument.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
IIRC on mac
sed -i
behaves differently - The default is not GNU sed. I believe you canbrew
it to get the good oneHi. I have never used any mac. Would you kindly provide details of
sed -i
behavior so I can update this article accordingly?BSD sed expects
-i
to take a file extension so it can save a backup.Instead of using this:
you can use something like the following, which will make a backup file and then immediately delete it if the command succeeded:
That looks a little nasty, but it's portable; GNU sed's
-i
also takes a file extension as an optional argument.