From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Feb 10 15:50:08 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 645A916A420 for ; Fri, 10 Feb 2006 15:50:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF83C43D46 for ; Fri, 10 Feb 2006 15:50:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1AFo71S096903 for ; Fri, 10 Feb 2006 15:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1AFo7A1096902; Fri, 10 Feb 2006 15:50:07 GMT (envelope-from gnats) Date: Fri, 10 Feb 2006 15:50:07 GMT Message-Id: <200602101550.k1AFo7A1096902@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: trasz@pin.if.uz.zgora.pl Cc: Subject: Re: ports/92817: ksh93: history does not work X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: trasz@pin.if.uz.zgora.pl List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2006 15:50:08 -0000 The following reply was made to PR ports/92817; it has been noted by GNATS. From: trasz@pin.if.uz.zgora.pl To: Joe Kelsey Cc: bug-followup@FreeBSD.org Subject: Re: ports/92817: ksh93: history does not work Date: Fri, 10 Feb 2006 16:48:35 +0100 On 0208T1552, Joe Kelsey wrote: [..] > I cannot reproduce your problem report from the information provided. > If you want me to spend more time researching this problem, then I need > more information, such as your current environment (env command), your > current .profile and your current ENV file. thanks for the environment hint. the reason for history not working was $HISTSIZE set to enormously big value. so, this was indeed user error. sorry for the noise.