-
Notifications
You must be signed in to change notification settings - Fork 21
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
Is it really necessary to pop up the output panel when typechecking a file? #109
Comments
@be5invis Yes, I also considered switching to a new way to display the type checking result, one possible way is to show |
What do you have in mind is the best way to show the type checking result? |
I would give a +1 to the problem panel (and I did) |
@chantisnake problem panel is supposed to be the best solution here indeed, but we still have to wait it appears in the next release of VSCode. |
maybe a 👍 👎 icon like this? |
I think @be5invis idea is generally valid for now. Idris atom uses a method like this (a notification in the status bar) |
@be5invis @chantisnake OK, thanks for the reference, I will remove the stupid output channel and use the thumb icons. |
So it is also no need to display the type checking errors in output channel right? cause we can check all the warnings and errors in problem panel. |
I think so. |
I found the forced switch to output to be exceptionally annoying since I was quickly doing other stuff in another terminal window. I would definitely like this to be eliminated. |
@ndmitchell I will address issue ASAP :) |
|
Note that the thing that broke my flow was forced switching to the output channel - actually having the output channel wasn't problematic. |
@zjhmale @ndmitchell Add an option for that, "showOutputWhenTypechecking" |
@be5invis Thanks, adding an option is on the todo list already. |
Hi @ndmitchell @be5invis @chantisnake Sorry for the huge delay, I was busy with something else these days, the |
When showOutputWhenTypechecking is false, saving the file or activating the idris.typecheck command does not actually type-check the file. This is a bug but since there is a discussion about it here I thought I'd mention it. |
@pandemonium Thanks, I will address it. There is also a bug of Github that I just got the notification of your comment with a huge delay. |
No description provided.
The text was updated successfully, but these errors were encountered: