I am trying to write some more advanced Integration scripts (for example Interface methods automatic implementation, PhpUnit coverage). I have realised that some macros in Integration settings are NOT WORKING at all - they are copied to command line verbatim instead of translating to their meaning:

@RelFName@
@RelPath@
@RelDir@
@Project@
@ProjectRoot@

Also, for better scripts possibilitis I would suggest new macros:

@CurrentLine@
@CurrentColumn@

Looks like you're doing something wrong, but it's not possible to say what without the details.
I'd add that macros are working fine. Otherwise, no other integrated commands like CVS Update would work.

No, CVS Update is not using these macros, it is using @Name@ and @Repository@. These work. The ones I have listed DO NOT. Try it.
For example (use execute with shell).



Output is:

It depends on where you're using these macros. For example, @Project@ is not known if you call it from the Explorer popup. Only Workspace's popup knows @Project@ and expands it appropriately. Same goes to the other macros you listed.

Ok. Then it does not allow to bind hot key to such macro (the main way I use integration) or menu on file tab - the macros are not working there.
They should work there, opened file knows which project it belongs to, right?

it does allow. Please use appropriate popup in the integration settings.



No, file tab does not know this info. File may belong to one or many projects or even neither.

Uff. No. I append a key, but macros (@project etc...) are not expanded then. See my example.





Then project related macros should expand ALWAYS according to active project.

@project is not a correct macro, should be @project@. From your example it's clear that you tried to bind commands to file tab's popup, while the macros used are supported by workspace's popup only.



I explained how it was designed and how it actually works. If you think about improvements, please post your request on this forum