Gregory Anders

@Mike325 Could you also add a test case for this? You can add a simple check here: https://github.com/neovim/neovim/blob/f64098a2df774c79dd454f63ac491570cdcaf2b2/test/functional/lua/fs_spec.lua#L240-L255

https://github.com/neovim/neovim/pull/16522 was an attempt to convert the help system into Lua, which would make these kinds of changes/extensions much easier to implement. Unfortunately that PR stalled out and we haven't...

I think we stick to what the spec says. If the EditorConfig people decide the spec is wrong and change it, we can change it too (it's as simple as...

```lua require('editorconfig').properties.insert_final_newline = nil ``` will disable this behavior completely, and is pretty easy to add to one's config (it's not _that_ much longer than setting an option).

> (Actually, it works if I set `require('editorconfig').properties.insert_final_newline = nil`. Thanks for the pointer!) Thanks, my mistake. I updated my original comment.

Fixed by https://github.com/neovim/neovim/pull/24738.

>TL;DR: Fixed it by removing terminfo file from user directory: mv ~/.terminfo/a/alacritty{,.bak} Just to clarify for future readers: the problem was not that the terminfo file was under `~/.terminfo`, but...

@ajoino `$TERM` being `xterm-256color` in Neovim is fishy and is almost certainly the source of your problem. I'm not aware of anything in Neovim that would change your `$TERM` value,...

> Indeed, this line sets `$TERM` upon `termopen` or `:term`: > > https://github.com/neovim/neovim/blob/v0.9.5/src/nvim/eval/funcs.c#L8821 > > Docs: `|termopen()|` > > > ``` > > Terminal environment is initialized as in |jobstart-env|,...

👋 I noticed that using mini.notify causes the intro text to disappear. Steps to reproduce: ``` mkdir repro cd repro git clone https://github.com/echasnovski/mini.nvim cat >repro.lua