xiyaowong

Results 258 comments of xiyaowong

Can't reproduce ![a](https://github.com/vscode-neovim/vscode-neovim/assets/47070852/0e838cfc-d28e-4834-a36c-f9d0c5db090d)

If this issue still exists, please let me know, and I'll reopen this issue.

@ian-h-chamberlain Is this issue still present? If it is, please try adding the following code to the setup function https://github.com/vscode-neovim/vscode-neovim/blob/c5b72fbd4c40900b38295f07c9e5489e7b39b3f9/runtime/lua/vscode-neovim/highlight.lua#L164 ```lua setup_globals() setup_syntax_overrides() setup_syntax_groups() ```

Most plugins have not been upgraded to eslint v9 yet. There are conflicts in peer dependencies. Furthermore, I recommend using [eslint-plugin-import-x](https://www.npmjs.com/package/eslint-plugin-import-x)

If it's just that the highlighting takes a while to appear, that's expected. Scrolling must be debounced, so it's an unavoidable phenomenon. https://github.com/vscode-neovim/vscode-neovim/blob/12e0d8b53708c28adc31a5c4083bfb40b44d0e33/src/viewport_manager.ts#L147

`set icm=nosplit` works, but sometimes the highlighing is wrong https://github.com/vscode-neovim/vscode-neovim/assets/47070852/48f659a9-a524-418e-918e-958fb487094d

> `set icm=nosplit` works, but sometimes the highlighing is wrong Hard to reproduce with #1976

Merged, this PR has no side effects

I originally used ThemeColor, but later found that the effect was not good https://github.com/vscode-neovim/vscode-neovim/blob/c81e64dd0f0502f79b14fe2430d7d442f347fd85/runtime/lua/vscode-neovim/highlight.lua#L58-L62

Sure. But now users can still set it in settings.json. If you want to add to this, that's fine with me.