Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Designed or bug? Send debug log to file.io -- > Better BibTeX in the help submenu #2955

Closed
ramonmi opened this issue Aug 21, 2024 · 3 comments
Labels

Comments

@ramonmi
Copy link

ramonmi commented Aug 21, 2024

Debug log ID

None

What happened?

  • This row appears in the first seconds after start-up, and disappears soon.
  • BTW, there are duplicated Send Better BibTex debug log... functions in the help submenu and Tools/Better BibTex.
    屏幕截图 2024-08-21 172430
Copy link

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:

  1. If your issue involves specific references, citekey generation, or exports, right-click on the relevant item(s) and select "Better BibTeX -> Submit Better BibTeX debug log" from the menu.
  2. For issues where items do not play a role, follow these steps:
  • Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
  • Reproduce the problem.
  • Choose "Send Better BibTeX debug report..." from the help menu.

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”.

@retorquere
Copy link
Owner

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.

@ramonmi
Copy link
Author

ramonmi commented Aug 21, 2024

Thanks for your quick reply. I see.

@ramonmi ramonmi closed this as completed Aug 21, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants