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

[Luc Teirlinck]

Nick Roberts wrote:

   Again the name comint-copy-old-input doesn't suggest this behaviour and
   my preference would be not to have it.

Motivating the behavior of a function from its name seems backward.
One could always rename it to something like `comint-use-old-as-input'
or whatever.

There also is the possibility of keeping both comint-copy-old-input
(maybe renamed) and comint-insert-input (_without_ the latest
adaptation to non-nil comint-use-prompt-regexp).

`C-c RET' would then be bound to comint-copy-old-input by default and
mouse-2 to comint-insert-input (if comint-use-prompt-regexp is nil)
and one could tell people in the docs that if they prefer to have
`C-c RET' behave like mouse-2, they can rebind it to
comint-insert-input using comint-mode-hook.  Even when used on input,
there can be a difference in certain modes, such as Inferior Lisp mode.

Sincerely,

Luc.