Closed ramonmi closed 1 month ago
Hello @ramonmi,
@retorquere
is ready to assist you with Better BibTeX. In order to do so efficiently, a debug log is generally required. The information it containst is key to him understanding, replicating, and resolving your issue.
Here’s how you can share your debug log:
After these steps, you will receive debug ID displayed in red. Please share this ID with @retorquere
in this issue thread. If your query is about an export, include both the actually exported result and your expected/desired outcome.
Sharing your debug log gives @retorquere
a view of your Better BibTeX configuration and the elements contributing to the issue. This helps him address your concerns more efficiently.
Thank you.
PS: If the Debug Log menu is not available, or if it fails to send the debug log, you can use the option under “Help” > “Send debug log to file.io”.
This row appears in the first seconds after start-up, and disappears soon.
This is by design. If BBT starts up normally, it disappears. Should BBT have a problem starting up, it remains, so that an error log can be sent to diagnose the startup problem
BTW, there are duplicated Send Better BibTex debug log... functions in the help submenu and Tools/Better BibTex
People had trouble locating the one under tools and kept sending me Zotero debug log IDs.
Thanks for your quick reply. I see.
Debug log ID
None
What happened?