--debug (or new option) write to console (stdout (and/or stderr))
Enables debug output for orca and sends all debug output to a file with a name of the form 'debug-YYYY-MM-DD-HH:MM:SS.out' in the current directory. The YYYY-MM-DD-HH:MM:SS portion will be replaced with the current date and time.
Enables debug output for orca and sends all debug output to the given filename.
I find this quite strange, surprising. The only application I know so far doing that.
If not a great effort... Could you please consider making
--debug write to console (stdout (and/or stderr))? Or adding another parameter for that?
--debug-file=/dev/console but that didn't work.
If I use
--debug a few times I end up with a lot
.out files. Then I easily forget which one was which.
I am used to watch debug logs in console. For example, let the application startup, write a lot log which is irrelevant for what I am testing. Then wait for application to be idle. Then press the enter key many times to make a visual distinction between the irrelevant log and the action I am going to take and interested in seeing what debug output that would generate. This is even more important with orca because if I used two console tabs when switching from one console tab to another generates more debug output which makes finding out what I was actually looking for harder.
That would also allow the usual Linux workflow with bash redirections
orca --debug &> mydebugfile.