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
Describe the bug
I'm not sure if this is bug with gocui, but i'll report it here, you'll know better.
When you open a commit message modal, and type few characters, then click with mouse in the middle of the modal, cursor will go to that position. If you continue typing, it will type, but cursor will be at wrong position all the time. Also you cannot delete anything after that happens.
To Reproduce
Steps to reproduce the behavior:
Stage some files
Open "Commit message" dialog with C
Type in few characters
Click with mouse in the middle of the commit message dialog
Continue typing, notice the behavior of the cursor
Try deleting with backspace, nothing happens
Expected behavior
I guess either cursor should jump back to the right position or clicking in the middle of modal should not even trigger cursor movement.
Screenshots
I'm not able to make a screenshot that shows the cursor for me, i'm probably using bad tool for it.
Desktop (please complete the following information):
Yeah I've seen this as well. I believe over in awesome/gocui work is being done to make the editing experience better wrt cursors: awesome-gocui/gocui#48
Describe the bug
I'm not sure if this is bug with gocui, but i'll report it here, you'll know better.
When you open a commit message modal, and type few characters, then click with mouse in the middle of the modal, cursor will go to that position. If you continue typing, it will type, but cursor will be at wrong position all the time. Also you cannot delete anything after that happens.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I guess either cursor should jump back to the right position or clicking in the middle of modal should not even trigger cursor movement.
Screenshots
I'm not able to make a screenshot that shows the cursor for me, i'm probably using bad tool for it.
Desktop (please complete the following information):
Additional context
restarting lazygit fixes it.
The text was updated successfully, but these errors were encountered: