#windows terminal
1 messages ยท Page 1 of 1 (latest)
also cc @raven plume
Hi @untold sapphire happy Monday. would you have few mins to allow me to show what is happening with windows terminal thing.
hm
happy monday ๐
this is for https://github.com/dagger/dagger/pull/9334?
?
so applying this change causes the weird exit behavior you see?
yeah
it works fine with dagger call but I see that issue with dagger shell
after I type in exit and click enter, the terminal prints exit 0, and then print the container object and then clears the terminal. but it keeps it there until I click anykey again
so i am wondering if stdin is waiting for that keypress ๐คทโโ๏ธ, but i am not familar with the TUI stuff there.
but on main it works?
let me quickly try to be double sure
also, this works fine on mac, but only a prob on win]
ok.
- does not work with main.
- hangs until key-pressed with branch.
on main, it seems like the original issue itself was not fixed. I was shuffling computers to test on windows, so can't rule out a possibility that I tested with a wrong compiled version of dagger-client originally.
now that I am testing it, with main - it seems original issue is not fixed. with PR, this weird behavior only on exit on shell.
given you have spent so much time on TUI, i am really hopeful that once you see what is happening, you might be able to either tell where the issue is or atleast point me in a direction to debug this more
okay, the weird behavior seems weird, but definitely better than it not working at all
i added log statements in tui code, but couldn't figure out where is it getting stuck.
it's potentially restoring the terminal, and getting an empty screen
the process might not be running anymore
but when i press any key, its restored correctly?
๐คทโโ๏ธ could just be the shell rendering it fully then?
how about let me do a small recording and share it here.
or if you think we can live with this and just merge that fix, that works as well ๐
eh, i think we can live with this ๐ but a screen recording would be good too