Re: C-f in isearch's non-incremental minibuffer edit

[Richard Stallman <rms@gnu.org>]

    But I recently noticed that it behaves very strangely: if I move point
    towards the end with something like C-f, when I reach the end of the
    minibuffer instead of getting the usual beep I see chars from the main
    buffer being added.

    It seems like it's a new "feature", but it looks much more like a bug to me.

I see your point; however, since C-f at the end of the buffer would
otherwise be an error, this feature seems to be harmlessly
upward-compatible.  Does it actually cause trouble or inconvenience,
or was it just surprise?

    While I'm at it, I also suggest we make isearch-edit-string use the usual
    history functionality, so it behaves even more normally.

Could you tell me, at the level of user-visible behavior, how its
currently differs from the usual history functionality?