Gregory Anders

> This may not be a good idea. For default autocommands their augroups have a common `nvim_` prefix. For mappings there is a proposal for namespaced mappings. If namespaced mappings...

>the preferred convention for bufnr/winnr/etc is: > >* nil means "all" >* 0 means "current" Which means we really shouldn't need these "resolve" helper functions at all, since most (all?)...

The original justification for this suggestion was that it was awkward or difficult to use `` on some keyboards, though that appears to not actually be the case? (cc @dundargoc)....

Can we remove libtermkey while we’re at it?

Differences between POSIX platforms and Windows have bitten us many times in `normalize` and other `vim.fs` functions. Does `.` and `..` have any meaning on Windows? AFAIK it's a POSIX...

OSC 52 is gated behind a query to the terminal that it is supported. So it should not be enabled by default unless your terminal supports it. What terminal are...

We should have a way to opt out of OSC 52. Even if the XTGETTCAP query determines that the terminal supports it, the user may have disabled it (and I...

> How about aligning it with other builtin plugins and use the `vim.g.loaded_osc52` method? (Just like `let g:loaded_netrw=1 `) Just a random idea ;) For newer builtin plugins we’ve not...

> @gpanders I hate to ask but may I ask if there's any progress here? Repeating what @clason said, the quickest way to get this change in would be to...

>I do not want to contribute to neovim anymore because unfortunately I got the worst treatment by the core devs multiple times and I'm sick of it. I'm sorry to...