I have want seems like it should be a simple question but I keep striking out...
In Eclipse 3.8 / STS 3.1, how do I stop Eclipse from truncating the file names in the editor tabs. I can't tell which tab is which. Thanks in advance.
Try this solution.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=32789.
I have tried it with Eclipse Kepler 4.3 SR1
Under Window-> Preferences go to General -> Editors.
The last point should be "Close editors automatically", and you can specify a number.
If you check this, the least recently used editor will be closed when the given amount of opened editors is reached. That way the open editors don't take up so much space, and the possibility of truncated names is reduced.
You can always quickly search and open resources with Ctrl+Shift+R, so there is no need to have them open all the time.
Of course it can't be guaranteed to always show the complete name. If there is not enough space, what do you expect Eclipse to do?
you need to set eclipse Threme.
Under Window-> Preferences go to General ->Appearance
Threme: Classic
Related
I'm using Ubuntu 12.10 and Eclipse Juno. This happens frequently: When I put focus in eclipse editor window, I can input few words in editor at the beginning, and then undo several times, Suddenly it happened that, I can't input any word in eclipse, that's strange problem.
Then, I change to other program and input anything, After that, back to eclipse it can accept my key again. It get me so frustrate.
Any one knows this problem? I am using desktop pc, memory is 1G.
This may help;
I guess you have lots of projects in your workspace and Project->Build Automatically option was enabled by default. Disable this and use Project-Build All or Project-Build Project commands before you start debugging your application OR If possible create two workspace and move some of your projects to other workspace. Note that you can open two instances of Eclipse on two different workspaces simultaneously.
Increase heap space for Eclipse.
Its also possible that you installed many plug-ins in Eclipse. You can disable unnecessary plug-ins to load on eclipse start up as shown below
Edit
Two more options.
1. Disable all options in **Highlighted** category of preferences. Restart eclipse.
2. Delete **.metadata** in your workspace and restart eclipse. Note!!!. All you preferences will be lost!!!
I found this problem; It is scim input method conflict with XIM(X Input Method) method.
Solution 1,
just right click in eclipse workspace -> select Input Methods -> SCIM input methods, that's OK. But, Every time you should do it while opening another file.
Solution 2, make scim as default system input methods.
Edit /etc/X11/xinit/xinput.d/scim as below:
XIM=SCIM
XIM_PROGRAM=/usr/bin/scim
XIM_ARGS="-d"
XIM_PROGRAM_SETS_ITSELF_AS_DAEMON=yes
#GTK_IM_MODULE=xim
#QT_IM_MODULE=xim
GTK_IM_MODULE=scim
QT_IM_MODULE=scim
also, add x95input file to /etc/X11/Xsession.d/95xinput
/usr/bin/scim -d
XMODIFIERS="#im=SCIM"
export XMODIFIERS
export GTK_IM_MODULE=scim
Hope this can help others.
I found it.
I googled and found the answer
The answer is:
Right click in Editor area InputMethods-Scim
*Editor area is where you write code
I am always the first one to jump on any latest Eclipse release thinking that it would solve some of the issue that i have with slowness but i am always disappointed. The DLTK thing that keeps running, memory heap issues, internal error occurred ....
The latest version that I have tried is KEPLER
I know that I can close the projects that i am not using, disable validation, remove projects from the build path, hack into their myriad of codes and change settings but really?
I have to admit my workspace has only 5 projects but more than TWO HUNDRED heavy duty folders. within those folders you have for example, Drupal, Wordpress and so on..
I have used visual studio for years with 5 times as much projects without this kind of slowness but that is besides the point. Let's go back to eclipse.
looking at my settings, some people might say: why don't you create a projects for each of those folders? I tried that but the DLTK indexer keeps on indexing every projects in my workspace unless i close them. WOW!!! Create multiple workspace is out of the questions, if i have to do that i will just ignore Eclipse all together.
My hardware is decent and I have SSD Drive and plenty of RAMs.
What is the largest amount of projects or files can Eclipse safely handle? What about the DLTK what are its limitations?
How large is too large?
What doesn't visual studio seem to suffer from the same slowness? Is the problem java related or with the data structure? Can Eclipse handle that amount of projects?
I know that there are a lot of moving parts and answering these questions is not black and white but why is this thing indexing even the stuffs that i am not using?
I would like to get some opinions on how to use this editor effectively?
While the number of projects/files is not exactly "limited" (beside the resources of the host machine), the number of open editors is.
Eclipse 2019-09 proposes by default 99.
Close editors automatically when reaching 99 open editors
The preference to close editors automatically is now enabled by default.
It will be triggered when you have opened 99 files.
If you continue to open editors, old editors will be closed to protect you from performance problems.
You can modify this setting in the Preferences dialog via the General > Editors > Close editors automatically preference.
IDEs are slow by nature because they do a lot.
I would never use eclipse for webdev stuff like wordpress.
You should be leaving your library files outside of your main project as external folders so that eclipse discounts them. That way you can just have the files you need in your workspace.
Also, try closing the projects you aren't working on by right clicking and choosing "close project"
Personally I use vim and FTP to handle this stuff. Eclipse is nice and integrated but very chunky.
I've been using eclipse for java android development for 6 months and I love the compare editor. In the last few days I have been hacking away and I think I have all my git ducks in a row, or close enough that things are clean and neat and I can find old working versions of apps.
But it seems in the last day or two, the eclipse compare editor has stopped showing diffs! i right click on uncommitted PlayThread.java and choose to compare with Commit... or HEAD or branch or anything, and no matter how similar the files might be, the compare editor shows one big white bar on its right side, and clicking to go to the next difference highlights the whole file!
I have looked through the git and compare preferences on eclipse and can't find anything that might help.
Any help getting my beautiful compare editor working for me again would be greatly appreciated!
With respect to Javascript compair showing nothing, there is a known bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=509820
Workaround...
Window >> Preferences >> General Tab >> Compare/Patch
Deselect checkbox next to "Open structure compare automatically"
Note the the latest EGit 5.3.0 (Feb. 2020, 8 years later) improves the right side of the compare editor, using the Eclipse -> Preferences -> Text Editors -> Show whitespace characters mentioned in Vivek's answer.
Text comparisons in Eclipse have been improved to make "Show Whitespace" work in more cases.
Also, concurrent editing of a file in a merge editor and in another editor open on the same file has been improved and works now better and even for files not in the Eclipse workspace.
Note that both showing whitespace and concurrent editing depend not only on the way EGit sets up the comparison (which is what we improved) but also on the actual editors being used. These editors are beyond the control of EGit.
With files not in the Eclipse workspace, one may encounter Platform bug 214351 when a file is open in another editor.
Original answer (May 2012):
The compare editor shows one big white bar on its right side,
That means Egit considers the local content of that file (on your disk) differs completely from what have been committed.
The one classic case where that happens is for automatic eol conversion (Windows <=> Unix), which is why I always set core.autocrlf to false.
See "Git beta on Windows (msysgit) - Unix or DOS line termination".
See also "Distributing git configuration with the code" for managing those eol through .gitattribute file (except EGit doesn't support yet .gitattribute file).
In this instance, the OP mwengler reports:
Well that was it.
The way I fixed it was in Eclipse > Window > Preferences > General > Compare/Patch > General on that page I checked "Ignore white space" and now the editor shows my diffs.
But I think I will turn off that autocrlf stuff, I don't think I'm using anything on windows that can't handle both flavors
See Egit bug 361503 which mentions that this "Ignore White Space" now also honors the core.autocrlf setting.
Below setting also works for Eclipse Oxygen Release.
It appears that this has something to do with the Structured Compare. To
use the simpler and apparently working version of compare choose:
Window > Preferences > General Tab > Compare/Patch
Deselect checkbox next to "Open structure compare automatically"
Enjoy text level diffing of ES6 classes.
Regards,
Rasool Javeed Mohammad
javeed.mca#gmail.com
Today again after long I caught in this issue. Every-time I fix this problem and move on but this time I tried understanding the root cause and get it fixed and since the fix which worked for me is not in the answers to this question, thus adding part with details :
I am using EGit plugin in eclipse, and the problem was same as OP - eclipse compare tool was not highlighting the differences rather a whole block as if the whole file has changed.
Lets understand the issue first , since I was aware that this is related to CRLF vs LF eol , so went to check that first and enabled the visibility as :
Eclipse -> Preferences -> Text Editors -> Show whitespace characters
In the above click on configure visibility.
Now as you see highlighted in above image, select the check boxes under Trailing and against both Carrier Return (CR) and Line Feed (LF).
Apply - Save and Close. Now in my case , file looked like this :
and this evident that for me I had CRLF window like eol which further also confirms as I do not have core.autocrlf set to true and by default it is false thus Git actually didn't tried to do anything about my EOL delimiters (as expected in this case).
And until this stage, the compare tool was showing the whole file as changed.
Now, moving to fix which worked for me.
Since, I wanted to get this fix within IDE realm, thus I first converted the particular file to Unix delimiters as :
Then my file became with LF (Unix delimiter) eol :
And compare tool started highlighting the delta.
So the issue as it was assumed was because of CRLF (window style) eol and eclipse comparator was not able to highlight delta rather whole file.
Then, instead of changing each file or package to Unix delimiters .
I updated in Eclipse->Preferences -> Workspace
By this, eclipse takes care of line-endings for new files to Unix, so that text files are saved in a format that is not specific to the Windows OS and most easily shared across heterogeneous developer desktops. After all this compare tool worked happily ever.
Hope this helps.
How do I get Aptana to recognize .jspf files?
I'd like to have syntax highlighting for .jspf files. I'm sure there's a preference/config option or an xml file to edit, but I'm not finding it.
I assume it's similar to the eclipse process, so I'm tagging eclipse, too. If it's not, I'll remove the tag.
I hope this is what you mean but you can set your file assosiations in Eclipse usually like this (and yes, Apatana is Eclipse based so it should work the same way):
Window -> Preferences
Then
General -> Editors -> File Associations
Select *.jspf and move or add the Aptana Editor you want to use by default.
I use Eclipse 3.3 in my daily work, and have also used Eclipse 3.2 extensively as well. In both versions, sometimes the Search options (Java Search, File Search, etc) in the menu get disabled, seemingly at random times. However, with Ctrl+H, I am able to access the search functionality. Does anyone know why this happens? Has it been fixed in Eclipse 3.4?
window > close all perspective works for me.
Using Eclipse 4.3(!) this happened to me after doing a case-sensitive search.
Window -> Close All Perspectives didn't fix it and neither did restarting Eclipse using -clean. While messing with the search box, I discovered that simply clicking to a previous search entry allowed me to edit it and search again! Clicking back to the case-sensitive search grayed the option out again.
So before you reset anything in your workspace, try pulling up an older search entry using the Down Arrow.
I think this answer is what you all need to solve the issue on all versions.
I am using RAD 8 and I have also faced this problem than I removed org.eclipse.search directory in (workspace currently using) workspace/metadata/plugins folder then restart the eclipse.
That's all.
I don't have an exact answer. I will recommend that you try to correlate the disablement with which perspective is active. Likewise, which view is active. I have been using 3.4 and not experienced this issue.
Darn! I have that problem too -- in Eclipse 3.4.2.
Seems to be related to Navigator and Project Explorer views:
- Switch to Debug perspective: Search menu items are there.
- Switch to Java or Java EE perspective: Search menu items still there.
- Click on a project in Navigator or Project Explorer: Search menu items all DISABLED.
(Curse! I use search in Selected Resources a lot! )-:
Hmmm... It may slso depend on the file type currently open in the editor. (Like Java vs xml.)
Still present in Eclipse 3.5.2 -- and for the first time really sticky.
I checked out the "close all opened files and open any other file afterwards" answer and that brought back the Search menu items. Additionally, if you were lucky and have the Search result view open, than indeed there is this little link "Open search dialog".
By the way, additionally lots of other project-related menu items seem to be greyed out also together with this, and they did not reanimate :-( But I did not really check out if these are only items for which it is useful and planned to be greyed out in this situation.
I'm using RAD 7.5.1 which runs on Eclipse 3.4 and I get this problem frustratingly often. It doesn't matter which perspective or view I'm in, or which editor I have open.
Restarting RAD usually clears it up, but because that's such a colossal pain, I found that you can get around it in the Search View, there is a link; "Start a search from the search dialog" which will bring up the search dialog.
This isn't a great workaround because the link only shows if you have no search history. To do another search, you'll have to clear your search history in the view.
A late comment for anyone getting bitten by this, but I found "eclipse -clean" fixed it => this does a cleanup of the workspace before starting
Thanks http://letsgetdugg.com/2009/04/19/recovering-a-corrupt-eclipse-workspace/ for the tip, after I guessed my workspace might be corrupt.
Before search, check you may choose scope in empty Working set. Most Search menu disables Search button when you choose it. And mine, too :)
window > close all perspectives worked for me too.
But if you are just looking for a text search in the project you could press Ctrl+Alt+G on a marked text
I couldn't get it to work even when restarting Eclipse.
Here's what worked for me: Closing all open files and opening a different file. The different file happened to be .java, but not sure if that had anything to do with it.
I get this problem from time to time.
In the past I've fixed by starting eclipse with the -clean option.
Once when that didn't work I created a new workspace.
I followed these instructions for those two solutions.
The clean option didn't work for me today and I found this thread because I didn't want to create a new workspace. The closing all files and reopening one file did work however.
I had this issue also in eclipse 3.6.2: Helios Service Release 1.
Closed all the editor windows, and the search has been enabled.
Switching to another perspective, then back, works quickly for me.
I've faced similar issue in Ctrl+H "File Search" tab. The "Search" and "Replace" button was grayed out (disabled). The solution is fill the "File name patterns" text box (for eg, *.py). May be this is by design!
I have this problem with MyEclipse 7 (eclipse 3.4) under Debian Lenny. Perspective doesn't seem to matter. I get around it with the shortcut Ctrl+H but I was hoping for a better way.
Just had this problem in Eclipse Neon 3. It is a very common problem in RAD. I could find using in the console, then switch back to the source and search. RAD would disable the find/search options per source file open. This is very frustrating.
I had this problem too. It appeared when I installed the m2eclipse plugin.
I had not found a solution, but you can use Ctrl+H shortcut instead.
And you can navigate between tabs with Ctrl+PgDown or Ctrl+PgUp keys.
I've uninstalled the following pluings and it worked.
Maven integration
PMD
eclipse checkstyle plugin
EclEmma (coverage)
I don't know which of those cause the problem. To uninstall a plugin: Help -> Software Updates...-> "Installed Software" tab.