Kevin Lawler

``` +/!1e6 /over, optimized to run using clean C loop via dispatch table 1.321s //-O0, before 0.280s //-O3, before 0.015s //-O0, after 0.015s //-O3, after ``` A better than 10x...

``` +\!1e6 /scan, optimized to run using clean C loop via dispatch table 1.454s //-O0, before 0.354s //-O3, before 0.016s //-O0, after 0.014s //-O3, after ``` Scan with Kx's Q:...

@wisefool769 https://github.com/kevinlawler/kerf1

Build things, tell people about what you build. You can contact me at [email protected] or post here and I'll help you. From another email I sent when asked about building...

seems fixed for me

this is the basic fix. if you were integrating it in the production plugin you'd do a few things better. nmap :call wrapped_smooth_scroll_page('u',1,4) nmap :call wrapped_smooth_scroll_page('d',1,4) nmap :call wrapped_smooth_scroll_page('u',0,4) nmap...

I think it meant add those functions to the C API. It looks like `ksk` made it (maybe?). The function `sfn` seems not to have. https://github.com/kevinlawler/kona/blob/master/src/kapi.c#L35

`7:` is fine to me. Implementor can pick.

Whoever runs with this can dictate the sort order. There are certain natural attributes that should be respected (e.g. the verbs have a particular sort order in memory, {} should...

They're the same thing, as far as I can remember. Thinking about it I can't see a good situation where you'd want to do that. We don't have to duplicate...