Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <19990810210956.A15706@ba.best.com> Date: Tue, 10 Aug 1999 21:09:56 -0400 From: Glenn Spell To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Terminal handling with the 990809 snapshot Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: the aerie The 990809 snapshot seems to have corrected the get_signal_mutex and the CTRL-C problems, at least the ones I saw on Win95. There are two issues remaining that I'd like to get on the table before the next release. Both involve terminal/console handling. First, an issue with "ls --color" and the console screen on Win95. (This is of interest to me only if it's likely that whatever is causing this may also cause other more significant problems.) This only happens with "tty" set. With "notty", it's normal. If I log into Cygwin with any shell and immediately issue the command "ls --color", I can see the color appear for an instant, but then it disappears and everything is black and white. If I continue issuing the same command, somewhere around the third to the fifth try... the color will "stick". This behavior started with the 990626 snapshot and continues thru the 990809 snapshot. Last (but as they say, not least), the 990614 thru and including the 990628 snapshots were the only ones, until recently, where issuing a "CTRL-A \" command in 'screen' would exit all running processes before terminating 'screen'. (I had always used "tty" with 'screen' until just yesterday so I don't know how those snapshots behaved with "notty".) Now, with both the 990808 and the 990809 snapshots, 'screen' will exit all processes before terminating. That's good. Thanks, Chris. However, 'screen' now only runs properly with "notty" set. I can best explain all this by illustrating the display. First, I'd like to illustrate that it works with "notty" set. The next two illustrations are with starting 'screen' from a bash login shell and four windows being started via the .screenrc file with bash running in each window. My comments are in parenthesis. (This is with 990808 and "notty":) BASH-2.03$ ps PID TTY STIME COMMAND 10001073741824 19:12:04 /USR/BIN/BASH.EXE 10011073741824 19:12:07 /BIN/SCREEN.EXE 1002 -1 19:12:08 /BIN/SCREEN.EXE 1003 0 19:12:08 /USR/BIN/BASH.EXE 1004 1 19:12:09 /USR/BIN/BASH.EXE 1005 2 19:12:10 /USR/BIN/BASH.EXE 1006 3 19:12:12 /USR/BIN/BASH.EXE 1007 3 19:12:41 /USR/NEW-WINSUP/BIN/PS.EXE BASH-2.03$ (CTRL-A \ issued) [screen is terminating] BASH.EXE-2.03$ ps PID TTY STIME COMMAND 1000 -1 19:12:04 /USR/BIN/BASH.EXE 1008 -1 19:12:59 /USR/NEW-WINSUP/BIN/PS.EXE BASH.EXE-2.03$ (This is with 990809 and "notty" (better :-)):) BASH-2.03$ ps PID TTY STIME COMMAND 1000 -1 19:19:41 /USR/BIN/BASH.EXE 1009 -1 19:20:17 /BIN/SCREEN.EXE 1010 -1 19:20:17 /BIN/SCREEN.EXE 1011 0 19:20:17 /USR/BIN/BASH.EXE 1012 1 19:20:18 /USR/BIN/BASH.EXE 1013 2 19:20:19 /USR/BIN/BASH.EXE 1014 3 19:20:21 /USR/BIN/BASH.EXE 1015 3 19:20:28 /USR/NEW-WINSUP/BIN/PS.EXE BASH-2.03$ (CTRL-A \ issued) (The next line actually moves to bottom of display) [screen is terminating] BASH.EXE-2.03$ ps PID TTY STIME COMMAND 1000 -1 19:19:41 /USR/BIN/BASH.EXE 1016 -1 19:21:11 /USR/NEW-WINSUP/BIN/PS.EXE BASH.EXE-2.03$ But there's a problem when "tty" is set. My guess is that some buffer is not getting flushed at the right times. The remaining illustrations are with 'screen' being the login shell and four windows starting up via the .screenrc file with bash running in each window. This is using the 990809 snapshot with "tty" set. My comments are in parenthesis. I'm starting 'screen' from "cygnus.bat". (The status line at bottom of display does not disappear and the prompt for the last window does not appear. I press RETURN, the status line disappears but still no prompt. I press RETURN a second time, a prompt appears.) BASH-2.03$ (I press RETURN a third time, no change. I press RETURN a fourth time, two more prompts appear.) BASH-2.03$ BASH-2.03$ BASH-2.03$ (I press "p", no change. I press "s", two more prompts appear.) BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ (I press RETURN, no change. I press RETURN again, "ps" appears and the title changes to "ps" and back to "screen".) BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ ps (I press RETURN, no change. Press RETURN again, I get a partial display of the output of 'ps'.) BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ ps PID TTY STIME COMMAND 1000 0 19:47:57 /BIN/SCREEN.EXE 1001 -1 19:47:57 /BIN/SCREEN.EXE 1002 1 19:47:58 /USR/BIN/BASH.EXE 1003 2 19:47:59 /USR/BIN/BASH.EXE 1004 3 19:48:00 /USR/BIN/BASH.EXE 1005 4 19:48:01 (Press RETURN again, the rest of the output of 'ps' appears plus an additional two prompts.) BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ BASH-2.03$ ps PID TTY STIME COMMAND 1000 0 19:47:57 /BIN/SCREEN.EXE 1001 -1 19:47:57 /BIN/SCREEN.EXE 1002 1 19:47:58 /USR/BIN/BASH.EXE 1003 2 19:47:59 /USR/BIN/BASH.EXE 1004 3 19:48:00 /USR/BIN/BASH.EXE 1005 4 19:48:01 /USR/BIN/BASH.EXE 1006 4 19:52:50 /USR/NEW-WINSUP/BIN/PS.EXE BASH-2.03$ BASH-2.03$ (Press RETURN, no change. Press RETURN again, three more prompts appear. From now on, it takes two presses of RETURN to produce a change and the change is, two prompts appear.) -glenn -- ) Glenn Spell ) _ _____ ) Fayetteville, North Carolina, U. S. A. )_ (__\____o /_/_ | ) _ _ _ _ _ _ _ _ _ _ _ _ _ _ ) >-----._/_/__]> )- blue skies - happy trails - sweet dreams -) `0 |