5 ms·
Very cool. For those of you who know sed well, can you actually read the source of this program and understand it, or does it look like garblygook?
by snazz 8y ago
Very cool. For those of you who know sed well, can you actually read the source of this program and understand it, or does it look like garblygook?
- jniedrauer 8y agoIt doesn't look that complicated compared to normal sed usage. It's just a series of find/replace for the most part. That said, regex is always pretty hard to read, and putting it together like this is impressive to say the least.
- cmiller1 8y agoIt's pretty nicely put together and commented, still trying to work through exactly how the interleave steps work though.
- davidten 8y agoI’m one of the organizers of Hack N Roll and personally know the guy who built this. He says that the code on Github is actually broken but he forgot in what way.. I still think it’s pretty cool though
- saevarom 8y agoI tried running this on a Mac but got an error. Assumed it was because of some sed version difference. Perhaps the code on Github is just broken.
- kritixilithos 8y agoThat's probably because you used BSD sed. Running it on my BSD sed also gives an error, presumably because it thinks the `}` is a part of the label in `binput}`. However it works fine in GNU sed, and now that you mention it, GNU sed's extensions were not used, like the `-z` flag to slurp all input in one "line" to avoid `:input;$!{N;binput}`.
- bjoko 8y agoOn macOS: install gnu-sed via Homebrew.
- NeccoNeko 8y agoIt works with the GNU sed that ships with GitBash on Windows.
- ashelmire 8y agoYou know how artists will use a bunch of plates (or other objects) to make a giant version of the Mona Lisa or something like that to make a photographic mosaic? It's like that. Each line makes sense, but you've got to have some real vision to make this happen, and it's really difficult (nearly impossible) to see the big picture by just looking at a small part.