I'm evaluating WebStorm 11 and I have a problem with the /*jslint maxlen: 130, nomen: true */ comment only the maxlen doesn't work:
Also the git code analysis return the same errors only for the maxlen too:
What am I missing here?
I looked into the WebStorm jslint docs but couldn't find anything about this.
Related
May be I am missing something but I have not found a dedicated place in WebStorm where I can see (and navigate) all errors reported by TSLint.
In the best case I can find the errors while opening a file and pressing F2 (to go to Next Highlighted Error) which not always working as well.
PS. There is a dedicated TypeScript Pane/l in WebStorm but it doesn't show any TSLint errors, neither these reported in Event Log Pane/l.
Select npm tab from the bottom left side.
Run linting script (you must have it in package.json).
See screenshot below for example:
List of tslint errors/warnings
I am a beginner to vim and just downloaded the c-support plugin (for C/C++ programming) from the following link: http://www.vim.org/scripts/script.php?script_id=213
As advised in the link, to enable cmake and doxygen, i added the following lines to my _vimrc:
let g:C_UseTool_cmake = 'yes'
let g:C_UseTool_doxygen = 'yes'
However, now when I start up gvim, I get the following error message dialog:
Could not load the tool "cmake" (Vim(let):E117: Unknown function: mmtoolbox#make#Interface)- occurred at C:\Users\Satyendra\Vim\vimfiles\autoload\mmtoolbox\cmake.vim, line 219
My OS is Windows 10. How do I resolve this error?
(Posted on behalf of the OP).
I opened an issue on C-Support's Github page, and the problem was solved.
I'm using Pycharm 3.0 with python 2.7.
The problem is that when I'm coding, Pycharm is underlining my code which I'm sure its correct. when I cut the line of code and paste again it has not errors!
The funny part is that Pycharm is underlining my codes in the comment as errors as you can see in the picture. what should I do?
Try inspect the code.
Code > Inspect Code
Choose the options: Whole project, File or Custom scope.
The underlines are possibly spelling or indentation; for the spelling the solution is:
Save 'word' to dictionary.
I just installed vim-autoformat and astyle to format my c/c++ code inside vim. Everything seems to work, but it puts a newline to the end of the file everytime I run it. Even if there is one (or multiple). I tried to find the option in astyle -h and search the web, but didn't find anything. What do I do?
It looks like it's a bug in astyle that's been fixed. See http://astyle.sourceforge.net/subversion.html for help getting the latest development version. I'm using version 2.05 beta and it seems to be working correctly now.
I've wrote up my regex for error parsing of an unsupported compiler. However, it seems to ignore me and I don't know how to debug it.
The error message looks like this:
"file.c", line 224: Error: #20: identifier "myvar" is undefined
I wrote up this regex for Error:
"(.*?)", line (\d+): Error: #(\d+): (.*)
File: $1, Line: $2, Desc: $4
Eclipse's Console and Problems tabs seems to ignore it. What am I missing here?
Eclipse for Windows 3.7.1, CDT 8.0.0
Edited: while I use an online Javascript-based regex tester,
to debug CDT regular expressions I prefer to click into the console and use the regular search dialog box.
This might help someone. I was trying to get a custom parser working but I could never get it to match. It was a setup problem. You have to setup the match in Window > Preferences > c/c++ > Build > Settings > Error Parsers. To get it to USE it you have to check it in > Properties > c/c++ build > settings > error parsers.
Looks like my regex wasn't matching the error message.
The following regex solved the issue:
"(.*?)", line (\d+): Error:(\s*)#(.*): (.*)
File: $1, Line: $2, Desc: $5
Hope this helps someone with the same issue.
It did help me, actually. In response to your question about how to debug the error parser, I did my regex pattern testing with Python against strings captured from a compiler run. Once I got that working I just pasted the regexes into the error parser form in CDT.
Obviously, there are many different ways to play with regex, notably Perl.