Bob Swift

> My only concern is that I had thought after our recent discussion that we might get completely rid of the dateutil dependency. Oh right. I forgot about that. >...

> Nah, you don't need the quotes, unless the path contains spaces (which is an expected behavior imo) I agree that is the expected behavior. Having said that, do we...

> * If there is no running instance, nothing will happen, as picard -e blocks Picards startup In this case, would it make sense to start an instance and process...

> * If there is an existing instance, picard -e will send all the positional arguments in the given order. Then the commands. So yeah, you are right, all files...

> In that case we have to either redesign the argstring handling or allow only one file per LOAD (like in REMOVE), because paths can contain spaces At the risk...

> Take for example: `picard -e QUIT`. Would it make sense to start Picard only to quit it? Actually, I believe that it would make sense because it would allow...

One final (?) item... I see that we have a `SAVE_COMPLETE` command to save fully matched releases, but nothing for saving partially matched releases which are quite common when the...

Sorry, but I just thought of another potential command (enhancement), that being the ability to read the commands from a text file. Perhaps the command could be called `BATCH` or...

> > One final (?) item... I see that we have a `SAVE_COMPLETE` command to save fully matched releases, but nothing for saving partially matched releases which are quite common...

It was a fairly easy change, so I added the option to use regular expressions for the match strings. This is disabled by default.