I cannot get any useful error reporting in IDEA 14. Errors are nicely underlined but it would be nice if I could somewhere see a collection of all the errors I have in my code.
Problems monitor is not showing anything, scala facet wont load, I', lost.
I would be satisfied with a window that would just collect all the errors I have underlined in my code, or a functionality similar to F2 shortcut (go to next problem) if it would work across whole solution, not only within a file.
Related
I'm using DrRacket to develop R6RS programs but I often see a bug where DrRacket hangs when either clicking on Check Syntax or Run. For example when checking syntax the message 'Check Syntax: expanding expression' is displayed at the bottom of the DrRacket window but no progress is made. Clicking on Stop shows the error message
C:\Program Files\Racket\collects\compiler\cm.rkt:213:2: user break
As far as I've been able to tell the problem always happens when running a program that imports a user library. I'm able to run the user library directly but for some reason there a problem when importing that same library into a program. I'm also able to use raco make on the same program without any issues, so I don't think there is any problem with the code.
A few more details. When I see this problem the Windows Task Manager shows that DrRacket is consuming no CPU (although a lot of memory). The memory use indication at the bottom right of the DrRacket window is ticking over, showing that DrRacket has not completely frozen. This feels like a thread deadlock situation to me. I have the latest version of DrRacket (8.7).
Any solution or workaround would be appreciated.
I've been trying to set up the Scala layer and the Metals backend for spacemacs. I am relatively new to spacemacs and completely new to Scala. Quickly some problems, for which I have no idea how they can be connected to the Scala layer, arised. Firstly I got an error saying "package eldoc not initialized in layer java" despite the fact that I had no java layer installed at the time. I managed to resolve that one by installing the java layer and then deleting a line saying "eldoc" in the file at layers/+lang/java/packages.el.
Afterwards another problem appeared, which I still haven't managed to solve, namely now I get the following message upon opening spacemacs:
(Spacemacs) Error in dotspacemacs/user-config: Symbol’s value as variable is void: lsp-server-install-dir
I googled right about everything about this error and found absolutely no other reports of such a problem and nothing close to a solution.
I tried experimenting with disabling certain layers in .spacemacs and commenting out the lines I added before the problem appeared, but nothing changes or even more errors and warnings appear.
I am not sure if this is in any way connected, but after trying to install the Haskell IDE Engine into spacemacs a few months back, I got a warning, which still appears whenever I start spacemacs, saying:
wrong-type-argument stringp nil
This second problem seems to be harmless, so after a few days I gave up on trying to solve it and have been using spacemacs normally until now. This new error about lsp-server-install-dir, however, seems to be more urgent and spacemacs shows a red line at the bottom saying that it might not work correctly.
I'm investigating switching from Eclipse Scala IDE to Intellij 15 + Scala plugin.
I can see that compile errors are reported in the Messages tool, but I can't see any highlighting of source files containing errors in the project tree.
Is this feature not available? If not, how do you cope? Have I been just spoiled by Eclipse and should learn to 'rough it'?
Update
This question is different to IntelliJ - show where errors are because:
This question is concerned with visual indicators against files in the folder/file tree view.
That question is concerned with indicators within the files being edited. This can be seen in the accepted answer, where the screenshot concerns editor settings for code highlighting.
I opened an issue with the exact same request when I switched from Eclipse to IntelliJ: https://youtrack.jetbrains.com/issue/IDEA-110767 !
After a while you become accustomed to look at the messages window where you get active links which when clicked, directly take you to the error.
Having syntax highlighting in the tree is nice when you refactor and hence tend to break a lot of existing code. At the same time automatic refactoring was (still is?) much better in IntelliJ than it was in Eclipse.
I don't recall when this happened, but whenever I attempt to use suggested fixes, imports will frequently show without the actual class it's suggestion to import, as shown below. This is not the case for all imports, some show up. But it seems fairly consistent with which ones are not showing up. It makes updating things annoying because I have to guess to see if I'm getting the correct import.
http://imgur.com/5t6fO1h
Very often, when I run my unit tests for my iPhone project, XCode feels like making the actual errors disappear from the errors and warnings group. These errors are often under the general sub-item of that group, and often when I need to read the text of the error in detail, all errors disappear and all I have left are the build warnings. Has anyone else seen this behavior and is there a way to fix it?
Edit: I forgot to mention; this seems to happen when i have errors that are not tied to any file (it says Line Location:0 in the second column of the error list). If there aren't any errors there (when generally the only errors are failed assertions) then it seems to work ok.
I haven't seen this behavior but what you describe sounds like a bug to me. You should submit it to apple.
It's hard to follow what you're talking about. What I can deduce is that you:
Build a Unit Test target
See the Errors and Warnings in an item in the Build Results window
Do something you don't explain to "read the text of the error in detail"
See the errors disappear (from the build results window?) but the warnings remain
It would help to see a screen shot of your project when it's doing what you want, before the errors disappear, and to learn what you are doing right before they go away.
This is probably happening because you have multiple targets with dependencies.
One target is dependent on another (usually unit tests) and the unit tests get built and their warnings/errors show up. Then, the main target gets built and its warning/errors show up. Since they are different targets, they second batch shows up over the first batch.
Assuming this is the problem, you can see the first batch by manually changing your target temporarily.