You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is annoying when adding bib entries to a bib file, e.g. rfcbibtex draft-ietf-httpbis-rfc6265bis >> specs.bib, because the warning ends up in the bib file.
The text was updated successfully, but these errors were encountered:
SECtim
added a commit
to SECtim/rfc-bibtex
that referenced
this issue
Jan 2, 2024
The utils.print_x functions take a `file` argument that was not used in their implementation.
This lead to errors and warnings being printed to stdout instead of stderr.
Fixesiluxonchik#33
Thank you for your creating the issue and submitting a merge request. I will review it soon. From a quick check, your observation and code change seems valid. I'll just make sure that that doesn't break anything, and then work it into a release.
The README says
However, this is not the case. For example,
rfc-bibtex/rfc_bibtex/rfc_bibtex.py
Lines 127 to 129 in 84bca57
seems to print to stderr, but doesn't:
rfc-bibtex/rfc_bibtex/utils.py
Lines 9 to 10 in 84bca57
This is annoying when adding bib entries to a bib file, e.g.
rfcbibtex draft-ietf-httpbis-rfc6265bis >> specs.bib
, because the warning ends up in the bib file.The text was updated successfully, but these errors were encountered: