-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The messages bar is missing? #280
Comments
Hey @brando90, I've noticed that you're used to cross-posting the same questions on multiple channels, but this is not a recommended practice as this makes it harder for others to follow the discussion. Most people are active on all these channels, so they will see all your messages and will decide to answer here or there and other people won't see their answers. So for instance, if you are sure that something is a bug, then you should report it only in the proper bug tracker. But if you are not sure, then you should only use Discourse or Zulip to ask whether it is a bug, and if people tell you it is, then open an issue. And if something is clearly just a question whose answer might be useful to others, then post it on StackOverflow or Discourse. In this case, it does look like a bug to me that messages from |
It's not a bug, it's not printed in "Notices" but in "Info". |
Oh, right! But how are users supposed to discover the various types of output and how to switch between them? |
I don't know to be honest. |
This does not seem to be working in VsCoq 2, I will keep it open to investigate. I would expect the message to appear in the messages section of the Goal panel. |
Solved by #842 |
I am expecting something in my messages bar but I don't see it
Example script:
in JScoq I see (https://coq.vercel.app/scratchpad.html):
in vscode I see nothing.
See pics for clarity

cross: https://coq.discourse.group/t/how-to-activate-the-messages-window-in-vscode-like-the-coqide-has/1584
https://stackoverflow.com/questions/71352672/how-to-activate-the-coq-messages-in-vscode-vscoq-like-in-the-coqide
The text was updated successfully, but these errors were encountered: