I can probably be of some assistance here. I should do a write-up of exactly what API calls Parinfer needs in order to be implemented 100% in editors.

Incidentally, this would be the same write-up as "why VS Code does not support Parinfer Smart Mode"

These API calls would be really useful - we are already adding new API, meaning that we're already "our own thing", not limited by what Atom used to offer only 🙂

Thanks for the help!

Also, I remember seeing the write-up about VSCode, but unfortunately I'm not finding it - can you link it to me, so I can see if the same problems exist in Pulsar too?

Could someone link me that post as well? I too am curious (although I'm into neovim, but would love to know what's missing).

Hi @U3Y18N0UC, coming back to this, I think the third paragraph of the section you quoted from has the most details about what Smart Mode requires from an editor: https://github.com/parinfer/parinfer.js?tab=readme-ov-file#status-update-2019-smart-mode

Looking at this, it seems that the problem in Pulsar is copy/paste and buffer refreshes from changes on disk - these indeed are not implemented. If I'm not mistaken, it's possible to get every change from every cursor using the change callback; still, it might have some trouble in case of some "API text change" (which is something I am experimenting on a different plug-in I'm writing)

Also, this 3 version might be interesting for very big files that might add latency too