i have read thru the bug listings and features, and i cant see a reason why the highlight config files arnt correctly parsed, so items like $(FilePath) are converted to the path, they just appear in the commandline as strings. is this a bug or am i just going about it the wrong way?
it seems to affect build, compile and run in the same way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-11-07
aah, if only there was an edit button, and maybe i wasnt so tired, i ment to say:
they just appear in the commandline as <i>empty gaps</i>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
$(FilePath), $(FileName), etc. are special variables which are only expanded for the Build, Compile and Run commands. They are appearing as empty gaps in the actual command being executed, correct? Is the rest of the command being executed correctly?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tested what you are saying and you are totally correct. It seems as if some of the new config file code is trying to expand the variable when it should not be. I'll make sure to get this fixed in the next version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i have read thru the bug listings and features, and i cant see a reason why the highlight config files arnt correctly parsed, so items like $(FilePath) are converted to the path, they just appear in the commandline as strings. is this a bug or am i just going about it the wrong way?
it seems to affect build, compile and run in the same way.
aah, if only there was an edit button, and maybe i wasnt so tired, i ment to say:
they just appear in the commandline as <i>empty gaps</i>
$(FilePath), $(FileName), etc. are special variables which are only expanded for the Build, Compile and Run commands. They are appearing as empty gaps in the actual command being executed, correct? Is the rest of the command being executed correctly?
I just tested what you are saying and you are totally correct. It seems as if some of the new config file code is trying to expand the variable when it should not be. I'll make sure to get this fixed in the next version.
This should be fixed in v0.18.