How to disable error checking in NetBeans 6.9.1?
It is very annoying to have red line in the source code.
This is similar to NetBeans - Turn off - wavy red underlines - How?, but I want to disable underlines at all, not only when typing.
(It incorrectly parses PHP sources and omits syntax errors.)
Netbeans has a vast array of settings but this might do it. Try changing the drop down labelled "Wave Underlined" to "None":
Update:
Since I don't do PHP development I wasn't originally aware of the PHP plugin for Netbeans. You can find it listed in the plugins (Tools > Plugins) for Netbeans and should provide a much better environment for PHP work, with, I'm assuming, better PHP parsing and syntax highligting.
I would just click on the hint on the left side by the line numbers, it should create a pop-up, while that's still up click on the hint again. Now another pop-up will be there asking if you want to turn off the error check for either that single file, or for all files. Choose for that file, b/c it should be off by default.
I have no 6.9 at hands, but in 7.x (and believe so, for some time)
go to Options->Editor->Hints-> and uncheck
[ ] CSS (all those rules together)
[ ] HTML Validator (ditto)
Did the trick for me, when working with proprietary template files, 'coincidentally' named .html ...
Related
Question:
Is there a way to run an eclipse action that is available from the context menu in the editor on every file of an project.
Actual Case:
I have to work with the leon3 and my dull mind has trouble enough understanding the code, that I do not want to scan lines to see if there is a semicolon hidden in there to see if there are multiple instructions or if the end if happens to be behind another instruction rather than on a line of its own (I missed an end if, which caused me to think that statements were conditional,...), therefore I would like to format the source nicely. I have access to Sigasi PRO which offers the option to "beautify" code as an operation in the editor. I would like to run this operation on all files in the leon project automatically.
Sigasi indeed only offers formatting in the editor at this time. In the Sigasi editor, you can format a selection or the entire editor's content. But, you can not trigger the formatting action without an editor.
I have not tried this, but I think you can achieve this with the Eclipse EASE project. EASE is a scripting environment for Eclipse.
I have a file with extension .xml.
But it doesn't necessarily contain XML. It may also contain HTML and JavaScript. Now I would like to either have Eclipse decide inteligently/heuristically which syntax highlighting would be appropriate or to switch it myself.
Any ideas?
Eclipse associates files with an editor. You can let eclipse decide which editor to use (e.g. defaults per file extension) or select the editor by yourself. I guess you might already know that or have at least experienced it.
Syntax highlighting isn't always set seperately but instead part of some editor (together with stuff like keyboard shortcuts). So what you are going to need is an editor that behaves the way you want it to. I do not know if there is an editor like this available but one options is writing an eclipse plug-in and implementing such an editor.
Fortunately there are great editors for each of XML, javascript, HTML, etc that are all open source. I guess you might be able to use some of their code. Ideally as a client of their API / Objects or if it won't work out just by reusing code.
short answer: not possible. use PHPStorm instead :)
I've just installed Eclipse for PHP Developers and for the most part it works fine, but I seem to have a problem with the highlighter:
If you hold control and then roll-over a method, eclipse shows a pop-up of the first few lines of source of the method (That's obviously not as useful as JavaDoc, but whatever). The problem is that the background of this popup is black and I can't seem to figure out which preference to set to change this.
Bonus points, BTW, if you can tell me how to adjust the PHP Eclipse colors.
In the Eclipse Preferences, select PHP -> Editor -> Syntax Coloring to change the colors.
By the way... some people say Netbeans is much better for PHP development currently.
This is a bug which actually has to do with Ubuntu as well as Eclipse: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/540332
I've not gotten it to work locally yet, but this is a good head start.
Trying to edit Freemarker Templates in Eclipse, and going nuts because I have some inline Javascript that I'm creating on the fly, and can't easily comment / uncomment multiple lines at a time.
I've tried the following:
expanding the scope of the "toggle comment" behavior (to things like "Editing Text", or "In Windows") - has no effect
installing the official Freemarker eclipse plugin (both 1.0 and 1.1) - has absolutely no effect that I can see, other than appearing under "Preferences ... File Associations"
associating the .ftl extension with other types of editors - HTML, JavaScript, 3rd party - all these have absolutely no effect that I can see
Is there a way I can tell if Eclipse is even honoring my file associations? How do I know, for sure, which Editor is being used? I know when a Java file is being edited, I see additional pulldown menus (Source, etc.) - is there any other diagnostic way to figure out what's going on?
Any help is appreciated.
I know this isn't what you want to hear, but the Freemarker support in IntelliJ IDEA is really great.
Unfortunately, it isn't part of the free Community Edition, so you have to get the Ultimate Edition to benefit from it. But you can try it out for 30 days for free.
No, I am in no way associated with JetBrains, just a happy user.
I am SOOOOO discouraged. This seems so simple, but being a complete novice in Drupal and Eclipse PDT I have absolutely no idea where to look. My DAYS of searching seems to indicate that I am the only person on the planet with this problem.
Eclipse IDE for PHP Developers (1.2.1.20090918-0703)
WampServer Version 2.0
Apache 2.2.11
PHP 5.2.9-2
MySQL 5.1.33
Drupal 6.15
xDebug php_xdebug-2.0.5-5.2.dll
I setup my project in Eclipse to point to my Drupal directory (C:\wamp\www\drupal-6.15). I start the debugger (xdebug) and I stop at the first line of code. I can step through the code line by line -- so I think I am in the debugger, and when I terminate the app, I see the xdebug termination message in the tab heading.
But I cannot set a breakpoint in any of the PHP code files -- specifically a new .module file.
When I right click in the breakpoint column on the left in index.php (main) I see "toggle breakpoint" and the little blue circle next to the line of code...so I think I know how to set a breakpoint. But when I try to set a breakpoint in my .module, I see a menu that asks me to "add a bookmark" and no option to set a breakpoint.
Why can I not set a breakpoint in this file? Is my project path not set up correctly? Do I need to amend my include path? I can't get Eclipse to recognize even core modules not just site/all modules. I've seen posts about "importing" files into the project, and making sure the correct php.ini file is used for configuring xdebug. I'm lost.
There are so many posts about using Eclipst PDT and xDebug and they all end with "have fun debugging" or "just set some breakpoints and off you go" -- but what if you CAN'T set a breakpoint? Any ideas about where Eclipse is lost? Where in Eclipse can you get a list of files it has included in its build?
I think I just need to know understand why Eclipse cannot find these modules within the project (i.e. drupal application) path to allow me to set breakpoints. Then I think I can carry on. So discouraging...
Thanks to anyone listening.
Thanks for the tip. I think I had seen your similar response in another post somewhere.
Actually, the solution for me was to make sure to include all of the standard Drupal file extensions in the Eclipse file associations preferences: Preferences->General->Content Types->Text->PHP Content Type. The defaults are various *.php, *.phpX, *.phtml extensions, but not the extensions used in Drupal modules -- *.info, *.inc, *.module, *.install, etc.
Simple and obvious once you figure it out. I'm surprised with all the Eclipse-xDebug-Drupal setup instructions out there that this had not shown up. Lots of details about matching project paths with server paths, but nothing about this.
I hope my struggle helps someone. I did learn a lot about Eclipse PDT along the way :-). Good luck.
Breakpoints are tricky in PDT projects:
for php files, you need to be careful
One thing that gets me a lot is that there a lot of "invalid" places where you set breakpoints. You can put the dot there in the IDE, but the debugger won't stop at it:
blank/non-code lines
on switch statements
in some types of callbacks (for example, preg_replace)
But for breakpoints in .module files, this should be related to a setup issue.
I made the following changes to my setup:
Upgraded from php 5.2.1 to php 5.2.3
Installed the Zend debugger client in Eclipse/PDT (theoretically not necessary from what I understand, but I decided to give it a try)
Made sure that the Drupal files were fully imported into my project, not just referenced as include libraries.
I did that last step after I created a tiny test case and discovered that I could get the debugger to stop on a breakpoint in an externally included file only if that file was imported into the project, not if it was referenced as part of an include library directory.
To my mind this seems like a bug - the debugger could certainly see that the files in the include library directories were source files and it let me set breakpoints in them, so it seems that it should stop on them.
(For comparison from a separate (java) IDE, IntelliJ will let you define breakpoints in jar files as long as you tell it where the source is. Once you've defined it, it will stop on it.)
I think it was principally that last step that did the trick, so I'd suggest that anyone else with a similar problem make sure that isn't an issue in their setup first, and then try the other steps.
check whether you opened your java file in java editor mode.
ie ctrl+shift+R, in this popup check the button beside OPEN option and select java editor.
The problem of not being able to set a breakpoint can occur if you have recently created a file. You must close and re-open the file for it to be recognised as a source file that can be debugged, and to enable the code highlighting.