I have netbeans stuck pushing into a repository (no errors of course, that would be too easy). While clicking around and trying to find out what is wrong, I came across this option:
I tried clicking on it - I never noticed it before. It doesn't do anything but I have not found any docs on that feature either. The problem is that these keywords match many other things: netbeans watch process.
So do you have any idea what is it supposed to do?
In the netbeans progress indication documentation, you can find the definition you are looking for:
Show Output - opens the appropriate "output" window (valid only when the "output" window exists)
Watch Process - puts process to the status line
Cancel Process - cancels and removes the process from the pop-up list
In the help from the netbeans menu you can find the definition of the status line:
Status Line
The Source Editor status line is in the bottom right corner of the IDE. The first area of the status line shows the current line number and row number in the form line:row. The second area of the status line indicates the insertion mode (INS or OVR). The text area on the right is used for status messages.
So the watch process option is used to place the selected process in the status line.
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:
I'm trying to fix literally hundreds of XML validation errors in a Java webapp using Eclipse. Researching them with Google has been excruciatingly painful, because up to now, this has been my workflow:
Open Google in a browser.
Click in the Eclipse editor tab where the error (shown as an icon at the start of the line that's a red circle with a white "X") is located, mouseover, and try to memorize a chunk of it.
Click on the search form in the browser, and attempt to replicate the chunk from memory.
Repeat steps 2-3 until the text in the search form matches the text Eclipse ephemerally displays on the screen. Usually, something like:
"cvc-complex-type.2.4.d: Invalid content was found starting with element 'description' No Child element is expected at this point."
(that's just one error out of thousands, shown for illustration. I copied it from memory in 5 or 6 chunks)
At the moment, it's blowing my mind that there doesn't appear to be any easy way in Eclipse to do something like right-click the error icon & choose "copy error description"... or at least display it in some way that will survive giving another window the input focus so I can read it while typing it into the search form.
I know there has to be a better way to do this.
I suspect the error descriptions are present somewhere on the "Problems" tab, but I literally have almost 10,000 Errors & Warnings there, and no obvious way I'm aware of to sort or filter them. Is there maybe some keyboard modifier + mouse action that will allow me to click the red/white X icon and have Eclipse take me directly to the error on the Problems tab?
Good question, and I feel for you, there is a slightly easier way. I'm running Eclipse Kepler but I suspect this will work for you too.
Roll your mouse cursor over the problem x icon in the editor gutter (if you're showing line numbers it will be in that area), wait till the tool tip displays the error message, then quickly move your cursor over the tool tip and click within the text, then you can select all (Ctrl + a) and copy (Ctrl + c), then paste wherever the error description.
I used to see the line and column (character count) in the status bar of Eclipse (actually Precision32's version of Eclipse), but somehow it went away. According to the Eclipse UI guidelines it's supposed to be there:
Editors with source lines of text should show the current line and
optionally column numbers the status line. It's optional for the
editor to show line numbers for each line in the editor itself.
But I can't find anything that tells how to turn it on. I didn't update my editor, AFAIK.
Edit:
The editor is active.
I have no idea what happened, but it started working again. Might be when I installed Juno eclipse, maybe some register settings in common were touched? I hate doing a re-install to fix a problem as you lose settings and it isn't getting to the root cause, but for this round I'll have to accept it.
I am developing using the PyDev plugin in Eclipse. My program uses several classes in several files. I usually run the program using the green "play" icon or using Control+F11. The only problem is that it will run the file, which is currently in "focus". Usually this is not the one containing the starting point of my application. As I run my program something like 200 times a day, this means that I need 200 extra click on the mouse and often forget about this.
Is there any way of setting the default file to launch?
Yes, change the launching to rerun the last launched, so Ctrl+F11 will launch the last one -- and use F9 to launch the one with focus -- See instructions and details at: http://pydev.org/manual_101_run.html
For me, the shortcut is Ctrl+Shift+F9. I don't think I've changed any keybindings, so its strange that it would be different from the official documentation.
Go to Run->Run History, and select the run that is your 'main' run. Now you should be able to use Ctrl-Shift+F9 from any other file to rerun your main. If it isn't Ctrl+Shift+F9 for you, look on the console window that should be at the bottom of your screen showing the stdout after every run. There is an icon on the top of it that has the green start arrow with a yellow arrow underneath it pointing to the right. That is the command to relaunch with the same configuration. If you hover over that, it should tell you the keyboard shortcut you need.
I am working on an iPhone project containing a ton of code. The application receives outside requests and performs actions. However, I cannot figure out exactly where the app begins executing code for a particular event. Is there some functionality in Xcode which would allow me to solve this problem?
Thank you.
Have you tried setting break points in your code? Click on the line numbers column in Xcode on the number to set a break point.
Without knowing more about what these requests are or where they are coming from, its hard to give any advice on what tools Xcode might have, but looking in any project files named <xxx>AppDelegate.m or <xxx>Controller.m would be a good start, placing breakpoints on likely sounding methods.
I figured out that you can use the Instruments Profiler to this end.
Start the profiler
Choose "Time Profiler"
In the bottom left section make sure the following are checked: Show Obj-C only and Hide System Libraries
In the timeline, click on the the point before the event occurred.
Click the left-most icon in "inspection range" (located on the top-bar immediately to the left of clock)
In the timeline, click on the point after the event completed. (optional)
Click the right-most icon in "inspection range"
Inspect the Call Tree.