-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
8.1.2153 (3439028c) broke detection and highlighting of misspelled words #5078
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
Comments
I see a similar issue on 8.1.2169 where most words at the beginning of lines appears to fail spellcheck, screenshot:

Notice how all letters except the first letter are incorrectly marked
as mispelled, but problem goes away after a space is inserted before
each word.
Thanks for reporting. That patch was a risky change. I finally decided
to take the risk, because the computation of attributes was so messy.
It's at least in the right order now, but I already fixed a few problems
caught by tests, then found a few more problems not caught by tests,
like this one. There might be another one.
…--
(letter from Mark to Mike, about the film's probable certificate)
I would like to get back to the Censor and agree to lose the shits, take
the odd Jesus Christ out and lose Oh fuck off, but to retain 'fart in
your general direction', 'castanets of your testicles' and 'oral sex'
and ask him for an 'A' rating on that basis.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
|
manuelschiller
pushed a commit
to manuelschiller/vim
that referenced
this issue
Nov 10, 2019
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim#5078)
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 17, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 17, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 18, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 18, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 18, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d N/A patches for version.c: vim-patch:8.1.1541: check for ASAN is not reliable Problem: Check for ASAN is not reliable. Solution: Check the version output. (Dominique Pelle, closes vim/vim#4543) vim/vim@bffc504
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 19, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d N/A patches for version.c: vim-patch:8.1.1541: check for ASAN is not reliable Problem: Check for ASAN is not reliable. Solution: Check the version output. (Dominique Pelle, closes vim/vim#4543) vim/vim@bffc504
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 19, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135 N/A patches for version.c: vim-patch:8.1.1541: check for ASAN is not reliable Problem: Check for ASAN is not reliable. Solution: Check the version output. (Dominique Pelle, closes vim/vim#4543) vim/vim@bffc504
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 19, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135 N/A patches for version.c: vim-patch:8.1.1541: check for ASAN is not reliable Problem: Check for ASAN is not reliable. Solution: Check the version output. (Dominique Pelle, closes vim/vim#4543) vim/vim@bffc504
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 21, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 21, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 24, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Jul 26, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Aug 1, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
janlazo
added a commit
to janlazo/neovim
that referenced
this issue
Aug 2, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
farisachugthai
pushed a commit
to farisachugthai/neovim
that referenced
this issue
Aug 4, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
tjdevries
pushed a commit
to tjdevries/neovim
that referenced
this issue
Aug 5, 2020
Problem: Spell highlight is wrong at start of the line. Solution: Fix setting the "v" variable. (closes vim/vim#5078) vim/vim@7751d1d Skip spell tests in OpenBSD. Nvim or screen likely crashed. Revist once issue neovim#12104 is fixed. Skip the test for the following reasons: - unknown regression caused by neovim#12104 - cannot revert failing test from neovim@ed0d135
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm on macOS 10.14.6. Vim 8.1.2153 has broken the identification and highlighting of misspelled words. Specifically, some words that aren't misspelled are highlighted as misspelled, but only partly.
Bisection reveals that this commit broke the identification and highlighting of misspelled words:
It particular, if a word was declared good by me in
~/.vim/spell/en.utf-8.add.spl
, then if that word begins a line all of it except the first letter are highlighted as a misspelled word. But if that same word is not at the start of a line, Vim correctly leaves it alone. This only happens for words that I have in my spelling additions file.All of this involves starting vim with -u NONE -U NONE -N --noplugin.
I have
en.utf-8.add.spl
in my~/.vim/spell
. It contains 'Quine' as a good word.After 3439028, if I put the following in a file:
and do
:set spell
, then I observe the following:In the first occurrence of 'Quine', only the 'uine' is highlighted as a bad word while the 'Q' is left alone. So vim is wrongly identifying it as bad, and then botching the highlighting of the badness.
The second occurrence of 'Quine' is left alone.
Interestingly,
]s
doesn't move the cursor onto the first 'Quine'. And interestingly, there's nothing special about 'Quine'. This happens for all words in my spelling additions file, as far as I can see.When I say that Vim highlights it as misspelled, I mean that I see the
undercurl
that is normally used for misspelled words. I'm using a colorscheme that does not explicitly setundercurl
orguisp
for anything, so this is coming from Vim.The text was updated successfully, but these errors were encountered: