command line to tell a running Code::Blocks to open a file

[DrewBoo]

I'm in Unix-land, and often find myself at the command line using my terminal application of choice.

Is there a way to tell the Code::Blocks instance which I am already running to open a particular file?

Using "codeblocks --file=MyFile" always opens up a new Code::Blocks (or, based on my settings, tells me it can't open a new Code::Blocks and aborts)



DrewBoo

[mariocup]

Hi DrewBoo,

under windows it is already possible using the DDE command. Under Linux this feature is currently disabled, but it think it could be added in app.cpp. wxWidgets provides IPC communications with a special class that is using under the hood either real windows IPC or TCP on other platforms.

Bye,

Mario

[Jenna]

On my debian-system, I just added a wxClient-class to C::B (with #ifndef __wxMSW__) and reused the most part of the actual DDEServer for MSW to open a file inside a running C::B-process.

For test-purposes I hardcoded the filename, and it worked as expected.

If it will be implemented the question is, how should it work ?

Shall it always try to open a given file in a running instance of C::B, or only if multiple instances are not allowed, or should another instance of C::B only be opened if no filename is given on commandline, or ...

I hope I found some more time this week and maybe this weekend to work on it a little more.

[DrewBoo]

If it will be implemented the question is, how should it work ?

Shall it always try to open a given file in a running instance of C::B, or only if multiple instances are not allowed, or should another instance of C::B only be opened if no filename is given on commandline, or ...

You bring up good questions.

It would certainly be safest to implement this specifically for "no multiple instances" mode.  That is, no user could reasonably be jostled by this change.

Then again, if Code::Blocks already has similar behavior in Windows, the best design is to match that behavior.