question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Info v.s. Debug output

See original GitHub issue

It seems that Feedback.msg_debug messages go to the Debug “view” of the Output tab, while Feedback.msg_info go to the Info “view”.

I’ve two problem with this:

  • the two class of messages are decorrelated by this presentation: a debug message may arrive before or after an info one, and you don’t know
  • at least in my setup, the Debug “view” takes precedence over the Info one and this is bothering me on normal use: if there is anywhere a debug message, then the infos are not shown (you need to click after every interaction with Coq).

I can imagine two improvements:

  • an option to merge the two views (or merge then and have an option to hide/show debug stuff)
  • make the user choice about the preferred view take priority over the last-updated view

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:1
  • Comments:5

github_iconTop GitHub Comments

1reaction
maximedenescommented, Sep 19, 2019

After some offline discussion, we agreed that two improvements could be made:

  • Output generated by commands in the document should be attached to their location of origin.
  • Some specific views may be needed for trace-like information
  • The output panel should not be used much for standard activities, maybe just for debugging
0reactions
Blaisorbladecommented, Oct 18, 2019

We discussed this on gitter, and we seemed to agree a temporary measure meanwhile could be nice. Also for old Coq versions!

We also debated (but didn’t reach agreement) on whether "X is definedshould indeed be Info-only, sinceXmight not appear in the source, e.g.Inductive foo := .generatesfoo_ind` etc. But that’s a separate question anyway, and I’m not so sure myself.

EDIT: Also, for now I’m happy reverting #35 locally.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Log.INFO vs. Log.DEBUG [closed] - Stack Overflow
DEBUG: Information interesting for Developers, when trying to debug a problem. · INFO: Information interesting for Support staff trying to figure out the...
Read more >
Logging Levels: What They Are & How to Choose Them
A log level or log severity is a piece of information telling how important a given log message is. It is a simple,...
Read more >
Sending Text to the Debug Output Window - Microsoft Learn
To see the debug output window, in Microsoft Visual Studio, click View, click Other Windows, and then click Output.
Read more >
What is the difference between logger.debug and ... - Quora
The INFO level designates informational messages that highlight the progress of the application at coarse-grained level. DEBUG. public static final Level DEBUG.
Read more >
Tip: Use Logging Levels Consistently - Reflectoring
When searching for a bug, or just trying to get a feel for an ... It's harder for to define what information to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found