I just noticed with current SVN that Ctrl-U doesn't work, because it
depends on CONFIG_FEATURE_EDITING_FANCY_KEYS.
As Ctrl-U is a feature that works even without line editing, I consider
that strange. Especially because Ctrl-W, which is also present without
line editing, is always enabled.
As a side note, input of characters with codes above 128 works now, and
input of control characters with Ctrl-V also works, but control
characters are output directly and not in readable form.
With Readline:
echo ^[[2J
With BB:
echo { Screen erased while typing }
But considering the scope of BB it is reasonable to leave it as it is.
Regards
Ralf Friedl
Paul Fox wrote:
> i noticed a while ago that it was impossible to type a TAB
> character on the ash commandline. by comparison, gnu readline
> allows prefixing any character with ^V to force insertion of the
> character -- this is now i normally enter a TAB when using bash.
> there was code in lineedit.c to allow this, but it was ifdefed
> out along with unrelated features. i've re-enabled it
> (unconditionally). along with the fix for 8-bit characters, i
> think it's now possible to enter any character (with the possible
> exception of NULL) at the commandline.
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
