TStatusBar

[fanfix.git] / README.md

diff --git a/README.md b/README.md
index 2f146cc4f3b585d4678eeb3bd2c350109099ed32..22436558fb3f653491423ec7a26bb600fb3855aa 100644 (file)
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@ Jexer currently supports three backends:
   sequences generated by the library itself: ncurses is not required
   or linked to.  xterm mouse tracking using UTF8 and SGR coordinates
   are supported.  For the demo application, this is the default
   sequences generated by the library itself: ncurses is not required
   or linked to.  xterm mouse tracking using UTF8 and SGR coordinates
   are supported.  For the demo application, this is the default

-  backend on non-Windows platforms.
+  backend on non-Windows/non-Mac platforms.

 
 * The same command-line ECMA-48 / ANSI X3.64 type terminal as above,
   but to any general InputStream/OutputStream or Reader/Writer.  See
 
 * The same command-line ECMA-48 / ANSI X3.64 type terminal as above,
   but to any general InputStream/OutputStream or Reader/Writer.  See


@@ -23,9 +23,9 @@ Jexer currently supports three backends:
   character encoding than the default UTF-8.
 
 * Java Swing UI.  This backend can be selected by setting
   character encoding than the default UTF-8.
 
 * Java Swing UI.  This backend can be selected by setting

-  jexer.Swing=true.  The default window size for Swing is 132x40,
-  which is set in jexer.session.SwingSession.  For the demo
-  application, this is the default backend on Windows platforms.
+  jexer.Swing=true.  The default window size for Swing is 80x25, which
+  is set in jexer.session.SwingSession.  For the demo application,
+  this is the default backend on Windows and Mac platforms.

 
 Additional backends can be created by subclassing
 jexer.backend.Backend and passing it into the TApplication
 
 Additional backends can be created by subclassing
 jexer.backend.Backend and passing it into the TApplication


@@ -180,10 +180,11 @@ ambiguous.  This section describes such issues.
     input (see the ENABLE_LINE_INPUT flag for GetConsoleMode() and
     SetConsoleMode()).
 
     input (see the ENABLE_LINE_INPUT flag for GetConsoleMode() and
     SetConsoleMode()).
 

-  - TTerminalWindow launches 'script -fqe /dev/null' on non-Windows
-    platforms.  This is a workaround for the C library behavior of
-    checking for a tty: script launches $SHELL in a pseudo-tty.  This
-    works on Linux but might not on other Posix-y platforms.
+  - TTerminalWindow launches 'script -fqe /dev/null' or 'script -q -F
+    /dev/null' on non-Windows platforms.  This is a workaround for the
+    C library behavior of checking for a tty: script launches $SHELL
+    in a pseudo-tty.  This works on Linux and Mac but might not on
+    other Posix-y platforms.

 
   - Closing a TTerminalWindow without exiting the process inside it
     may result in a zombie 'script' process.
 
   - Closing a TTerminalWindow without exiting the process inside it
     may result in a zombie 'script' process.