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
basically, the following things happen when one tryes to use caret navigation, either individually or all at once
odilia doesn't read that I moved to another line till I moved through a considerable number of them
when I move between characters, it sometimes doesn't read the character I moved to
when typing new characters, sometimes it doesn't read the character I'm typing, other times it reads characters from earlier in the line
when moving backward, it can sometimes not read anything at all
The algorythm from the prototype and early versions of odilia worked considerably better, since I was able to type text in the terminal, get output relatively on point and read text in an editor relatively normally
you once said on matrix that you had a branch where you almost fixed it, but you didn't apply that commit or something, perhaps you could recreate that? Essentially, on the surface, the algorythm is correct, I don't know why it's not working as intended. It's possible that the cache hits again, but it's not very likely for that to be a definite answer either way.
The text was updated successfully, but these errors were encountered:
basically, the following things happen when one tryes to use caret navigation, either individually or all at once
The algorythm from the prototype and early versions of odilia worked considerably better, since I was able to type text in the terminal, get output relatively on point and read text in an editor relatively normally
you once said on matrix that you had a branch where you almost fixed it, but you didn't apply that commit or something, perhaps you could recreate that? Essentially, on the surface, the algorythm is correct, I don't know why it's not working as intended. It's possible that the cache hits again, but it's not very likely for that to be a definite answer either way.
The text was updated successfully, but these errors were encountered: