Chet Ramey wrote:!
It's not attempting command completion, since it doesn't think
it's in a context where a command name is expected (the completion
line parsing is pretty ad-hoc -- it doesn't use the shell parser). It's
attempting readline's default filename completion. I'll have to see
whether it can be taught that this is a context where a command name is
valid, even though it's the second line of a multi-line construct.
---
Well, as it *is* a place where one can type in commands, so you
should slap it up the side the code, and put it in it's place! ;-)
If this is really a big deal, you can temporarily turn off command line
editing while cutting and pasting text into the shell. That way you
won't be surprised.
---
set +o vi?
----
I don't remember this being a problem before.
I've done it before...as I'm writing code, sometimes I want to take
a snippet and test it, so I cut/paste ..
Hasn't been until recently that I noticed this problem.
