From c3ded5eb7279122b1fe46a1864e815fb7d1a617d Mon Sep 17 00:00:00 2001 From: Kovid Goyal Date: Mon, 17 Jan 2022 10:39:13 +0530 Subject: [PATCH] ... --- docs/kittens/icat.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/kittens/icat.rst b/docs/kittens/icat.rst index ae090eced..3c25f76ec 100644 --- a/docs/kittens/icat.rst +++ b/docs/kittens/icat.rst @@ -36,12 +36,12 @@ Then you can simply use ``icat image.png`` to view images. manager, there are a couple of things to keep in mind. icat works by communicating over the TTY device, it both writes to and reads from the TTY. So it is imperative that while it is running the host program does not do - any TTY I/O. And any key presses or other input from the user on the TTY - device will be discarded. At a minimum, you should use the - :option:`kitty +kitten icat --silent` and :option:`kitty +kitten icat --transfer-mode` flags. To be really robust - you should consider writing proper support for the - :doc:`../graphics-protocol` in the program instead. - Nowadays there are many libraries that have support for it. + any TTY I/O. Any key presses or other input from the user on the TTY device + will be discarded. At a minimum, you should use the :option:`kitty +kitten + icat --silent` and :option:`kitty +kitten icat --transfer-mode` flags. To be + really robust you should consider writing proper support for the + :doc:`../graphics-protocol` in the program instead. Nowadays there are many + libraries that have support for it. .. program:: kitty +kitten icat