From: Kamesh K S <kamesh@signal-networks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Up-arrow and Down-arrow related Query
Date: 01 Feb 2007 10:29:39 +0000 [thread overview]
Message-ID: <1170325780.1594.9.camel@Kamesh> (raw)
In-Reply-To: <20070112165244.B344B353BC5@atlas.denx.de>
Hi ALL,
I went thru' the latest 1.1.6 code and found that
History command and various other command line
editing options can be enabled using the
CONFIG_CMDLINE_EDITING macro. But it does not
support command completion.
The CONFIG_AUTO_COMPLETE macro allows command
completion but that does not work in tandem with History
and other cmd line editing options(only very few cmd line
edit option work).
readline() has few cmd edit options along with command
completion.
cread_line() has many cmdline editing features available,
but command completion option is not supported.
How do we make both of them work in in u-boot environment
togather ?
Or am I missing anything ?
Thnx in Advance
Kamesh
On Fri, 2007-01-12 at 16:52, Wolfgang Denk wrote:
> In message <1168625193.1678.23.camel@Kamesh> you wrote:
> >
> > I'm using u-boot for our custom board.
> > We are customizing the Cmd Line interface of U-Boot
> > to suit our needs.
>
> Start trying to understand what's already present...
>
> > The Up-Arrow & Down-Arrow keys don't function the way
> > they do in Bash Shell prompt.
>
> Umm... it seems you are somewhat confused about functions of the
> terminal emulation running on your host computer and the imput
> processing in U-Boot.
>
> In the standard configuration, there is no such thing as "Up-Arrow"
> or "Down-Arrow" keys - U-Boot is reading a character stream, and tere
> is no such characters in the usedC (= ASCII) character set.
>
> However, you can enable command completion, commandline editiong and
> history functions by enabling these in your board configuration.
> Then, and only then, will U-Boot respond to certain character
> sequences.
>
> > The Up-Arrow takes the cursor up the screen thru the previous
> > prompt lines. Where is this Up-Arrow functionality defined ?
>
> In the terminal emulation program running on your host system. U-Boot
> is just echoing the characters in your input.
>
> > I chkd the readline() function in common/main.c, but that does
> > not take care of Up & Down arrows in Switch - Case stmts.
>
> It does not ven know that such things might exist.
>
> > I need to know where the Up and Down arrow key press
> > functionalities are defined.
>
> You repeat yourself.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Quote from a recent meeting: "We are going to continue having these
> meetings everyday until I find out why no work is getting done."
>
next prev parent reply other threads:[~2007-02-01 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 18:06 [U-Boot-Users] Up-arrow and Down-arrow related Query Kamesh K S
2007-01-12 16:52 ` Wolfgang Denk
2007-02-01 10:29 ` Kamesh K S [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-12 13:28 Martijn de Gouw
2007-01-12 17:19 ` Timur Tabi
2007-01-12 17:34 ` Wolfgang Denk
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=1170325780.1594.9.camel@Kamesh \
--to=kamesh@signal-networks.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox