delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
From: | "Ben Wing" <ben AT 666 DOT com> |
To: | <cygwin AT cygwin DOT com> |
Subject: | Bad interaction -- alternate console buffer and console history |
Date: | Thu, 9 Dec 2004 21:16:27 -0600 |
Message-ID: | <00c801c4de66$a3754aa0$210110ac@NEEEEEEE> |
MIME-Version: | 1.0 |
I apologize if this is a FAQ. One of the clever features of the `cygwin' TERM type is that programs like `man' and `more' and others switch to a secondary screen buffer, so that when you exit the program, you get back the original buffer, uncluttered by the program's output. Unfortunately, this interacts extremely badly with the console history -- all console history is erased as soon as the secondary screen is invoked. Any plans to fix this? This is under W2k if it matters. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |