I think it would be advisable to generate an output text according to whether or not there have been errors in the acquisition process. By this I mean, in case no metadata was found, to indicate with an output error 1 that the program has failed. Currently in Linux at least, it can be seen that the execution code remains at 0, i.e. there have been no problems or errors.
Another example of use is when the -clip argument is added to copy to the clipboard, even if no metadata could be found, it still prints All bibtex entries found in will be copied into the system clipboard, which leads the user to think that something could be found but in fact it was not. Also, the error/problems text should be printed to the standard error output and not to the standard error.
I think it would be advisable to generate an output text according to whether or not there have been errors in the acquisition process. By this I mean, in case no metadata was found, to indicate with an output error
1
that the program has failed. Currently in Linux at least, it can be seen that the execution code remains at0
, i.e. there have been no problems or errors.Another example of use is when the
-clip
argument is added to copy to the clipboard, even if no metadata could be found, it still printsAll bibtex entries found in will be copied into the system clipboard
, which leads the user to think that something could be found but in fact it was not. Also, the error/problems text should be printed to the standard error output and not to the standard error.Can I make a PR to contribute in this part?