Thank you, I will take a look at this a bit later (in a few days)

It's possible that it would make sense to just implement the base API in Neovide, and implement the rest in a separate plugin for easier development, and possible faster updates. But I'm not sure yet.

I don't know what you're unsure about, but there are plugins like equalsraf/neovim-gui-shim that separate GUI-related functions. I can't say that it works stably yet, so separating it as a plugin would probably be better in terms of development. Also, regarding handling IME with a plugin, in terms of performance, the focus is on the implementation using NeoVim's autocommands rather than on plugin loading.

Anyway, if you're going to merge only the base API, please let me know so I can make the change.

Hi! I build and use your commit id: e58082d
In Manjaro KDE Plasma 6 Wayland + Fcitx5 chewing.

I try to insert mode with ime input at 3rd lines.
But always insert at first line end character.

And I use direction keys move cursor.

Display Bug like this image:

Is freeze status. Press Enter key is not response.

@chyuaner,Thank you for reporting!
I would like to know what kind of behavior it has, so could you please send me the log data?

I Record Screen. And found another bug!
If I have swp file will freeze.
and output log:

ERROR [neovide::bridge::ui_commands] Input failed

Caused by:
    0: Error decoding response to request 'nvim_exec_autocmds'
    1: Error while reading from Reader
    2: EOF
ERROR [neovide::bridge::ui_commands] Input failed

Caused by:
    0: Error sending request 'nvim_exec_autocmds'
    1: Error writing to the Writer
    2: Broken pipe (os error 32)
ERROR [neovide::bridge::ui_commands] Input failed

Caused by:
    0: Error sending request 'nvim_input'
    1: Error writing to the Writer
    2: Broken pipe (os error 32)
ERROR [neovide::bridge::ui_commands] Input failed

Caused by:
    0: Error sending request 'nvim_input'
    1: Error writing to the Writer
    2: Broken pipe (os error 32)
ERROR [neovide::bridge::ui_commands] Input failed

Back to yesterday's question.

I would like to know what kind of behavior it has, so could you please send me the log data?
It doesn;t show any log. But I try to record my screen to reappear this bug.

I try to insert mode with ime input at 3rd lines.
But always insert at first line end character.

處理 User Autocommands: "ImePreedit" 時發生錯誤:
Error executing lua callback: [string "<nvim>"]:63: Invalid 'end_col': out of range
stack traceback:
        [C]: in function 'nvim_buf_set text'
        [string "<nvim>"1:63: in function <[string "<nvim>"]:44>
Press ENTER or type command to continue

Regarding the swapfile issue, it looks like Neovim is either not responding at all, or crashed. It's possible that it's caused by something else and not these changes, @chyuaner, are you able to reproduce it without?

Regarding the swapfile issue, it looks like Neovim is either not responding at all, or crashed. It's possible that it's caused by something else and not these changes, @chyuaner, are you able to reproduce it without?

I change neovide version to Arch Linux Pacman Package: neovide-0.15.0-1.
And try reproduce the swapfile issue.

All hint text is show half one second and disappeared.
But key input is normal operation can use.

I think, I know what's wrong with the hang.

This PR tries to execute autocommands, which probably isn't supported when a message is showing. Perhaps a more explicit lua API with callbacks could be created. We don't have much yet, but it can and will be extended. For example, the image support will also provide an API.

And even then, it's possible that the lua side, has to disable some things, like actually showing the pre-edit.

You might be able to reproduce this by simply opening a confirm dialog https://neovim.io/doc/user/builtin.html#confirm()

I will change my policy to implement a Lua API. I intend to separate the pre-edit preview and other functions into a separate plugin.

I separated it into a Lua API and a plugin that supports pre-edit. However, since the plugin only transferred what was written when opening pull request, I would like to address the problem there.