OK, well I'm still working on 2008.10, so things may be different there.

in hush I can see 2 references to CONFIG_FEATURE_COMMAND_EDITING which is NOT defined in my set-up

elsewhere I see #define CONFIG_CMDLINE_EDITING 1 /* add command line history */

which I have now added in to the .h file for my board - it wasn't in the ATNGW100 file I started from.

and I have command history going, and it's wonderful :-)

-------------

All of which is lovely, but the behaviour I commented on is still odd - command line parsers shouldn't accept unprintable chars and then complain about them in an unprintable way.

David

In article 20091023093207.5B570E398E1@gemini.denx.de, wd@denx.de (Wolfgang Denk) wrote:

*From:* Wolfgang Denk wd@denx.de *To:* from_denx_uboot@dexdyne.com *CC:* u-boot@lists.denx.de *Date:* Fri, 23 Oct 2009 11:32:07 +0200

Dear "David Collier",

In message <memo.20091023095756.2092I@postmaster+dexdyne.com.cix.co.uk> you wrote:

...

my u-boot doesn't react well to my hitting the up-arrow key in puTTY.

When I do it ( hoping for cxommand repeat ) it moves the arrow iup and down - but u-boot notices the chars, and barfs any command I then type

Can I fix this in u-boot or by changing the putty session setting to emulate something else :-) ?

Maybe CONFIG_COMMAND_HISTORY is not enabled at all in your board configuration?

Best regards,

Wolfgang Denk

-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "If God had wanted us to use the metric system, Jesus would have had 10 apostles."

David Collier

www.dexdyne.com