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

Mode message for spell completion doesn't match allowed keys #15065

Closed
wants to merge 1 commit into from

Conversation

zeertzjq
Copy link
Member

@zeertzjq zeertzjq commented Jun 21, 2024

Problem: Mode message for spell completion doesn't match allowed keys.
Solution: Use "^S" instead of "s".

fixes: neovim/neovim#29431

This matches the code in vim_is_ctrl_x_key():

case CTRL_X_SPELL:
    return (c == Ctrl_S || c == Ctrl_P || c == Ctrl_N);

Problem:  Mode message for spell completion doesn't match allowed keys.
Solution: Use "^S" instead of "s".

fixes: neovim/neovim#29431

This matches the code in vim_is_ctrl_x_key():

	case CTRL_X_SPELL:
	    return (c == Ctrl_S || c == Ctrl_P || c == Ctrl_N);
@chrisbra
Copy link
Member

thanks!

@chrisbra chrisbra closed this in 7002c05 Jun 21, 2024
@zeertzjq zeertzjq deleted the compl-spell branch June 21, 2024 06:09
zeertzjq added a commit to zeertzjq/neovim that referenced this pull request Jun 21, 2024
…llowed keys

Problem:  Mode message for spell completion doesn't match allowed keys
          (Kyle Kovacs)
Solution: Show "^S" instead of "s".
          (zeertzjq)

This matches the code in vim_is_ctrl_x_key():

	case CTRL_X_SPELL:
	    return (c == Ctrl_S || c == Ctrl_P || c == Ctrl_N);

fixes: neovim#29431
closes: vim/vim#15065

vim/vim@7002c05
zeertzjq added a commit to neovim/neovim that referenced this pull request Jun 21, 2024
…llowed keys (#29437)

Problem:  Mode message for spell completion doesn't match allowed keys
          (Kyle Kovacs)
Solution: Show "^S" instead of "s".
          (zeertzjq)

This matches the code in vim_is_ctrl_x_key():

	case CTRL_X_SPELL:
	    return (c == Ctrl_S || c == Ctrl_P || c == Ctrl_N);

fixes: #29431
closes: vim/vim#15065

vim/vim@7002c05
github-actions bot pushed a commit to neovim/neovim that referenced this pull request Jun 21, 2024
…llowed keys (#29437)

Problem:  Mode message for spell completion doesn't match allowed keys
          (Kyle Kovacs)
Solution: Show "^S" instead of "s".
          (zeertzjq)

This matches the code in vim_is_ctrl_x_key():

	case CTRL_X_SPELL:
	    return (c == Ctrl_S || c == Ctrl_P || c == Ctrl_N);

fixes: #29431
closes: vim/vim#15065

vim/vim@7002c05
(cherry picked from commit 1db1476)
@nullromo
Copy link

Thanks for the fix! However, I fear there may be a localization issue. For example, search in vim/src/po/nl.po for "spelling suggestion" and you will find these lines:

msgid " Spelling suggestion (s^N^P)"
msgstr " spellingsuggestie (s^N^P)"

Now that the message has changed, I think the translations might not work properly.

I'd be happy to fix it, but I don't know how this is normally handled. Would I make a PR against vim or neovim? Do vim-based neovim patches get added manually?

@zeertzjq
Copy link
Member Author

I'd be happy to fix it, but I don't know how this is normally handled.

I checked the commit history of src/po and it seems that translations usually don't get updated when a message changes, so I'm not sure if this should be done.

Do vim-based neovim patches get added manually?

You don't need to worry about that.

@nullromo
Copy link

I see. Based on commits like this one it looks like each language and message is kind of handled individually on a case-by-base basis.

So in this case, since a message changed, each individual language might eventually get its own pull request to update that message with the proper text. Until then, all of the languages will just have wrong translations for that message. Seems like it would be better to just batch update them all at once while we're here, no?

Is there someone in charge of each language, or is it a community effort to keep the .po files up to date?

@chrisbra
Copy link
Member

you could ping the translators, check the author of those po files (or the Last-Translator in the files headers). We could also re-generate the po files in a separate PR. I believe we have sometimes done it.

@victorhck
Copy link

hello @nullromo I would like to help, but really don't know how to do it! :)

@nullromo
Copy link

I went ahead and made a PR for it, just to keep things cleaner.

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.

Insert mode spelling completion help text is wrong
4 participants