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.

Sign up for GitHub

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

Jump to bottom

Log file #11

Open
whereswaldon opened this issue Nov 15, 2018 · 2 comments
Open

Log file #11

whereswaldon opened this issue Nov 15, 2018 · 2 comments
Assignees
@jwhett
Labels
enhancement New feature or request

Comments

@whereswaldon
Copy link
Member

Right now, muscadine sometimes emits problems on stderr, which corrupts the TUI. It would be better if it used a well-known log file location instead.

Perhaps $XDG_DATA_HOME/muscadine/muscadine.log?

All that is needful is tweaking the settings for the log package right now. Maybe a corresponding tweak to arbor-go because it actually logs errors from the MakeMessageWriter and MakeMessageReader.
@whereswaldon whereswaldon added the enhancement New feature or request label Nov 15, 2018
@jwhett
Copy link
Contributor

jwhett commented Dec 4, 2018

perhaps all logging goes to a debug buffer instead of a persistent log file

@jwhett jwhett self-assigned this Dec 4, 2018
@whereswaldon
Copy link
Member Author

We now have a log file from #70, but it would be great to have it visible in the TUI as well (some special keybinding, maybe d or D?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jwhett jwhett

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whereswaldon @jwhett