You're describing VS Code. Now you may not think it's lightweight, but for anyone not toiling away on a turn of the century machine it's plenty fast and has great debugging facilities.
Do you mean if you select (preview) a file from the tree browser on the left, the file appears, but if you select another one, it goes away ?
Use this setting/preferrence:
"workbench.editor.enablePreviewFromQuickOpen": false,
I've never used vscode, but this makes me wonder how small a file has to be for vscode to manipulate it quickly.
The link to this SO question was purple when I Googled this just now: http://stackoverflow.com/questions/908575/how-to-edit-multi-...
In retrospect, I do remember also messing around with disabling syntax highlighting and splitting the file up into more manageable chunks that I loaded into separate buffers.
For my purposes, I was trying to delete certain portions of the dump - so vim was the perfect tool to do something like "delete everything from line 850 to the next time this regex is matched", with a minimum of scrolling around and rendering things unnecessarily. iirc, Sublime just locked up and refused to scroll.
I wonder if I could have used Vintage to do what I wanted in Sublime?
You "can" open one-off files from the command line. It's just way slower than other methods if you're just doing a quick change, and you'd go mad waiting for the file to open.
I never experienced this, which type of files ?
Now if only I can get it to stop automatically closing quotes during comments and ruining my english contractions:
// it' => // it''
Any way around that? :(
Unfortunately, that also turns off all bracket matching.
I'll take having to remember what I'm trying to type, look it up etc, and have autocomplete mostly work, vs. my editor wigging out in a large project for a really small change.
Also, absolutely love the integrated terminal and the git integration, though better merge/rebase would be nice.