Calling sed(1) a programming language is quite a stretch (although I guess you could say it's Turing-complete), as is calling a core Unix tool “fringe”.
Maybe we need a tongue-in-cheek emoji to mark submissions like this. Or would that ruin half the fun?
> At the top, we have a not strictly POSIX compliant, multi-argument shebang:
#!/usr/bin/env gsed -nE -f
> It may break on some fringe UNIX implementations, but it is necessary for the system to work.
I think I can vaguely remember that I had issues with something like this on a bog-standard linux. env has the -S option though, which should help on systems where multi-argument shebangs don't work.
As someone who only used sed for quick pipeline editing, I'm curious of what constitutes a "sed project" that this tool aims to build. Does anyone have examples?
11 comments
[ 2.6 ms ] story [ 44.1 ms ] threadMaybe we need a tongue-in-cheek emoji to mark submissions like this. Or would that ruin half the fun?
I think my brain is still in holiday mode haha
I think I can vaguely remember that I had issues with something like this on a bog-standard linux. env has the -S option though, which should help on systems where multi-argument shebangs don't work.