Justin M. Keyes

Will this "silently fail"? That seems like it will increase troubleshooting burden. The response to that would be a need for logging or some other indicator, but that could all...

Using `opt/` was an intentional design decision so that disabling plugins is a single step: just comment-out the line in your config. That doesn't work with `start/`. > I don’t...

please add that info to the commit message

## Proposal Depending on the nature of the "broken XDG" or "broken runtime dir", Nvim should detect that issue and at least write a log message, or even fail to...

> User config may check for attached UI If you mean configs calling `nvim_list_uis()` during startup, that isn't really supported, because user configs should use UIEnter for that. Though `has('gui_running')`...

> But the problem is that there does not seem to any way to ensure that all the GUI options (for example the font), all our options related to the...

> > User config may check for attached UI > > > > * has('gui_running') works without depending on UIEnter. > > This does not work when a remote server...

# Proposal (revised) > > > User config may cause redraw and UI flush > > > > As mentioned, Vim's GUIEnter doesn't support this. What do we lose if...

> If we can redefine UIEnter, we could define it as follows. But if not, we could introduce another event like UIConfigure. We could restore `GUIEnter`... > If the UI...

> The main difference is that `GUIEnter/UIEnter` would be called as soon as possible, as a response to the `nvim_ui_attach`, or `nvim_create_autocmd`. Yes, let's do that. If people are mis-using...