Peter Harris

...I thought I left the following comment earlier, but I must have forgotten to press the Comment button: In addition to the above, your suggested change breaks anyone who has...

> I agree that backward compatibility should be kept. Thus perhaps a new constructor could be added that takes the input / output streams to be used. This seems like...

Print the available options? How? I think I need a bit more detail to fully evaluate this proposal. Printing multiple options probably needs multiple lines, and liner isn't likely to...

I'm still having difficulty visualizing how the proposed multiple options would appear. How do you plan to implement temporary-overstrike-mode? Do you plan to use some sort of delimiter so the...

> then from here on it is business as usual. Assuming you mean "behave as if tab was pressed after every keystroke": That would make it impossible to type a...

Interesting suggestion. I was not aware of bracketed paste mode. I'm not quite sure what to do with bracketed paste mode. Certainly tabs should not be allowed as literal characters...

The last time we needed more features, we upgraded `Completer` with `WordCompleter`. This time, it probably makes sense to upgrade `WordCompleter` to `PosCompleter` Something like ```go type WordAndPos struct {...

"Move word back" and "set to end" are redundant when you have "set position". I especially want to avoid things like "move word back" when "word" is so poorly defined...

I don't know if I like that more or less than PosCompleter. As they say, there are only two hard things in programming: Naming, Caching, and off-by-one errors. You're doing...

Please don't worry about spam. Thank you for taking the time to create multiple patches for discussion. While looking at your previous patch, I noticed that `bash` treats punctuation differently...