ELLIOTTCABLE

A big :+1: here — although personally, I much prefer the behaviour of “look like the ASCII characters concatenated and beautifully kerned”, as opposed to “transform to a perhaps-more-semantic, but-less-pragmatic,...

Yeah, tabs is a :+1: here! I don't think it needs complicated support for framework-per-tab or whatnot, personally — just duplicate the browser behaviour: * **⌘-T** to create a new...

@Spy-Seth but ”tabs” do not “another internet browser” make! It's one, relatively small, usability feature — that browsers *also* happen to have. We're not asking for a Firefox-esque tab tree!...

This one is super-important to my workflow. For large, complex PRs, viewing changes "intermingled" is a nightmare — as long as your collaborators are disciplined, it's much easier to view...

Yeah — a lot of VScode features aren't possible unless the buffers exist 'on-disk.' Such virtual files don't have LSP support from most LSPs, etceteras. These LSP features work in...

Ah, my OP may have been unclear: the comment (on the right side) is, indeed, in the right place. However, the existence of the comment on the right side necessitates...

This is definitely still relevant in v6; and in fact, since my OP, this is now _worse_ for me, as I'm in the same situation as @denibertovic — I've got...

@jakehl Personally, I prefer declarative formats (see [Dhall](https://dhall-lang.org/)'s homepage and documentation for some good arguments there), but I wouldn't mind seeing your work published. Sounds like it'd be useful in...

Two related requests, one tiny and related to these builds, and one that could easily be included in the primary build: 1. when hovering in the menubar, these builds all...

This is surprisingly complex. Maybe we need a table of the ("project"-related setting location + checked-in status of that location) against the (whether that setting should be persisted when creating...