4 ms·
I tried it recently and I know it's just alpha right now but something feels a little fundamentally annoying about the way it changes things in the editor while
by blinkingled 6y ago
I tried it recently and I know it's just alpha right now but something feels a little fundamentally annoying about the way it changes things in the editor while you're typing. One example is that it seems too eager to claim something is a syntax error before you've really finished really typing it.
- metalliqaz 6y agoWouldn't that be the text editor's fault?
- blinkingled 6y agoNot sure about that - doesn't seem to be a problem with any other extensions.
- k__ 6y agoAs long as it does this with single digit millisecond latency, I'd be okay with that.
- blinkingled 6y agoTrouble is it will eagerly try to auto complete the wrong thing while you are trying to fix up your typo.
- k__ 6y agoAh, I had this problem with all languages. Don't know how to get around this :/
- matklad 6y agoOut of curiosity, which editor are you using? I've hit a similar problem when trying out upcoming neovim lsp support: https://github.com/neovim/nvim-lsp/issues/195 https://github.com/neovim/nvim-lsp/issues/195
- blinkingled 6y agoVscode
- ImprobableTruth 6y agoReally? I've had the inverse problem where it only corrects anything once I've hit safe.
- thramp 6y agoI think this might be caused by autosave being enabled in VSCode, but this is just idle speculation.