Syntastic does not seem to work properly for me. It is installed, :SyntasticInfo says everything is fine (active mode enabled, filetype cpp, checker is ycm). At first glance everything seems to be fine because it looks like this:
I have my signs on the left and the location list at the bottom. But as soon as I move the cursor, the signs as well as the loc-list disappear and it looks like that:
The only exception to this rule being entering insert mode right at startup. But of course once I leave it, everything disappears.
Now I know that there are commands like :SyntasticCheck or :Errors and they do exactly... nothing. I type them, I execute them and that's it. Like I hadn't done anything at all. Naturally saving the file doesn't yield any result either.
My .vimrc looks like this:
let g:syntastic_enable_signs = 1
let g:syntastic_auto_loc_list=1
let g:syntastic_check_on_open = 1
let g:syntastic_cpp_compiler_options = ' -std=c++11 -Wall'
If I remove these lines I don't even have the signs and loc-list on startup. So yea, I am really at a loss here.
Turns out this was more of a YouCompleteMe problem than it was Syntastic. YCM automatically sets itself as the checker for syntastic (for compatible languages) and also requires a .ycm_extra_conf.py which should contain the compile flags for the ycm compiler. Without these flags it is not capable of compiling the code or detecting any errors.
Related
Currently VS Code will only highlight errors when the file is saved. This can get bothersome, as it isn't immediately apparent sometimes if you've mistyped something or are using something wrong etc.
Is there a way to make VS Code automatically show syntax/logical errors i.e red/green squiggles underneath code?
I am working with python but I have the same problem.
As shown here: "Linting runs automatically when you save a file."
Therefore, what I did to automatically lint, is enable Auto Save. With this configuration you can achieve linting almost in real time.
I guess that for C++ will work similar. Hope it helps.
My project works fine in Xcode 8. When I build It in Xcode 9, there are many C++ semantic issues reported.It seems Xcode 9 C++ complier do much stricter type checking than Xcode 8.Is there a build configure fix to this.
There are three little lines in the upper right of the error list. Like an icon of lines of text. Click those to get the raw compiler output for your error messages. At the end of each warning it usually names the command-line flag corresponding to it (like [-Wwarn-about-mistakes]). You can search for that in build settings using the filter field to see the corresponding check box.
All that said: all these warnings have a reason for being there. You should find out what each warning is about and change your code the right way so the compiler doesn't have to warn anymore.
Even if these warnings seem pointless and your code appears to work, they usually indicate an issue that is either already occurring, or might have unexpected side effects later when you change another part of your code.
Is it possible to only list the set of rules which would have failed on input file without actually applying them? I find it too harsh to just modify the file without letting developer know that file is getting changed under the hood but I would like to get common coding standards and cause build breaks when rules are broken.
I know about --check flag but it only returns whether it succeeded or not without letting developer know which rule failed on which line. Perfectly I would like to get something like:
test.cpp - uncrustify failed on line 42, incorrect use of tabs - pos 0:6.
Also if you know other options where this could be more easily achieved please let me know.
wondering if I could have the same behavior as Brackets like it previews the code on the right side but only opens the file if we do some edits.
Helpful when I'm just going through the files and not really changing anything but then at the end I've to close all.
Is there a setting in web storm that can help achieve the same behavior like brackets
Currently I may only suggest to use View | Quick Definition to preview file content instead of opening (has to be invoked for each file, which is possibly not what you are willing to do).
Other than that: https://youtrack.jetbrains.com/issue/IDEA-130918 -- star/vote/comment to get notified on progress.
P.S.
As stated in this comment they seems to worked on something like that already but quite possibly did not finished it for IDEA v14 release: in build 138.2502 there was an option to open file in "preview panel" first (and if satisfied -- move to editor) instead of opening in editor straight away. But it still a bit different to what Sublime does.
If I add //(* to an un-commented line in my source code, the rest of the font becomes italicized and changes color. The code still seems to compile however. And I cannot find a way to "undo" this change of font sequence with some other sequence. What is this used for? This occurs in C and C++ code so far as I can tell, and it does not occur in vim. Im using Windows 7 and CodeBlocks 12.11.
//(* and //*) is a special comment block used to identify code that is automatically generated by the wxSmith plugin included with Code::Blocks.
This looks to be an IDE extension, but for what, I have no clue at all. All I can say is that you can end it by putting //*) on a new line:
One might think this could be used to have multiline comments that contain */. However, the catch is that the darkened code still compiles. Why it would be a different colour and not act different is beyond me.