Help with command line

[shotsky]

I use the command line in a program to convert ebooks. While I can get ONE option to work, I cannot seem to get any additional options to function, such as adding input and output profiles.

In the manual, these are described with double dashes followed by single dashes, with some commas thrown in for giggles. How about a complex command line that actually works. If I can SEE a working command line, I can program one like that, but I've spent HOURS trying variations, with few results.

I am able to convert ebooks and create a debug folder, but at this point, I can't seem to add ANY other commands. And, while I'm at it, how in the HELL can I get it to stop splitting the files into separate files, when all I want is one big html file in the debug folder? Sometimes, I get a debug-raw.html file, which is what I want, but more often, I don't get that, but do get a folder full of html files.
Thanks,
John

[DoctorOhh]

Originally Posted by shotsky

In the manual, these are described with double dashes followed by single dashes, with some commas thrown in for giggles.

I understand your frustration, but no commas are thrown in for giggles.

Originally Posted by shotsky

How about a complex command line that actually works.

Here is one example I found in calibre's user manual.

[theducks]

--fields, -f

    The fields to display when listing books in the database. Should be a comma separated list of fields. Available fields: author_sort,authors,comments,cover,formats,identifiers,isbn,last_modified,pubdate,publisher,rating,series,series_index,size,tags,timestamp,title,uuid Default: title,authors. The special field “all” can be used to select all fields. Only has effect in the text output format.

The first line (the switch) is an either or choice Use the Red or use the Green.. Not both

calibredb list  -f author_sort,title,isbn,last_modified --sort-by series

[shotsky]

Originally Posted by dwanthny

I understand your frustration, but no commas are thrown in for giggles.



Here is one example I found in calibre's user manual.

Thank you. I spent a lot of time looking for such an example, but guess I missed the example in comic books. I really didn't expect that the double dash was really intended, and when I did try it, I must have had something else that was not perfect. Altogether, a very frustrating day, since sample working lines were simply not easily located, searching through the manual or this group. In fact, I used Google looking for sample working command lines, and never found more than one option used at a time.

I think the command line section should have several more examples, especially where all the default options are over-ridden by the command line.

Again, thanks, this is what I needed, I just coudn't find it.
John

[shotsky]

Originally Posted by theducks

--fields, -f

    The fields to display when listing books in the database. Should be a comma separated list of fields. Available fields: author_sort,authors,comments,cover,formats,identifiers,isbn,last_modified,pubdate,publisher,rating,series,series_index,size,tags,timestamp,title,uuid Default: title,authors. The special field “all” can be used to select all fields. Only has effect in the text output format.

The first line (the switch) is an either or choice Use the Red or use the Green.. Not both

calibredb list  -f author_sort,title,isbn,last_modified --sort-by series

I take it then, that no spaces are used between options. The problem I have is that it is not clear how to separate options, what tags start new options. I can't believe how many things I tried that didn't work. Maybe the software could detect an attempt at something such as -'input-default' and either suggest the correct format, or just USE it and do the correct thing? Software that simply refuses to funtion, or tells you 'you are stupid, you did it wrong' without telling you what is right, is just a waste. I have spent many hours trying to figure out the secret to command lines, when it would have been so simple to document it in the first place, and even easier to recognize correct commands with incorrect leadins or separations and either do the right thing, or tell the user what the hell is wrong.
John

[Manichean]

Originally Posted by shotsky

Maybe the software could detect an attempt at something such as -'input-default' and either suggest the correct format, or just USE it and do the correct thing? Software that simply refuses to funtion, or tells you 'you are stupid, you did it wrong' without telling you what is right, is just a waste.

Having done quite a bit of user input parsing in the past few years, I can tell you that it's very nontrivial to find where syntax errors in user input are, let alone correct them. You have to keep in mind that there are at least as many ways to make an error in a given input as there are users of the software. As for correcting the error, the software would have to know the intention of the user. I believe it's better do do nothing and error out than have the software do something the user didn't want it to do and potentially break data in the process.

[theducks]

Originally Posted by shotsky

I take it then, that no spaces are used between options. The problem I have is that it is not clear how to separate options, what tags start new options. I can't believe how many things I tried that didn't work. Maybe the software could detect an attempt at something such as -'input-default' and either suggest the correct format, or just USE it and do the correct thing? Software that simply refuses to funtion, or tells you 'you are stupid, you did it wrong' without telling you what is right, is just a waste. I have spent many hours trying to figure out the secret to command lines, when it would have been so simple to document it in the first place, and even easier to recognize correct commands with incorrect leadins or separations and either do the right thing, or tell the user what the hell is wrong.
John

1 space between each option (switch), 1 space to the first argument after the switch, commas with no space for additional values.
quote each argument value with spaces: "two words","three small words",word
pretty much common CLI (MSDOS uses a colon after the switch that has values

xcopy  /EXCLUDE:file1[+file2][+file3]

and chains them with a +)