John Gehrig

@zeGolem If you're willing to help, we may be able to get this working! Two approaches: 1. If you know how to fix this with `QInputMethod`, I'm happy to review...

[Delete] Weird... GitHub double posted.

@zeGolem Those are EXCELLENT instructions! That is exactly what I was looking for... I will work on getting a test environment set up, and I will report back in a...

I hear what you're saying... We should provide an option of some kind. However, I also feel strongly that the 'out-of-the-box' behavior should be roughly what you find today in...

@xiaohuSuperman Thanks for the bug report! What font are you using? Can you provide a link or TTF file? Can you paste the problematic characters into the bug? These issues...

> Should running nvim-qt foo.txt work correctly now? Yes. Can you open a new issue to track your problem? It would also be helpful to provide additional information about your...

@equalsraf Hopefully, you don't mind me poking your branch :) I've found a workaround for the test-failure-output issue! It looks like something about the GitHub Actions environment is causing issues...

It looks like the `tst_shell` failures are related to #898. The behavior of the `neovimAttachmentChanged` signal changed, and this broke tests. A call to `->show()` is now required. I didn't...

If we can get GitHub Actions working reliably, it would be nice to consolidate the CI jobs... Perhaps we could remove CircleCI/AppVeyor/AzurePipelines after some period of time? If we do...

@alfredobarroso Sorry for the huge delay here. Is there any chance you could do some testing with the current iteration? I am not familiar with these keyboard layouts... It is...