Christian Clason

No. Features are not backported to release branches, so this will only be in 0.7.0.

Update: `filetype.lua` is now the default on Neovim master (and 0.8.0, when that is released). It has full parity with `filetype.vim` (including `scripts.vim` and `setf FALLBACK` support), passing Vim's filetype...

Not Windows, `Window`: Here's my local build failure. ``` error[E0432]: unresolved imports `crate::event::KeyboardInput`, `crate::event::VirtualKeyCode` --> /Users/clason/.cargo/git/checkouts/winit-58efae9df3f5264a/6f91c74/src/platform_impl/macos/event.rs:10:34 | 10 | event::{ElementState, Event, KeyboardInput, ModifiersState, VirtualKeyCode, WindowEvent}, | ^^^^^^^^^^^^^ ^^^^^^^^^^^^^^ no `VirtualKeyCode`...

I've made my thoughts known elsewhere, but briefly I am _strongly_ in favor of a dedicated config file -- I don't see a reason for shoehorning configuration for one program...

For the sake of completeness: I was only considering one-time setup options and not runtime changes (which I don't see a lot of use for, to be honest); for the...

> But then there are two config files (nvim config and neovide config). Yes, that is exactly what I am suggesting. I don't consider this bad. (Just to make it...

Are you sure that this is not in fact an undercurl that is just clipped to much (so it cuts off the lower part of the curl, leaving a dotted...

It's a completely understandable endeavor, but let me just note for the sake of completeness that this would add friction to users: 1. For one, the "one stop shop" nature...

Let me be clear that I totally get where you are coming from and do not oppose this fundamentally; I just wanted to play *advocatus diaboli* and add points against...

> I don't know if moving them out even has a benefit if no one wants to maintain them in the end we have the same issue. ☝🏻 This. (And...