You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I’d like to express my gratitude for creating such an incredibly useful tool. I recently started using Firenvim, and it has been extremely helpful for my workflow. I also appreciate that Japanese input is supported, which has made things much easier.
However, there’s a small improvement I’d like to suggest. While typing in Japanese, the text being input doesn’t appear "inline in the actual textarea" where it is meant to be entered. In my environment, the Japanese input system shows the text near the mouse cursor, but since it’s displayed slightly away from where I am typing, I find myself prone to making typing mistakes.
Therefore, I’d like to request support for "inline input." Similar requests have been raised in other tools, such as WezTerm, and they've successfully implemented it, as shown here: wez/wezterm#3411
I tried making changes to support inline input myself, and it seems to work. If possible, could you please review my implementation?
Thank you once again for your hard work!
The text was updated successfully, but these errors were encountered:
Hello!
First of all, I’d like to express my gratitude for creating such an incredibly useful tool. I recently started using Firenvim, and it has been extremely helpful for my workflow. I also appreciate that Japanese input is supported, which has made things much easier.
However, there’s a small improvement I’d like to suggest. While typing in Japanese, the text being input doesn’t appear "inline in the actual textarea" where it is meant to be entered. In my environment, the Japanese input system shows the text near the mouse cursor, but since it’s displayed slightly away from where I am typing, I find myself prone to making typing mistakes.
Therefore, I’d like to request support for "inline input." Similar requests have been raised in other tools, such as WezTerm, and they've successfully implemented it, as shown here: wez/wezterm#3411
I tried making changes to support inline input myself, and it seems to work. If possible, could you please review my implementation?
Thank you once again for your hard work!
The text was updated successfully, but these errors were encountered: