Re: why the Up key doesn't work to go through the searching history

thank you for your advices.

I checked what you suggested.
1) The return for :echo has('cmdline_hist') is 1.
2) the answers to :set cp? history? are
nocompatible
history=50
it seems that the problem doesn't come from
these issues. and the Ctrl-p and Ctrl-n work.

On 4月7日, 下午8时37分, Tim Chase <v...@tim.thechases.com> wrote:
> On 04/07/2011 10:04 AM, wxuyec wrote:
>
> > while it works for gvim and the command mode.
> > after I press /, when I want to use Up key to
> > go through the searching history, I get a character
> > A inserted.
>
> In addition to Tony's good advice, it would also be worthwhile to
> check that (1) you've got a build with command-line history
> enabled and (2) that you have some history to recall
>
> For #1, issue
>
> :version
>
> and check for "+cmdline_hist" or verify that
>
> :echo has('cmdline_hist')
>
> returns 1. If it's not built with cmdline_hist, you're likely
> running a stripped down "vim tiny" version and you may want to
> run/install/build a fuller-featured vim.
>
> For #2, if you started Vim in compatible mode, the 'history'
> setting defaults to 0 which means no history is maintained.
> Check your value for 'history' to make sure it's >0
>
> :set cp? history?
>
> You can override that setting.
>
> Finally, if your term settings aren't detecting your <up> arrows,
> you should be able to use control+P instead (and control+N in
> place of <down>).
>
> -tim

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php