Rafał Chłodnicki
Rafał Chłodnicki
It was reported as https://github.com/sublimehq/sublime_text/issues/4870 before, fixed and then regressed again.
Actually that was slightly different case. I can't find anything more relevant now.
Is there any progress on this on the clangd side? I don't think we can do anything with this issue otherwise.
Yeah, it needs updating. Doing that relies on availability of maintainers (typically me in this case) which varies.
Released https://github.com/sublimelsp/LSP-rust-analyzer/releases/tag/v1.11.0 Should be available in a couple hours from now.
> While the API might be confusing, isn't > > > but closing the primary view will remove phantoms from the clone > > just an ordinary bug? I suppose...
Sorry, I was wrong about one detail. The phantoms don't go away on closing the primary view. ```py from sublime import LAYOUT_INLINE, Phantom, PhantomSet, Region import sublime_plugin phantoms = None...
I was wrong about being wrong. The phantoms might not go away after closing the primary view but they become "dead" instead - updating `PhantomSet` doesn't update the view anymore....
@kaste I think your indirection will also fail when the primary view is closed - the `PhantomSet` won't react to updates anymore.
Well, depends what one considers to be the issue here... One could argue that the fact that `PhantomSet` takes a `View` but makes phantoms also show up on clones (which...