You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing an ncurses-based (such as vim), the output does not appear to update correctly.
For example:
try runAndPrint("/usr/bin/vim")
I do not see the vim UI at all. When I hit Ctrl-C, I see a flash in the terminal. So this implies that the text controls were sent but perhaps are being buffered. I looked through the code but I don't see an obvious way to control the stdout buffer size.
As a separate issue, it would be nice if there was a way to pass-thru ctrl-c and other job control keys to the executing process.
The text was updated successfully, but these errors were encountered:
Hi, SwiftShell does not support interacting with running processes, other than launching them and getting their output.
Except if you run a command `runAsync` you can send commands .stop, .interrupt and .suspend . .stop is normally the same as Ctrl-C I believe.
24. nov. 2021 kl. 02:41 skrev Danny Sung ***@***.***>:
When executing an ncurses-based (such as vim), the output does not appear to update correctly.
For example:
try runAndPrint("/usr/bin/vim")
I do not see the vim UI at all. When I hit Ctrl-C, I see a flash in the terminal. So this implies that the text controls were sent but perhaps are being buffered. I looked through the code but I don't see an obvious way to control the stdout buffer size.
As a separate issue, it would be nice if there was a way to pass-thru ctrl-c and other job control keys to the executing process.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
When executing an ncurses-based (such as vim), the output does not appear to update correctly.
For example:
I do not see the vim UI at all. When I hit Ctrl-C, I see a flash in the terminal. So this implies that the text controls were sent but perhaps are being buffered. I looked through the code but I don't see an obvious way to control the stdout buffer size.
As a separate issue, it would be nice if there was a way to pass-thru ctrl-c and other job control keys to the executing process.
The text was updated successfully, but these errors were encountered: