This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Bad interaction -- alternate console buffer and console history
- From: Larry Hall <lh-no-personal-replies-please at cygwin dot com>
- To: "Ben Wing" <ben at 666 dot com>, <cygwin at cygwin dot com>
- Date: Thu, 09 Dec 2004 22:42:19 -0500
- Subject: Re: Bad interaction -- alternate console buffer and console history
- References: <00c801c4de66$a3754aa0$210110ac@NEEEEEEE>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
At 10:16 PM 12/9/2004, you wrote:
>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.
Based on the information you've provided so far:
# history
104 ls
105 cat ~/.bashrc
106 q
107 hisory
108 history
# man ls
# history
106 q
107 hisory
108 history
109 man ls
110 history
If this isn't what you see, perhaps you want to check out
<<http://cygwin.com/problems.html>http://cygwin.com/problems.html>.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
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/