[wruza]

I don’t mind slowdowns as long as they are synchronous and deterministic. But most IDEs and IDE-like plugins work asynchronously, so you have to wait and sync all the time. I think that this async-all approach gains technically but loses methodically, so I stick to basic editing. Ymmw.

What I would like to try is an asynchronous non-inplace helper. Like a side panel or a bg overlay to the right-ish that understands what you’re doing and suggests identifiers, reference snippets, full type info, etc. Like the whole page in a smaller font dedicated to what’s under the cursor. Then you could choose what to type into the code, or ignore it because I already know that. I don’t mind typing if it doesn’t require too much attention.

Another thing I’d like to try is mobile-style typing suggestions. First - semi-transparent popups above words in case there’s a typo or an obvious continuation, applied via M-CR. Second - 3-5 most obvious next tokens to insert without even starting to type. Like in

  let start = new Date
  let date|

Suggests [“=“]. When you choose it, it suggests [“new”, “start”, “Date”, “undefined”]. I bet one could type pages with this alone.

This might work nicely with any editing model, imo.

[VoidWhisperer]

The last suggestion seems somewhat similar to what copilot does, although copilot tends to suggest whole statements instead of a word

[riffraff]

I wish copilot.vim had a way to insert only a token from the suggestion. I often get stuff which is partly correct but "diverges".

[pynappo]

there is a somewhat hacky way to accept just a word, to my understanding, since copilot.vim allows you to access the raw text that's being suggested. try out the snippet in the linked comment:

https://github.com/orgs/community/discussions/12426#discussi...

[wruza]

It’s a similar job, but a different value. Copilot writes code you don’t know yet (supposedly), while this speeds up typing what you know you’d like to type. Both modes could be useful, I think.