feat: add_visual_selection_inline should support non-file buffer - #442
Conversation
phanen
commented
Jul 3, 2026
```
opts.keymap.output_window = {
['r'] = { 'add_visual_selection_inline', mode = { 'v' } },
}
```
5f2c4de to
3aa07d1
Compare
|
This is a nice adition, and a workflow I dind't know I needed :) Thanks again for another great little PR |
|
Sorry to jump in here. I was browsing recent PRs and was pleasantly surprised by this one. The profiling trick from #450 was also a very useful thing to learn. This PR made me rethink #318 a bit. Maybe the diff-review workflow I was imagining there was too heavy. What I actually want most of the time is simpler: while looking at any interesting part of Neovim — a code selection, a diff hunk, an opencode output block, a plan, or any temporary buffer — I want to select it, send it into the opencode input, and add a comment around it. From that angle, I’m not sure whether
One related question: do you use Maybe a small “one-shot selection / quote selection into input” mechanism would cover most of the use case from #318 without needing a dedicated diffview workflow. @phanen |
tbh I never use |
|
For my part I do use |
Ah, you probably use it more frequently than I do, so do you think the way it's being constantly cited is reasonable? I'm a bit unsure. |
|
They should be cleared once sent, If they are not it's a bug. |
…o-tee#442) ``` opts.keymap.output_window = { ['r'] = { 'add_visual_selection_inline', mode = { 'v' } }, } ```