Closed chriscroome closed 1 year ago
This unfortunately is a bug in urwid. I have no idea how to solve this ☹
The urwid
library looks like it needs some updating... perhaps simply remove support for piping or just update the documentation to say it doesn't work for now? :shrug:
The
urwid
library looks like it needs some updating... perhaps simply remove support for piping or just update the documentation to say it doesn't work for now? 🤷
In fact, even if I disable piping from jpterm
the very fact of piping is detected by the underlying urwid
library. Somehow, I need to find how to instructions to disable piping at the urwid
level. But I have a hard time finding relevant documentation.
In any case, sure, I will eventually update the README anyway and include a Known Issues section.
Thanks @springcomp for forking and updating this project :slightly_smiling_face:.
I have found that piping into
jpterm
generates an error:But writing a file and opening it work fine:
This isn't a big or urgent problem!
This is on Debian Bookworm with a
pipx
installed version: