@supakeen found a spelling mistake at the end of the first para
seriously, open up a device and changes are relatively large that you’ll find one
s/changes/chances
HN user
@supakeen found a spelling mistake at the end of the first para
seriously, open up a device and changes are relatively large that you’ll find one
s/changes/chances
there is a code2vec as well
its actually 250 for both, 130 for just the leader
claude one-shot it, then open source it, and build from there
from a few days ago: https://news.ycombinator.com/item?id=42706637
Interesting approach. Have you tried using existing clustering algorithms to determine the chunks instead of using distance or slope as a measure?
What did you use to create the chunks?
not sure why this just doesn't work now
markdown-composer passes a uri to the program. [1]
You can see the uri by setting `g:markdown_composer_browser = 'notify-send'`
inlyne expects a file so `inlyne http://127.0.0.1:44205/` fails
[1] https://github.com/euclio/vim-markdown-composer/blob/master/...