Lichen: The Sed Build System
github.com
Lichen: The Sed Build System
1–10 of 12 posts
Re: Lichen: The Sed Build System
#2Can't sleep, must publish build systems for more fringe programming languages.
Re: Lichen: The Sed Build System
#3Read that as “Lichen: the sea’s build system” and was expecting a comparison of lichen (a kind of moss) to makefiles.
I think my brain is still in holiday mode haha
Re: Lichen: The Sed Build System
#4> At the top, we have a not strictly POSIX compliant, multi-argument shebang:
#!/usr/bin/env gsed -nE -f
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.
Re: Lichen: The Sed Build System
#5> 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.
Hm, yeah, I've been using
#!/usr/bin/env -S ansible-playbook --diff
Re: Lichen: The Sed Build System
#6As 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?
Re: Lichen: The Sed Build System
#7As 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?
Most likely the kind of project that uses lookup tables to synthesize a decimal alu, per https://sed.sourceforge.io/grabbag/tutorials/lookup_table_co... ;-)
Re: Lichen: The Sed Build System
#8> 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.
Hm, yeah, I've been using #!/usr/bin/env -S ansible-playbook --diff to turn ansible playbooks to scripts, but reading https://www.man7.org/linux/man-pages/man1/env.1p.html it looks like -S isn't actually POSIX-specified.
-S is available from macOS env, which is good enough in my book! Unfortunately macOS sed and gsed differences are a huge pain in the ass
Re: Lichen: The Sed Build System
#9> 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.
[deleted]
Re: Lichen: The Sed Build System
#10Can't sleep, must publish build systems for more fringe programming languages.
Brainfuck anyone?