Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Micro and Alacritty cursors are not sync #2805

Open
khasanshadiyarov opened this issue Apr 21, 2023 · 2 comments
Open

Micro and Alacritty cursors are not sync #2805

khasanshadiyarov opened this issue Apr 21, 2023 · 2 comments

Comments

@khasanshadiyarov
Copy link

khasanshadiyarov commented Apr 21, 2023

Description of the problem or steps to reproduce

So, I installed Alacritty v0.12.0 (latest to that issue submission) and tried to use Micro, I found that when I scroll down cursor is flinching around. After experimenting with changing Alacritty's cursor style settings, I found that Micro's cursor and Alacritty's cursor are staying in two different places, Micro's one is where it's supposed to be (where I navigate it), but Alacritty's is where the last symbol is being rendered (e.g. the end of new line, I have scrolled to). This causes cursor to flinch when I scroll down and appear in random (last rendered symbol) location when I interact with Micro.

However, in other native editors like vim and nano, cursor is Alacritty's cursor, which can be seen by modifing Alacritty cursor settings.

Specifications

micro --version:

Version: 2.0.11
Commit hash: 225927b9
Compiled on August 01, 2022

OS: Windows 10 Home, 1903, build of 18362.175
Terminal: Alacritty v0.12.0

Screenshot

image
As you can see Alacritty cursor stands after utf-8, since 8 is the last symbol being rendered.

Troubleshooting

  • Yes, it's only happens in Alacritty terminal emulator
  • Any cursor related Alacrity configuration didn't help
  • Any Micro cursor related setting didn't help
@zyedidia
Copy link
Owner

I think this is because micro defaults to using a “fake cursor” on windows because the windows console cursor is extremely slow. I’ll look into adding an option to disable this for better terminals like alacritty.

@khasanshadiyarov
Copy link
Author

I think this is because micro defaults to using a “fake cursor” on windows because the windows console cursor is extremely slow. I’ll look into adding an option to disable this for better terminals like alacritty.

Yeah, that would be awesome, I think the cursor speed can be configure by terminal/system settings by the user itself. E.g. the same alacritty has pretty full cursor speed configuration.

Thanks for the reply, could you pls share an updated commit in this thread when the issue is solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants