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

macOS pipe none command seems to freeze kitty #1708

Closed
hanoii opened this issue Jun 12, 2019 · 4 comments
Closed

macOS pipe none command seems to freeze kitty #1708

hanoii opened this issue Jun 12, 2019 · 4 comments

Comments

@hanoii
Copy link

hanoii commented Jun 12, 2019

I don't use this very often, but I needed it now and it froze kitty.

I have this in config:

map f1 pipe @text none /usr/local/bin/subl
scrollback_pager_history_size 50

Now when I run f1, the editor opens with the output but kitty freezes and become unresponsive, I have to force quit it.

On the other hand, using tab instead of none works.

@hanoii hanoii changed the title macOS pipe command seems to freeze kitty macOS pipe none command seems to freeze kitty Jun 12, 2019
@kovidgoyal
Copy link
Owner

When you pass data to an external program kitty waits until all data is
read. It does so on the main thread. Presumably whatever program you are
passing the data to is not reading all of it.

@hanoii
Copy link
Author

hanoii commented Jun 12, 2019

That didn't happen on on 0.13.x, started to happen just recently.

Also, isn't none supposed to be background? it freezes with the loading clock, completely unresponsive. tab works.

@kovidgoyal
Copy link
Owner

No, the process is background, passing data to it is not, and never has
been. So if you use pipe with none without any data, it will never hang,
with data, it will hang till the process reads all the data.

@hanoii
Copy link
Author

hanoii commented Jun 12, 2019

Right..

echo "aa" | subl also never ends until I close the editor tab.. which just found out it also unfreezes kitty.

The data is all read, but I guess sublime is leaving stdin open. This must be something new, this was working ok before with the same editor.

Ok, I can work around this. Thanks :)!

kovidgoyal added a commit that referenced this issue Jun 12, 2019
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