Re: comint-insert-input on non-command lines: A trivial fix, a quibble, and a bug

[Luc Teirlinck]

>From my previous response:

   Yes, but if comint-use-prompt-regexp is t, then comint-insert-input
   does nothing even if point _is_ over input.

On closer inspection, what seems to cause this bug is that
comint-insert-input contains:

    (if (not (eq (get-char-property (point) 'field) 'input))
    ;; No input at POS, fall back to the global definition.

If comint-use-prompt-regexp is non-nil, then there are no field
properties, so, despite what the comment claims, that condition does
_not_ assure that there is no input at POS.

Sincerely,

Luc.