Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

encoding: UTF-32 Assertion Failure #12010

Closed
wants to merge 1 commit into from

Conversation

zubairabid
Copy link

A fix for #11877. Replaced characters over INT_MAX with U+FFFD, as proposed in the discussion.

Behaviour is now identical to that of vim -u DEFAULTS.

Test coverage:

[==========] 655 tests from 33 test files ran. (38134.31 ms total)
[  PASSED  ] 655 tests.

Linter:

Total: 0 warnings / 0 errors in 414 files

Fix neovim crash when editing specific files as UTF-32 encoded.
Replaces values above INT_MAX with U+FFFD.
@zubairabid
Copy link
Author

@bfredl would it be possible for you to take a look at this?

@bfredl
Copy link
Member

bfredl commented Mar 17, 2020

Code looks fine. Ideally we would have some kind of test for this. Perhaps there are some existing tests for fenc loading we can adapt.

@teto
Copy link
Member

teto commented Jun 8, 2020

could you add a test similar to the last one in test/functional/core/fileio_spec.lua please ?

@zubairabid
Copy link
Author

Hi sorry, I got a bit derailed by classwork. I'll look into adding tests in the next couple of days.

@gpanders
Copy link
Member

Superseded by #16354.

@gpanders gpanders closed this Nov 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants