Skip to content

Conversation

@veracioux
Copy link
Contributor

Closes #3871.

I also reverted to the behavior from v0.15.x where the resulting prompt is args.prompt + stdin, whereas in v1.x it is currently stdin + args.prompt.

Copy link

@kunaljaykam kunaljaykam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @veracioux it fixes the issue. i have tested in fedora

@veracioux
Copy link
Contributor Author

@kunaljaykam yw. What's missing is windows support, which I tried to add but doesn't work. I don't have a windows setup rn so I asked @rekram1-node to implement it. If you have a windows setup and are willing to help out, i think @rekram1-node would appreciate it.

@rekram1-node In any case, I think this PR is good to merge since it works for linux and doesn't break anything that wasn't already broken on windows (after reverting 53dc493)

@kunaljaykam
Copy link

i don’t have a windows setup, but you can spin up a windows instance on aws or azure and test it there using windows terminal.

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

Successfully merging this pull request may close these issues.

Bug: Stdin piping breaks UI

3 participants