> > we already have a quite good solution. > > Maybe its not evident due to all the discussion, but to be clear, to me it isn't a good solution at all.
Still after @techee's explanation above? I'm not convinced that insisting on mimicking the VSCode behavior might lead to delay this issue for some years although we already have a working solution. Yes, not the one you prefer but as said before, this is rather an edge case and putting so much efforts on it with all our limited spare time might not be worth it.