In one build of eclipse (it is on a computer I no longer have access to), when I typed in a task tag like //TODO or //FIXME eclipse would bold this in the editor so it stood out. How can I turn this functionality on in Eclipse 4.2.2 with PDT?
I found the setting for this under Window-Preferences-PHP-Editor-Syntax Coloring. Strangely, I had to change the PHPDoc option, not the Task Tag option.
Related
Just installed a new version of Eclipse ("Eclipse IDE for Enterprise Java Developers", 2019-06 / 4.12.0) and I find that although the hotkeys Ctrl-Shift-C and Ctrl-/ work to toggle comments for blocks of code in .java files, as expected, this doesn't seem to work for my .gradle files for some unaccountable reason.
OS is Linux Mint 18.3.
Anyone know how one goes about tweaking this sort of functionality in Eclipse (i.e. so that this toggling also works in .gradle files)?
NB I also find that going Ctrl-Shift-L twice does NOT open up (as previously) the "preference page" (i.e. where you can edit key bindings). I hope they haven't messed up things here.
However you can still edit these bindings by going Windows --> Preferences --> General --> Keys. This shows no fewer than 20 (!) "Toggle Comment" bindings, with Ctrl+7, Shift+Ctrl+C and Ctrl+/. The "When" column includes things like "Editing Java Source" but also "Editing in Structured Text Editors", etc..
So I tried to add my own key binding with "When" at "Editing Text". No joy. Anyone at all familiar with this aspect of Eclipse functionality?
greg-449 has the right answer.
Therefore what you have to do is install the correct Groovy editor.
I in fact gave the answer about how to do this here in early 2018.
It has changed ever so slightly now (for Eclipse "2019-06"/4.12), as described in my update there.
When you install that Eclipse-Groovy editor it automatically applies the various normal editing functionality not only to .groovy files but also (out of the box) to .gradle files: syntax highlighting, toggling of comments, etc.
I did not think this worked and was about to uninstall it, then I tried selecting Open with > Groovy editor, Thought I would share a little more detail, thanks!
In Eclipse (JEE) Oxygen I have the following plugins installed, other than what comes out of the box with a Java EE distribution of Eclipse:
groovy-eclipse for Oxygen (4.7) - Snapshot version as of November 8, 2017
Spring Tools for Oxygen - version from Marketplace as of November 8, 2017
I am coding in Groovy in .groovy files (created using New -> Groovy Class) and I very frequently get extremely weird and undesired autocomplete behavior.
Example 1
If I type System.out. on a new line, Eclipse autocompletes it to System.out0. (notice the 0). This is a private field of the System class and should definitely not be there.
To get rid of it, I can't just backspace and try the . again, or it'll put it back. I have to Backspace, then hit Esc, then hit . to get it to read System.out..
Example 2
In JUnit, I have in my class the following field:
#Rule
public ExpectedException ex = ExpectedException.none()
When inside a method body on a new line I type ex.expect( I see the autocomplete window pop up, and the first result is a member named anyExceptionExpected. Predictably, when I continue typing anything as an argument to the method, or type ), Eclipse replaces what is a perfectly reasonable method call with: ex.anyExceptionExpected(.
Again, hammering Esc "fixes" the problem, but what bothers me is that I shouldn't have to constantly hammer Esc to keep Eclipse from replacing perfectly valid code with total nonsense just because it's the first asciibetical hit in the list of member names of the object that happens to have the member name I typed as a substring.
Eclipse in Java certainly doesn't have this extremely oppressive behavior. Java autocomplete does not get in your way. You can blow through and type out your statements "raw" (without any autocomplete) when you don't want it, as if you're typing in plain vanilla Notepad, and Eclipse for Java generally won't mess with your code too much (except for sometimes making life harder by automatically adding closing parentheses or quotation marks when they are not wanted, but that's minor, since sometimes it's beneficial).
So why won't Eclipse for Groovy do the same? Is there a setting somewhere in the sprawling Preferences pane of Eclipse where I can tweak this behavior for Groovy code?
Basically I want Eclipse Groovy's autocompletion feature to work just like the default Eclipse Java autocomplete (meaning, the behavior you get with a default Eclipse install, a clean Eclipse workspace and without making any preference changes). How can I do this?
If you disable a couple of code assist options, proposals and completions will only occur when you explicitly request them.
Window > Preferences > Java > Editor > Content Assist :
uncheck "Enable auto activation"
uncheck "Insert single proposals automatically"
I wonder why the option "mark occurrences" isn't available (the button is grayed-inactive) when editing HTML files (*.html, *.htm extension). Is there an option to enable this feature in HTML editor in Ecplise (i'm running Eclipse Mars.2)?
I had your same problem with Aptana's HTML editor, and was finally able to resolve the issue.
First check to make sure this option is selected (by Default in Aptana for HTML, it is not). Go to Windows -> Preferences -> Aptana Studio ->Editors -> HTML. The very first option needs to be checked: "Mark occurrences with background color".
If the above did not work, you could try checking to see if you also have an additional installed software in Aptana that might be causing a conflict (this is actually what corrected my issue). I did have an additional software program added to aptana (called "Colorer"), which unbeknownst to me was disabling this functionality. If you have similar add-ins added to your installation, and they are not crucial to your workflow, I suggest removing them if the first option did not fix your issue. Once I removed my add-in, my Mark Occurrences for HTML (and CSS) came back to life.
If you start typing when the content assist is activated, content assist will only filter the suggestions based on the starting letters.
However, suppose that there is an object and we need to see if any of its methods contain a specific phrase in any parts of their names (not just checking if they start with that phrase).
Is there any way to configure the content assist or is there any plugin out there to provide that functionality for Eclipse?
The Eclipse Code Recommenders project includes subwords completion which seems to be exactly what you are looking for.
Keep in mind that with the upcoming 2.1 release (together with Eclipse Luna on the 25th of June, 2014), the subwords completion is no longer activated by default. Go to Preferences > Code Recommenders > Completions and activate the Subwords-Completion Processor.
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 ...