| To: | Linda Walsh <xfs@xxxxxxxxx> |
|---|---|
| Subject: | Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled? |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 3 Oct 2012 07:52:53 +1000 |
| Cc: | xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <506B5DE1.4020000@xxxxxxxxx> |
| References: | <506B1A03.7030600@xxxxxxxxx> <20121002201748.GQ23520@dastard> <506B5DE1.4020000@xxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| Previous by Date: | -Blastin Wax-New Benga, Danny Lifted, System of a Down, Funtcase, Blastinwaxx6 |
|---|---|
| Next by Date: | Re: OOM on quotacheck (again?), Dave Chinner |
| Previous by Thread: | Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled?, Linda Walsh |
| Next by Thread: | Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled? (+attachment), Linda Walsh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |