Gregory Anders

Thinking about this more I think I do lean toward `DiagnosticOk` rather than `Success`. `:checkhealth` is itself a diagnostic tool, so I also think we should create default links from...

>This also aligns with other editor (ahem) files such as .idea, .vscode. (Not super important, but at least indicates a pattern.) Both `.idea` and `.vscode` are directories. If we wanted...

> when? `.nvim.lua` can do arbitrary things like calling into a directory. For example, as another directory on `runtimepath` (adding new compilers, custom ftplugins/snippets/etc. for a project).

> To unblock this PR, shall we at least name the lua file `.nvim.lua` ? Then the idea of a `.nvim` directory can wait until later. 👍

Thanks @MunifTanjim! Nice work as always.

Try running an interactive rebase: ``` git rebase -i master ``` Change `pick` to `drop` on any commits that should not be in this PR. Then force push when you’re...

Isn't this the use case `vim.fs.find()` is meant to solve? It doesn't work with globs right now, but if it did, couldn't ```lua for _, kind in ipairs({ '*.vim', '*.lua'...

>Though If I'm being honest and transparent, I feel this API could be better. At the very least stop and type would both be better replaced by a more general...

>My personal opinion is that all boolean option values with 80% here seem like widespread enough to become default. This includes `number`, `expandtab`, `ignorecase`, and `smartcase`. The default value of...

For `'termguicolors'`, https://github.com/termstandard/colors#checking-for-colorterm has some useful information for determining support. This would not be hard for us to implement. We have the technology. 1. If `$COLORTERM` is `truecolor` or `24bit`,...