Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.2.0.14.0.20041209223744.053a4eb8@pop.prospeed.net> Date: Thu, 09 Dec 2004 22:42:19 -0500 To: "Ben Wing" , From: Larry Hall Subject: Re: Bad interaction -- alternate console buffer and console history In-Reply-To: <00c801c4de66$a3754aa0$210110ac@NEEEEEEE> References: <00c801c4de66$a3754aa0$210110ac AT NEEEEEEE> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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>. -- 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/