We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the default logger (in the REPL), you can use the JULIA_DEBUG ENV variable to control the display of @debug logs: https://docs.julialang.org/en/v1/stdlib/Logging/#Environment-variables We should also support this feature in our custom PlutoLogger.
JULIA_DEBUG
@debug
The default implementation is here: https://github.com/JuliaLang/julia/blob/6c2410361a6e413652ed89fb206d4dc6c2af89c9/base/logging.jl#L542 This looks pretty complicated, but maybe there is a way to call this mechanism directly from our code. It might be worth investigating how https://github.com/JuliaLogging/TerminalLoggers.jl did it.
The text was updated successfully, but these errors were encountered:
This would also fix #2487
Sorry, something went wrong.
No branches or pull requests
With the default logger (in the REPL), you can use the
JULIA_DEBUG
ENV variable to control the display of@debug
logs: https://docs.julialang.org/en/v1/stdlib/Logging/#Environment-variables We should also support this feature in our custom PlutoLogger.The default implementation is here: https://github.com/JuliaLang/julia/blob/6c2410361a6e413652ed89fb206d4dc6c2af89c9/base/logging.jl#L542 This looks pretty complicated, but maybe there is a way to call this mechanism directly from our code. It might be worth investigating how https://github.com/JuliaLogging/TerminalLoggers.jl did it.
The text was updated successfully, but these errors were encountered: