Chris Grieser

it would solve the issue for me, but having functions, nil, and line numbers feels like overcomplicating things to me. Is there any scenario not covered by "insert at line...

+1. Surprisingly, a simple "summarize current note" feature is actually something that none of the AI plugins I tried have.

oh nice, I didn't know about that one. Could it be that you are on nightly though? I am on 0.9.2, and trying `ia` as mode results in an error...

Update to using `keymap.set` as nvim 0.10 has been released. (Not using `vim.iter` to keep it simple for new users :) )

I have another case where the extraction is all wrong (e.g. all spaces missing), when it works with other PDF annotation extractors. You want me to add samples of PDFs...

seems to be a bit better, but not for all PDFs. will report when I tried it on more PDFs!

okay, apparently it's not the big rectangles, but certain pages with more complex images – even without an annotation? With further testing, it seems this page (from the same article)...

yeah, something like that would be one approach. (or rather `--markdown=suboption1,suboption2`, I guess?)

Also came here for this. I don't use a file tree plugin at all and installing one just for the LSP renaming operation feels a bit bad

for the API, something like these seems fine to me? ```lua require('lsp-file-operations').rename({ old_name = "foo", new_name = "bar"}) ``` edit: `old_name` should be optional, defaulting to the current file