yikes, a destructive manifestation of the same bug:
If a list of files is given with the --overwrite option, it actually
clobbers one file with the output of the other.
hmm.. actually I've misunderstood the man page:
--overwrite
Allow overwriting existing files. Otherwise the program terminates
with an error if an output file to be written already exists.
I thought "overwrite" meant to overwrite the source doc, not that it was
okay to overwrite the 2nd in a list. So in the end this may just be a
documentation problem. I suggesting making the docs more clear. I
believe this is incorrect BNF:
unpaper [options] {input-pattern output-pattern | input-file(s)
output-file(s)}
braces are invalid BNF; they should be parenthesis, and there should be
angle brackets like this:
unpaper [options] (<input pattern> <output pattern> | <input file(s)>
<output file(s)>)
then the non-obvious things in angle brackets should be defined
separately, like pattern. Patterns come in many forms. I tried giving
'*.pgm' as a pattern and it was rejected.
Also, I suggest an "--in-place" option of sorts so users can operate
directly on the source and not give an output file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921628
Title:
unpaper: error: no input or output files given.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unpaper/+bug/1921628/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
