Skip to content

test(basics): adjust win_borders test after Nightly changes#2489

Closed
abeldekat wants to merge 1 commit into
nvim-mini:mainfrom
abeldekat:test_fix_basics
Closed

test(basics): adjust win_borders test after Nightly changes#2489
abeldekat wants to merge 1 commit into
nvim-mini:mainfrom
abeldekat:test_fix_basics

Conversation

@abeldekat

Copy link
Copy Markdown
Member

Details:

  • The order of the fields in the resulting vim.o.fillchars now is the same as in the H.win_borders_fillchars definitions.
  • See PR 39849 in neovim/neovim.

Details:
- The order of the fields in the resulting `vim.o.fillchars` now
is the same as in the `H.win_borders_fillchars` definitions.
- See PR 39849 in neovim/neovim.
echasnovski added a commit that referenced this pull request Jun 29, 2026
Details:
- Order of entries in 'fillchar' does not matter, but using alphabetical
  one makes it more robust across Neovim versions (Neovim>=0.13
  preserves actual order of entries).

Resolve #2489
echasnovski added a commit that referenced this pull request Jun 29, 2026
Details:
- Order of entries in 'fillchar' does not matter, but using alphabetical
  one makes it more robust across Neovim versions (Neovim>=0.13
  preserves actual order of entries).

Resolve #2489
@echasnovski

Copy link
Copy Markdown
Member

Thanks for the PR!

I was about to merge into main, when decided to take a closer look locally as to why this happened. Turned out, there was a slightly better approach to fixing this by using alphabetical order in built-in 'fillchars' for win_borders. As this doesn't require any special handling in tests, I decided to go with it. And as this has zero code intersection with initial idea of the PR (and as I was going through backlog anyway), decided to not bother you asking to do essentially a completely different PR. Hope that's okay.

@abeldekat

Copy link
Copy Markdown
Member Author

That's completely fine. Thanks for the feedback!

@abeldekat abeldekat deleted the test_fix_basics branch June 29, 2026 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants