I am using Eclipse to work on a large Flex project. Whenever I have an error in an actionscript file, it shows nothing in the "Flex Errors" section of Markers but when I open the file that has the error it shows a question mark next to the line where the error actually is.
Is there a way to show these questions marks in the markers section of Eclipse?
Let me know if you need more information!
If you roll your mouse over the question mark, it should show details. Question marks were introduced in Flash Builder 4.5, I believe. They are a kind of "highlight problems as you type."
Often these question marks will turn into yellow exclamations (AKA Warnings) or red Xs (AKA Errors) on saving the file.
However, if you using the include directive to include one ActionScript file inside another, it may show these question marks in the include file, even though there isn't actually a problem.
Related
EDITED (see bottom)
Is there really, after so many years of unanswered questions such as mine, no keyboard shortcut to jump to the next or the previous error in Netbears 8.2?
This page says that the shortcuts are
Ctrl+./, Next/previous usage/compile error
Note the inclusion of the word usage. In no other "Next/Previous" shortcut is usage used. I wonder why it's here and if it points to the problem. It's not exactly a typo. What might it mean? Yeah, probably nothing.
Whatever, absolutely nothing that I have found shows how to accomplish this very important pair of tasks.
Using Tools > Options > Keymap shows that Ctrl+PERIOD and Ctrl+COMMA are how to do it. But it doesn't work.
Once Ctrl+PERIOD took me SOMEwhere, and doing it again took me to the next occurrence of it, etc., but those lines of code had no errors and it doesn't happen now.
I've clicked on the ellipsis on the line for Next Error and Previous Error and edited them to be Ctrl+BACKQUOTE and Alt+BACKQUOTE and I clicked on the ellipsis and defined alternative shortcuts to be Ctrl+CLOSE_BRACKET and Alt+CLOSE_BRACKET and I could NOT define Next error in Editor to ANYTHING.
NOTHING works.
So my question is WHY NOT? I use F2 and shift+F2 in Android Studio with every error I get! How can this NOT be possible in Netbeans 8.2?
I am reluctant to upgrade to Netbeans 11 for just this, especially not knowing if this problem persists.
======================
EDIT
After looking at what #Dmitry_M submitted, I took another whack at it with the above definitions, which cause:
Alt+1 to take me to Next Error, but ONLY after a fresh Build or Clean and Build Project, and it takes me to other lines (in xml, for one) that have no errors (that I know of; they're not flagged).
Alt+2 to take me to Previous Error unless I fixed it, in which case it takes me to that same line that HAD the previous error, just as Alt+1takes me to where the next errors USED to be and to the other places, too.
Next Error in Editor to do nothing.
This makes me wonder what Category actually means since Next Error in Editor says Source while the others that DO work say System.
My source files have more than a few "yellow warning" indicators, but unike Dmitry, the definitions don't find them.
If it finds the errors among other things, that's better than it was. But it only finds errors already listed in Output, and it requires build, and it finds other extraneous "errors". So I'll just look at Output. Keymap fails.
I'm discouraged with Netbeans 8.2.
I am using NetBeans 8.1
Next Error in Editor
The keymap moves a cursor to any hint or error that the editor shows. They are sometimes not compiler's errors. See it in action.
For example, the cursor moves to int i = 0; but there is no error there. There is just a hint that variable i is not used anywhere. And in the import statement: it's just a hint.
If you want to define a keymap for Next Error in Editor action try different key combinations. I use alt+1.
Previous Error/Next Error
The keymap only works for clean and build or build actions.
Probably, when just editing and saving NetBeans doesn't refresh errors list somewhere in the cache. It explains the behavior you experience: the cursor moves to a line where there are no errors. It simply moves to the line where an error was during the last build or clean and build action.
Se it in action just after clean and build. It works:
The cursor indeed moves only between "real" compilers' errors. But it only works after clean and build or build action. Probably it's a bug. There is a relevant bug but it was not resolved.
Also, in my case, Ctrl+PERIOD and Ctrl+COMMA were not working completely. Changed my keymaps to this one:
Currently eslint/tslint highlighting for issues/errors is super invisible (comparing, for example, to Atom). Its almost impossible to catch the issue - find the small green highlight zone (see screenshot)
VSCode:
Atom:
Question is not relevant since June 2018 (VSCode now has awesome highlights)
Simple. I use 2 extensions for that:
Error Lens (usernamehw.errorlens) for highlight the entire line and show on real time the error diagnostic
Error Gutters (igorsbitnev.error-gutters) for put error icons next of line number
Both look like this:
For those who would like a partial solution for this you can actually open up the console in vscode on the PROBLEMS tab to display all errors on across your application grouped by file.
I would prefer the inline visualised approach, but this does resolve this problem more or less.
To open the PROBLEMS tab, click CMD+Shift+M on Mac.
Not sure about windows.
I just set up Eclipse for PHP Developers on a new machine, and now I have a problem I haven't experienced before.
Normally, I keep track of short-term work that I want to do by adding TODOs in comments on a file. These show up on the right side of the editing window as little blue rectangles. This helps me find the next thing I need to work on.
That part is working, but when I remove the comment the blue rectangles aren't going away. I have used Eclipse for years and never had this problem before.
Anyone know why this isn't working?
For tasks added in the source file's syntax, you often need to Clean and Build the project again to reprocess the file (those are handled in the relevant compiler). For ones that don't get "compiled", check the General->Editors->Structured Text Editors->Task Tags page and have it try to redetect them from there.
is there a possibility in eclipse to mark multiple lines in different classes of a project for later editing, so i can write some test code and afterwards before i release my software i got the possibility to show all the marked lines and delete or edit them ?
I know the Tasks in eclipse just not sure if this is the right way to go, because i have to enter the name of the Task everytime and there isn't the possibility to group them together as far as i know.
You can also use a comment //TODO. Either will show up in the Tasks view and will give you special markers on the right bar (like you'll see for warnings or errors. //FIXME will work, too.
Checkout the #TODO annotated javadoc tag.
http://docs.oracle.com/javase/6/docs/technotes/guides/javadoc/taglet/overview.html
Just for other folks that will see this question, you can mark a line as a boolmark, see this answer: Highlighting lines in eclipse, like with a textmarker
There was a library issue in a file and after fixing it, the red error mark in the line disappears. But the file, package and the project shows with red error mark.
I refreshed but still get the red mark. How to get those marks removed.
Thanks.
There are two different mechanisms for displaying problems in Eclipse. Annotations are a lightweight mechanism that are bound to an editor, and markers are used for displaying the problems anywhere else (e.g. Package explorer).
If the in-line annotation disappears, but the project error mark does not, it means, the annotations and markers became inconsistent. First you should try to save the files (sometimes the annotations gets removed during editing, while markers are only refreshed on save). Of course, you have already saved (else the refresh would not make any sense), so I guess, some markers got stuck.
To remove that marker, open the Problems view (Window/Open view), and find there the corresponding error marker, then remove it (Delete in the pop-up menu).