I use Eclipse (4.2.1) to develop Python (3.2) programs using PyDev (2.8.2). I start my program in debug mode and when I encounter the first breakpoint, a new tab is opened with a copy of the script containing the breakpoint.
Debugging then takes places in the new copy.
When I stop debugging, the tab with the copy remains.
Changes to the copy, must be saved to update the original tab.
How can I make Eclipse NOT open a separate copy of my program?
Status: I still have this problem!
Related
I have a file open in Eclipse. I make some changes (new lines, type some stuff), and it never indicates the file has been changed (with the * on the file tab). So I ctrl+s to save, close the file, re-open it, and my changes are not there.
Context
Eclipse Build Details
Eclipse Platform
Version: 2020-06 (4.16)
Build id: X20200903-1448
OS: Linux, v.5.8.11-200.fc32.x86_64, x86_64 / gtk 3.24.23, WebKit 2.28.4
Java version: 11.0.8
Other
Vrapper (VIM) extension
PHP project
Happens in multiple projects
Only happens in PHP files
Reproduce
Double click a file to open. Starts in Normal Mode (VIM)
go to a line & press O to create a new line
Type echo "zeeb"; exit;
Now, there should be an asterisk next to my filename on the file tab, but there isn't.
At this point, if I click with the mouse & select some text, the asterisk will appear most of the time. Then I can save. Or, if I go back into normal mode, the asterisk appears
What I've tried
Project -> Clean
Project -> uncheck 'Build Automatically' (same behavior either way)
Closing all Eclipse windows & re-opening just one window
Disabling vrapper <- this works! But I need my vim.
Adding :set noatomicinsert to ~/.vrapperrc seems to have fixed it.
Vrapper Settings states:
Whether inserts should be handled as atomic operation. This causes problems sometimes, so it is deactivatable.
This is kind of a weird question so bear with me.
I found a way to allow unlimited output in the 'debug shell' view and then I executed a function in the Eclipse "debug shell" (used to be known as 'display') and it produced an output so large that it breaks my Eclipse. This forced me to reboot eclipse. Unfortunately, now everytime I open Eclipse it tries to open that view again, and so my eclipse is sort of permanently broken. Is there a settings file I can go into somewhere and dump so that it doesn't keep trying to load that garbage everytime I boot Eclipse?
Thanks
The answer lies somewhere in the eclipse .metadata directory (at the root of your workspace). I closed my eclipse, deleted this directory, and then restarted my Eclipse and was able to open up the debug shell again. Keep in mind this will delete all your Eclipse settings and have to restart from scratch again, however its worth it for me because I have to have this debug shell.
I've been working with Eclipse for years, but its PyDev wasn't working on my new Mac...so I swapped to LiClipse.
In Eclipse, when I have an open file that I'm editing and click run...it runs the file that's open and visible in my editor. But apparently LiClipse always tries to run the 'main' file thats set in the 'run configuration'.
Is there a way around this so I can test the module I'm actually working on and not the entire package?
Use F9 to run the file you're working on -- or Ctrl+F9 if it's a Python unit-test (Ctrl+F11 will always rerun the last launch by default in LiClipse -- you may change that in preferences > run/debug > launching > launch operation), although I recommend you use F9 to run your modules (or Ctrl+F9 for unit-tests), relaunch the last with Ctrl+F11, debug the last with F11.
http://pydev.org/manual_101_run.html has more details on running your modules
http://pydev.org/manual_adv_pyunit.html has more details on the unittest integration
Let say I have a working Eclipse project . The debug configuration is set up correctly such that I can launch Eclipse and start debug mode with a few clicks. No other run time input is needed and a breakpoint is already added to the beginning of the program.
Instead of clicking, I want to know if there is a way that I can do this from a terminal. Basically I want to script the command. I've found the options to disable splashdown and select the workspace. The Eclipse version is Luna. Thanks.
Check the properties of the process that's in the Debug view when you start it from there. Also: http://help.eclipse.org/luna/topic/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
I have written a small piece of code in C++(gui/wxWidgets) . It compiles/ links without any errors and produces an executable that when launched from command line opens the desired 'Hello World!' window, but when tried from within eclipse (menu, toolbar or ctrl-F11), it doesn't run. A quick error dialog appears/disappears before it can be read. After many runs I could make out that of the two msgs it displays, one reads something like "Looking for executables...". Apparently eclipse is unable to get to the executable in the Debug folder.
I tried a console application which runs without any issue from within eclipse as well.
My installation is indigo on Ubuntu 12.04.
Any ideas what could be the problem?
Problem resolved.
There was no Launch Configuration in Project Properties -> Run/Debug Settings.
Added one with defaults and it worked.