I'd like an option in the .toc files to pass in a
command line for cdrdao. That way I can encapsulate
all knowledge of what I'm building in the .toc file.
You mean to store all options but not the command ('write',
...) in the toc-file, right?
What should be the precedence if the toc-file and the
actual command line contains option? I'd say the actual
command line of cdrdao should overwrite the options of
the toc-file.
I'll put it on the TODO list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How about: If ANY command line options are specified, the
options in the file are ignored. If you just feed the .toc
file to cdrdao it will work. Or, you're free to give your
own options.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=5517
You mean to store all options but not the command ('write',
...) in the toc-file, right?
What should be the precedence if the toc-file and the
actual command line contains option? I'd say the actual
command line of cdrdao should overwrite the options of
the toc-file.
I'll put it on the TODO list.
Logged In: YES
user_id=122507
How about: If ANY command line options are specified, the
options in the file are ignored. If you just feed the .toc
file to cdrdao it will work. Or, you're free to give your
own options.