This has helped resolve a few bugs, but has also generated more spam issues than I can keep up with. To be really useful it needs source maps, which are quite bulky.
If we want to revive something like this, we should use VS Code's relatively new telemetry API.
I'd like to put out a release for the undo regression, but it seems VS Code's updates have also broken some other stuff. Don't have time to resolve these now, so skip skip skip.
The issue is pretty clearly that a recent VS Code update caused `onDidChangeTextDocument` events to be created (unreliably, from my testing) in such a way that trips our "change from disk" logic. We respond to that situation rather pessimistically by throwing out our undo stack, rather than trying to do something clever.
I haven't had the time lately to dig into the nitty gritty details of what changed on VS Code's side, so this is a bit of a shot in the dark.
The "change from disk" logic has caused issues in the past and I'm not sure how to reliably make it work, so I'm just deleting it for now. This may cause problems in some edge cases, but judging by my dogfooding, that'll be much less disruptive than losing your undo stack frequently enough that you can't trust it.
- Map quickfix commands (`:c`...) to markers/problems panel
- Map location list commands (`:l`...) to comments panel
Caveats:
- `cnfile`/`cpfile` and `cn`/`cp` are identical,
the vscode commands either only navigate within the current file (editor.action.marker.next),
or through each marker for all files (editor.action.marker.nextInFiles).
- `lnext[f]`/`lprev[f]` doesn't navigate across files,
the vscode commands doesn't seem to support it.
- `cwindow` and `lwindow` do not close their respective panels if there
are no items in their list. This felt like a reasonable compromise to
avoid complicating the implementation.
- `cclose` and `lclose` close the primary panel, not specifically their
respective panel, since it's not possible.
Fixes#3158
