Something has changed from Indigo to Juno which has made me much less efficient:
Content Assist menus items can't be cycled through using the "Line Down" shortcut anymore
Is there anything I can do to bring back the working behaviour?
Setup:
OSX Mountain Lion (v10.8.3)
Eclipse (v4.2.2, Build: M20130204-1200)
Command: "Line Down", bound to: CTRL-N, when: In Windows
Shortcut to invoke Content Assist: OPTION-/, when: In Dialogs and Windows
Note:
The exact same configuration, changing only Eclipse to Indigo (Version: 3.7.2; Build id: M20120208-0800) works perfectly. I have lots of muscle memory to undo if I can't fix this.. :(!
Reward:
I want to set up a bounty for a solution to this but it says I have to wait 2 days before doing so..
Reference links:
Navigating the Content Assist List in Eclipse
One thing you can do is go to
Window->Preferences->General->Keys
And from there you can change the binding of the commands you want to use. They are all there from copy and paste to running tests and refactoring. So if you assign several Ctrl+N you will get a list with all the commands you bound to and can click on the one you want.
Is this kinda what you had in mind?
Related
When working in Eclipse and hitting Ctrl+F with lines of code selected, the default behavior I expect is for the Find/Replace dialogue to open with the "Selected lines" option and, perhaps, either buffer contents or a previous search query in the "Find" prompt. On my home machine, what happens instead is the entire selection gets automatically copied to the "Find" prompt and Scope is reset to "All" instead of "Selected lines" every time.
I somehow do have this working by default on my work machine: "Selected Lines" scope option is chosen automatically when more than one line is selected in the editor.
Possibly unrelated: I do have CDT installed and I work mostly with C++ in Eclipse. Home machine is running Ubuntu 18.10, work machine is running Ubuntu 18.04.
I tried:
Re-downloading Eclipse, reinstalling CDT & cmake4eclipse
Changing to a new Workspace in Eclipse (without copying settings)
Searching high and low online for recipes on how to control this.
How do I change the IDE at home to the desired "Selected Lines" behavior?
[Edit 1 hour later]: I am now almost convinced the issue has to do with the Ubuntu version somehow. I'm running 18.04 on my Laptop (same as my work computer) and I just upgraded CDT & Eclipse Platform to latest stable versions (9.7 and 4.11/2019-03, respectively), which I have everywhere else. The new "wrong" behavior didn't appear. I will also start a thread on the Eclipse forums or perhaps even open a bug report. I don't want to reinstall the whole system or downgrade it (slim chance of success) just to get this back; if it's an Eclipse bug, I'd rather work on fixing it.
[Edit 2 days later] The bug did not manifest on a fresh install of Ubuntu 18.10. I still have no idea what was different on the 'culprit' machine. I ended up wiping the drive and reinstalling 18.04 on the same machine and the problem went away.
I am using Eclipse Neon on Fedora 24. The look and feel is not as great as Eclipse on Windows - for example, it takes a long time for the mouse pointer to become draggable when on the border of two windows. What are some potential solutions to improve this.
Thanks
A few things to consider:
Sometimes certain plugins cause glitches. For example I know Javascript plugin interferes with C development sometimes. Try a fresh upstream Eclipse with a fresh workspace, ex try the latest 'maintenance' eclipse:
http://download.eclipse.org/eclipse/downloads/
These often have the latest fixes.
If you've turned on the black theame, you could try the regular white theame as currently there are some u.i issues specific to the dark theme. ex:
499515: [Gtk3][Dark] Click on package explorer only works on second click when dark theme is enabled
https://bugs.eclipse.org/bugs/show_bug.cgi?id=499515
Some Window managers (ex i3) tend to introduce visual glitches in Eclipse. Try alternative window managers or the standard 'gnome' to see if there is a difference.
If you're running wayland, currently Eclipse is a little unstable on wayland, but port is in progress: 496923: [Wayland] Improve support for Wayland in 4.7
https://bugs.eclipse.org/bugs/show_bug.cgi?id=496923
You should also consider submitting a bug with more specific details of your setup, (help -> about -> installation details -> Configuration, copy and attach). To do so, go here:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform
Select "SWT" from Component.
If all else fails, I often hang out on freenode#swt, feel free to ping me there. (lufimtse)
Try this
https://coffeeorientedprogramming.com/2016/10/06/make-applications-eclipse-use-x11-backend-on-wayland-fedora-25/
and I modified my /usr/share/applications/elipse.desktop exec parameter, like this
Exec=env GDK_BACKEND=x11 eclipse
my eclipse.desktop =>
[Desktop Entry]
Type=Application
Name= Eclipse
Comment=Eclipse Integrated Development Environment
Icon=/opt/eclipse/icon.xpm
**Exec=env GDK_BACKEND=x11 eclipse**
Terminal=false
Categories=Development;IDE;Java;
Terminal=false
StartupNotify=true
Encoding=UTF-8
I have some problems with eclipse indigo x64 Linux; The problem is using windowbuilder (the SWT); I tried using gwt or swing but they both cause either windowbuilder freeze or even eclipse crash...
The alike issue it seems I found related info in official eclipse indigo offline Help which says :
How can I prevent the preview window from flashing under Linux using Metacity
In order to create the graphics that you see in the design view,
WindowBuilder Pro creates an off screen window containing the various
widgets and they takes a screen snapshot of them. This works very well
under Windows, OSX and some versions of Linux. Recent versions of the
Metacity window manager (more recent than 2.1.4), however, have been
modified/"fixed" to disallow windows to be opened off screen. This
forces the preview window to appear on screen leading to an annoying
flashing effect any time you make a change. The solution is to disable
the Metacity "fully_onscreen" constraint by patching the Metacity
source code and rebuilding and installing the patched version into
your system.
Here are the steps to follow:
Download the Metacity source code from ftp://ftp.gnome.org/pub/gnome/sources/metacity/
Unpack the source code tarball into any temporary directory.
Chdir into this directory (with the unpacked code).
Find window.c file and open it with your favourite texteditor.
Find a line with "window->require_fully_onscreen = TRUE;"
Replace it with "window->require_fully_onscreen = FALSE;"
Save the changes and close the editor.
Open a terminal and chdir into the directory with the source code (nice if you have already done this)
Run "./configure".
Run "make all".
Make sure that steps 9 & 10 completed without errors.
Become root (or execute the next command via "sudo" depending on the Linux you are running)
Run "make install" (or "sudo make install").
Save your work and close any application you are working with.
End your session (or press Ctrl-Alt-Delete to restart the x-server) and log in again.
You are done!
well seems like I have the snapshot really but, as I can get it, the snapshot doesn't want to dispose or similar so I have either resize the whole eclipse or press F5 to refresh (which works not at once);
I am not sure how to fix the issue in case I have xfce+adwaita installed? I don't have metacity installed; Seems like xfce works with gtk instead of metacity (correct me if I am wrong);
So my question is... how to fix the "window flashing or freezing" if I have :
xfce4
adwaita-dark theme
linux arch x64ce
Thanks
Try to install install libswt-gtk-3-jni and libswt-gtk-3-java.
I am on OS X 10.8.2 and Eclipse Juno; Copy/Paste/Cut suddenly broke. No response inside Eclipse.
Maybe a rogue plug-in (?) but that doesn't matter, can I just reset the values?
Which combination should I bind to COMMAND+{C,V,X}?
Paste from the clipboard in "Editing Text"
Paste from the clipboard in "Dialogs and Windows"
Paste from the clipboard in "Windows"
Other?
If you know how to do this in a preferences file, even better, I use keyConfigurationId="org.eclipse.ui.defaultAcceleratorConfiguration" but I don't know how to choose these parameters for the keyBinding rule in
org.eclipse.ui.workbench/org.eclipse.ui.commands:
contextId
commandId
In my installation, those commands are set to in "Dialogs and Windows". You should be able to also get that automatically by hitting the "Restore Command" button after selecting one of those commands. Or in very hard cases, use "Restore Defaults" in the bottom right corner to recreate all key bindings.
If you use the Android Development tools, please upgrade to the latest version, as a copy-paste-issue was fixed in ADT 20.0.2, which occurred for many Eclipse Juno users.
That all said, you really should upgrade to SR1, as that is a bugfix release, no feature release. So chances are very high it fixes more problems than it introduces.
I'm using Eclipse + pydev plugin as the development environment. In fact my application needs a big console area and I usually resize the console and minimize it, so that whenever I run the application, it automatically shows up.
But when I minimize the console view or detach it or mark it as Fast View, the toolbar for controlling the running process and locking the scroll disappears.
Can I have both minimize functionality and Process control toolbar ?
Eclipse : Galileo Build id: 20090619-0625
Pydev : 1.5.3
Right now, in Eclipse/PyDev, you can't have the toolbar when it's minimized (you have to open it to access it), but most of what you need should be available through shortcuts (some may need focus on a PyDev editor):
Terminate current process: Ctrl+F2
Terminate all processes: Ctrl+Alt+F9
Terminate / relaunch last launched process: Ctrl+Shift+F9
To launch the currently open editor: F9
To relaunch the last launch (provided you followed the steps at: http://pydev.org/manual_101_run.html): Ctrl+F11
To debug the last launch: F11
To show the console view: Alt+Shift+Q, C
And if you want, you should be able to configure those in the keybindings (Ctrl+Shift+L twice to open the preferences page to do so).
I used eclipse with pydev and it drove me nuts. I use Netbeans 6.8 right now which came bundled with its own python plugin that is a lot better. Especially when it comes to debugging.