an easy one: run without compile

hi all...

I have been switching back and forth between compile before running and no compiling lately.

It seems it would be useful to be able to run with or without compiling without having to always having to check/uncheck the option in the "edit configuration" panel.

It could just be as simple as an added menu item in the run menu: "Run Without Compiling"

Florian Hehlen

5 comments
Comment actions Permalink

Run dirty flag, I'm in...

+1

0
Comment actions Permalink

Florian Hehlen wrote:
>

It could just be as simple as an added menu item in the run menu: "Run Without Compiling"


What about including the settings for "Make module before... " and "Display settings before ..."
in the actual run-config, instead of just one global flag? Looks more natural to me and I don't
think the toolbar should be cluttered by a very rarely used button.

With 98% of my run configs I don't want to see the settings pane and do want to compile
before running. The remaining 2% are some odd configs that should take variable command line
parameters or should not try to make the module, but configuring that is not quite possible now.

Sascha

0
Comment actions Permalink

What about including the settings for "Make module
before... " and "Display settings before ..."


for me this is not a setting. This is just for how i want to run the code... like run and debug. I would like it to be a single key-stroke away.

But I do agree that the current settings that apply to all configurations is not very useful.

Florian

0
Comment actions Permalink

I don't quite agree on this subject. Well, you could have settings on a per module basis, that would be alright.

Anyway, if in most cases you don't want to show the settings and want to compile you should leave the settings that way, when you'll want not to compile just enter the "Edit configuration..." submenu and uncheck the option, it's just two more clicks...

I have never had the compile option active, come on, just press Ctrl+F9 and then run.

Having settings for each module would be fine, but i definetly don't want another button that most of us would never use.

0
Comment actions Permalink

Having settings for each module would be fine, but i
definetly don't want another button that most of us
would never use.


There is a missunderstanding. I don't want a per module setting; I want one for each run/debug configuration.

And the reason why ctrl-shift-F9 + ctrl-shift-f10 is not always handy, is that I work with a relatively big J2EE project and even pressing ctrl-shift-f9 with nothing to compile can take up to 30 seconds...

So what I really want is to be able to switch between dirty run and clean run.

And there appears to be a solution: macros! I can get what I want with macros. So if I set the current setting to never compile before running and then use a macro in cases when I want to compile first. This has the side effect that I have to compile in the forground otherwise the macro does not wait for the build completion. It would be good if macros could have a notion of witing for a background-action to complete. Then my problem would be totaly solved and there are a few other handy things I could do with macros.

Florian

0

Please sign in to leave a comment.