memreflect

It works for me as expected, and there is no difference whether I use `'*'.*` or `[*].*`. Here is what happens for me: 1. `*.[mM][Kk][vV]` expands to `hello.mkv`. 2. `hello.mkv`...

I like the buffered command input and the write to the history file even when an error occurs. I also am grateful that you did not enable timestamps. There are...

> Do you have any comments on the PR as written? I initially lamented the change from an always-open file descriptor to repeated opening and closing of a file by...

I like the idea of replacing the forkexec() calls in eval() with `%run` invocations. If the result is non-zero from `$&run`, a custom `%run` hook might throw an exception, differentiating...

That paragraph contradicts the TAP Philosophy: * Ignore any unparsable lines Do you want a consumer to rigorously adhere to the TAP spec, or do you want them to follow...

Regarding your last suggestion, i would expect anything inside an exception handler that results in a false value to throw another exception when `-e` is in use. This would be...

I found a couple of lines that i would personally change, but it certainly seems to work well after trying it out with my own sample tests. That's some really...

* You used strings in tests/embedded-eq.es and a few other places; why not `{blocks}` instead? * The `report` function could be a tiny bit DRYer: ``` fn report { if...

> I just upgraded to 14.0-STABLE and I'm getting the same issue, just endless wrappers spawning. If I run with --force-wrapper it seems to run the Makefile and exit, but...

The issue is caused by gcndup() expecting a null-terminated string of length `n` or greater, yet sealcountedbuffer() invoked by `$&read` instead provides the number of bytes stored in the Buffer,...