Closed drzraf closed 2 months ago
That is what is expected: --output
sets an output file. I believe this is clearly documented, and nowhere is it suggested otherwise.
That's why, for example, it is possible to actually make changes using --runsqlquery
and then write a new backup file with these changes in it.
Not sure what you expected actually, to write the console output to a file? If you want the output of your query, I suggest you simply redirect the output to a file, copy-paste it from your terminal window, or use the --logfile [file]
option to write a log file.
In any case, this is clearly not a bug. Thanks!
Running
--runsqlquery "SELECT * mms WHERE thread_id = 1" --output foobar
or--listrecipients --no-showprogress --output foobar
will not what is expected. Instead of directing the output, it runs the first command then proceeds with a full export stored insidefoobar
.