jarro2783

Yeah I guess having multiple files is not so bad. I'll look at this after some of the other changes because it will mess up PRs.

I think in bash that is actually being expanded to `--pattern=-1.5 --pattern=-0.5` etc. There is a parser in the code that splits a string up by a delimiter, default `,`....

That doesn't look right. I'll take a look. What do you mean by "unformatted"?

I think part of the problem is that I never designed this thinking that users would put their own new lines in the help description. I generally intended the help...

#215 was recently merged that allows new lines and does tab expansion. Can you have a look at that and see if it helps?

That code has a few issues like that. I'll have to go over it and try to write it in a way that doesn't produce those warnings.

I think the warnings caused by `-Wconversion` can be very noisy and produce a lot of problems. In these cases I don't think there is an actual problem. In fact...

I think this is fixed on master.

The reason that `newfile` ends up in positional arguments is because --dump-job has an implicit parameter. There were a few issues previously with confusion about implicit parameters and assumptions about...

Ok I remember now, you have to use the long option with `=`.