Tv

9e8e65293a037ce998ba0df102710c49313aa513 should help here. Leaving this pull open until I've actually had time to experiment on whether it's useful even after the decreased gc churn.

I'm very much open to doing something better with logging, probably along the lines of https://github.com/codahale/lunk but I'm not quite sure what your motivation here is. You do realize you...

Thank you. That's enough information that I think you'd be served well enough by having a trace ID in the messages and a good built-in "end processing" message, and that's...

I'd love to have an interface that's sufficient for lunk but not tied to it.

Definitely something more explicit than `interface{}`. I can't tell at this moment whether the proposed change is otherwise enough to support lunk. Rest assured this is within my own interests,...

`register_bin` / `register_bins` now exists. It, however, doesn't cover things quite well enough: I'm trying to write a testable README for a command that processes files. I'd love to have...

Since I really miss cram, I'm very tempted to make a PR that adds a "shell mode" where all command lines that don't look like binaries or environment variable setting...

I've read through the trycmd code base and done an experimental spike on the code changes needed. I feel like supporting "real shell" scripts properly is too much at odds...

This can also trigger after the watch: ``` [Routify] meta data changed [Routify] ✖ Failed to generate route files [Error: ENOENT: no such file or directory, stat '/blah/src/pages/blah/.#blah.svelte'] { errno:...

@Wolfr I'd argue it's more "respect the ignore pattern configured, everywhere". Changing the default value for the ignore pattern may also be worthwhile. But what I do *not* mean is...