[Divingduck]

Hi Kovid,
I have a question to options and global options. Is there a fix sequence what need to be declared first between normal and global options? I came to this during the cli translations and tests for this.

I did some tests and struggled with the global options what ends with a notice, that I am doing something wrong (but no good tip where I have to look for). In the end I fix my problem, but it take some time to understand what was going on.

Here the example:

Global options at the beginning:

calibredb --library-path="d:\Test-DB" list --separator=";" >Booklist.txt
ends up with an error

The same, but now the global option at the end:
calibredb list --separator=";" --library-path="d:\Test-DB" >Buchliste.txt
works well.

It is maybe a good thing to make a remark in the documentation to this, if there is a fix sequence between global and normal options.

An other point I found is regarding the option --line-width. Something is maybe wrong with the line length calculation. Is there an offset in? Pls take a look in the example attached (book-id 10313). The total line length should be 68/67 including the book-id. I can prevent a line break only with line-width >=129.

Some thoughts: I am missing an option for fields w/o filling spaces at the end of a field and use this in combination with line-width and the opposite one with a fix field-width. Then you have both, in combination with fixed and variable field-length w/o line break.

Best regards,
Armin