I'm not sure this is the best solution. My idea was just to have additional triggers, it won't catch everything, but the main one is just diagnostics which we can special case for now.

Maybe for the general case we can define a user autocmd which can be called?

My idea was just to have additional triggers, it won't catch everything, but the main one is just diagnostics which we can special case for now.

Hm, I think we can support special case for Diagnostic. We can add force_update in render.open function. And set this flag in true only for DiagnosticChanged event. Also, it will be necessary to change throttling to support force_update.

Maybe for the general case we can define a user autocmd which can be called?

Are you suggesting providing an API that allows users to manually trigger a context update?

Are you suggesting providing an API that allows users to manually trigger a context update?

Potentially. Need to know the use cases first.

@lewis6991 Since this plugin no longer concat multi-line contexts, how about open a window directly with the parent buffer, so lsp semantic highlight, virtual-text, etc. stay consistent and can also reduce the code required to query ts-highligts.

You'd need to open several windows so this would be more complicated.

Context already copies all the semantic tokens and extmarks.

Potentially. Need to know the use cases first.

I think manually trigger context in Telescope previewer is very cool and useful, combined with TelescopePreviewLoaded autocmd