From: Eric Sandeen <sandeen@sandeen.net>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled?
Date: Tue, 02 Oct 2012 21:06:16 -0500 [thread overview]
Message-ID: <506B9D98.6040808@sandeen.net> (raw)
In-Reply-To: <506B5CA0.7050306@tlinx.org>
On 10/2/12 4:29 PM, Linda Walsh wrote:
>
>
> Dave Chinner wrote:
>> $ sudo xfs_db -r /dev/vdb
>> xfs_db> inode 128
>> (reverse-i-search)`in': inode 128
> ----
> Um...When I press up-arrow, I get nothing.
>
> When I press down arrow -- also nothing.
>
> Try hitting home for beginning of line --
> nothing. Tried ESC to re-edit line -- nothing. (enters ^[).
>
> What are you typing to get the above? does it require a config somewhere?
Do you build your own pkgs or use a distro? IF distro, I'd file a bug.
Agreed that defaulting to on would be nice, but in Fedora & RHEL:
%configure \
--enable-readline=yes \
...
just FWIW.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-03 2:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 16:44 Why xfs_<utils> not 'readline' w/line-edit & history enabled? Linda Walsh
2012-10-02 18:41 ` Kinzel, David
2012-10-02 20:17 ` Dave Chinner
2012-10-02 21:29 ` Linda Walsh
2012-10-03 2:06 ` Eric Sandeen [this message]
2012-10-03 2:16 ` Nathan Scott
2012-10-03 3:51 ` Linda Walsh
2012-10-03 3:58 ` Nathan Scott
2012-10-03 4:21 ` Linda Walsh
2012-10-04 12:12 ` David Disseldorp
2012-10-02 21:30 ` Linda Walsh
2012-10-02 21:34 ` Linda Walsh
2012-10-02 21:52 ` Dave Chinner
2012-10-02 22:52 ` Why xfs_<utils> not 'readline' w/line-edit & history enabled? (+attachment) Linda Walsh
2012-10-02 23:14 ` Dave Chinner
2012-10-02 23:34 ` Linda Walsh
2012-10-02 23:50 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506B9D98.6040808@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.