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

Using Air whilst developing CLI tools #711

Open
frederickmannings opened this issue Dec 6, 2024 · 4 comments
Open

Using Air whilst developing CLI tools #711

frederickmannings opened this issue Dec 6, 2024 · 4 comments

Comments

@frederickmannings
Copy link

When using the air default toml config, I am unable to interact with a CLI tool I am building. Is this a feature or a bug?

image

q, does not kick the program out. Framework I am using under the hood is bubbletea.

@istyf
Copy link
Contributor

istyf commented Dec 6, 2024

Unfortunately air does not support forwarding stdin to the application. See #387

@xiantang
Copy link
Collaborator

@istyf do u have any idea to support this feature?

@istyf
Copy link
Contributor

istyf commented Dec 21, 2024

@istyf do u have any idea to support this feature?

@xiantang I have not had the need so I haven't looked at it, but @8LWXpg has proposed some changes in #653 . Those changes are not compatible with my #670 though, but could serve as an inspiration.

@8LWXpg
Copy link
Contributor

8LWXpg commented Dec 21, 2024

@istyf #653 is mainly about removing the return of stdout and stderr at startCmd since killing the command should
also close the pipe as well (not fully sure about the pty used on Linux tho).

I also ran CI test locally on WSL and facing possibly the same issue as #673, might as well the reason CI test failed on GitHub.

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

4 participants