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

moar -no-clear-on-exit -quit-if-one-screen with file located in /tmp creates problems with kitty terminal #190

Closed
jwezel opened this issue Jan 18, 2024 · 3 comments

Comments

@jwezel
Copy link

jwezel commented Jan 18, 2024

The mentioned command generates input on the terminal as depicted in the following screenshot:

Screenshot_20240118_172319

However, the problem occurs only in kitty terminal, not xterm.

Edit: initially I thought it has to do with the fact that the file is empty, but now I realize it is the fact that the file is located in directory /tmp.

@jwezel jwezel changed the title moar -no-clear-on-exit -quit-if-one-screen with empty file creates problems with kitty terminal moar -no-clear-on-exit -quit-if-one-screen with file located in /tmp creates problems with kitty terminal Jan 18, 2024
@walles
Copy link
Owner

walles commented Jan 18, 2024

What version of kitty is this?

I just tried it on Kitty 0.31.0 and I was unable to repro.

Also, please do moar --version.

@jwezel
Copy link
Author

jwezel commented Jan 18, 2024

Kitty version 0.30.1
Moar version 1.23.0

walles added a commit that referenced this issue Jan 18, 2024
Related to (but I can't see how this would fix) #190.
@walles
Copy link
Owner

walles commented Jan 19, 2024

I managed to reproduce by changing this timeout to zero:

moar/moar.go

Line 605 in d391bab

case <-time.After(5 * time.Millisecond):

On my system this has never taken more than about 3ms, even on Kitty.

Bumping to 50ms.

@walles walles closed this as completed in c7eaf9a Jan 19, 2024
walles added a commit that referenced this issue Jan 19, 2024
This may or may not prevent #190 and #191.
walles added a commit that referenced this issue Jan 20, 2024
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