From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q92LpWWU090683 for ; Tue, 2 Oct 2012 16:51:32 -0500 Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by cuda.sgi.com with ESMTP id BZcYBGZWGHTDUZwG for ; Tue, 02 Oct 2012 14:52:55 -0700 (PDT) Date: Wed, 3 Oct 2012 07:52:53 +1000 From: Dave Chinner Subject: Re: Why xfs_ not 'readline' w/line-edit & history enabled? Message-ID: <20121002215253.GT23520@dastard> References: <506B1A03.7030600@tlinx.org> <20121002201748.GQ23520@dastard> <506B5DE1.4020000@tlinx.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <506B5DE1.4020000@tlinx.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Linda Walsh Cc: xfs-oss On Tue, Oct 02, 2012 at 02:34:25PM -0700, Linda Walsh wrote: > > > Any reason these default to 'no'?? > > --enable-readline=yes/no Enable readline command editing default=no > --enable-editline=yes/no Enable editline command editing default=no > --enable-termcap=yes/no Enable terminal capabilities library default=no Lost in the mists of time, I suspect. Given that we use a configure script, I'd guess that this could easily be detected at configure time. Patches welcome. Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs