Making it simpler to start using linecomp

[nkh]

Hi, thank you for linecomp, I think it's a good idea.

• make it clear in the docs that having "set -o vi" is going to stop everything from working
• maybe start with a default inputrc, mine groaked with an error
• some baseline where it would be useful as is and not be disturbed by watever the user has for config

first thing I got what a line that accepted no input

then return would display multiple line

then it worked better, why ? I can't guess

completion worked for options but not for file

...

Could you please add a "start clean" mode, even if that mode reflect how you use it? And add some documentation?

I can probably find time to hel with the readline vi-* functions

[armoar334]

Thanks for the feedback! (and sorry i took so long to respond)
Im aware of the weird first command thing, it keeps coming back between different commits so im not sure what the actual cause is.
As for vi-mode stuff, I wouldnt recommend starting that now (if you were still interested in doing so of course) as I plan to do a pretty big rewrite of the main functions to get rid of some nasty stuff like external calls to grep and ideally make it easier to implement stuff like modes, as right now the prompt still acts as if emacs mode is active 100% of the time, not only in vi mode but also when emacs mode is off. Hopefully me doing that should also get rid of the empty line bug.

[nkh]

Then I'll wait for the re-write. please let me know when you have something to test.