Kevin Van Brunt

Place your **select** answers in a text file, each on its own line. For instance, answers.txt. ``` 1 2 1 ``` Then run your tests like this: `cat answers.txt |...

@mardy It sounds like you are seeing the same behavior I reported in issue #70. I ended up having to call `unqlite_close()` periodically to work around this.

@tleonhardt The permanent fix needs to be in 2.0. We need a way to support instance-specific parsers and that will most likely be a breaking change.

@anselor Do you have any thoughts on this issue?

@anselor and I agree the 2.0 release does not have to wait for this fix. The risk of someone using two cmd2 objects and editing common parsers between them is...

**run_script** is for basic command scripts, which have no logic. They're no more advanced than running multiple command lines in a row. Great for automation, but not for things which...

Closing since `run_script` is functioning as designed.

I think we'll have to use something like a double pipe `||` to distinguish between piping output to a built-in command and an OS shell command. Lots of thoughts come...

Since the parser is created before the `CommandSet` instance, `type` is pointing at an unbound method. This is the same for tab completion methods like `choice_provider`. Command parsers are basically...

@ddejohn Yes, that is a typo. I've corrected the code now.