Adding annotations to user dictionary entries seems to be glitchy

[x-yuri]

That's me again :) Hopefully you haven't got tired of my issues.

I must admit, I don't have the need to add custom entries yet. It's just that this prompt pops up every now and then, and I don't really know what I'm supposed to do, other than pressing Esc/Ctrl-c (somehow) twice. I didn't. Right now I think I get the hang of it for the most part. But it doesn't seem to always work properly.

Disclaimer. I'm going to use (supposedly) imaginary words.

I type, ;asuri<Space>, it asks me for the converted version, I type, ;asu<Space>ri<CR>. This way it works.

Now let's try to add an annotation: ;asuri<Space>, ;asu<Space>ri<Ctrl-j>;annotation<CR>. It adds the word all right, but when I press Enter, ▽ is still in the buffer, and it doesn't seem like it finished properly. Am I doing it wrong? Missing something?

On a side note, is there an easier (than double-Esc/Ctrl-c) way to cancel adding an entry?

[Shougo]

reproduced.

[Shougo]

On a side note, is there an easier (than double-Esc/Ctrl-c) way to cancel adding an entry?

I think empty enter is the better way to cancel.

[Shougo]

The twice reason:
You have pressed space key twice. They are adding an entry and henkan. The states are stacked.

The first cancel is adding an entry.
But henkan is not canceled! So you want to cancel both, you need to press esc keys twice.

[Shougo]

I get the reason. It seems bug. But it is hard to fix...

[Shougo]

Reason.

https://github.com/tyru/eskk.vim/blob/8e3f82a838452b44062c567dd8aad5f613931ec2/autoload/eskk.vim#L2128

If you input annotation, the eskk is disabled to input ;.
So insert word is canceled.

[Shougo]

If in eskk#util#prompt() eskk restores eskk state, it is better.
But I don't know how to implement it.

[Shougo]

I have workaround fixed.

[x-yuri]

Great.

Regarding the cancelling thing. It appears Enter, Esc, Ctrl-C (and Ctrl-G for that matter) are not much different in that regard. I'm mostly running vim (or usually nvim) in tmux. And with tmux it looks like this:

Then I press any of those:

And for me the last state looks like it's asking for something else (after all, the cursor is still at the command bar), although in a weird way (empty prompt). Now I see, that at this point I can just continue typing. Without tmux it looks a bit different, although still confusing:

I'm not sure, but it might be just how vim works (or vital). Meaning, there's not much to be done about it.

[Shougo]

And for me the last state looks like it's asking for something else (after all, the cursor is still at the command bar), although in a weird way (empty prompt). Now I see, that at this point I can just continue typing. Without tmux it looks a bit different, although still confusing:

Yes. I know the behavior. But I don't know it can be fixed.

[x-yuri]

But it's introduced by eskk, isn't it? I can't see such effect after input() or vital's input_safe(). Do you know what causes it? Which command (file:line)?