Path display on Windows is not consistent

[ilg-ul]

While updating the CMSIS Packs, the console displays some paths with POSIX syntax, and some with Windows syntax.

An initial check showed that the code correctly uses getCanonicalPath() which should generate the POSIX path, but, for unknown reasons, sometimes this does not work.

[TommyMurphyTM1234]

Apologies if this might be slightly off topic but isn't there a strong argument for making "/" the default path separator regardless of OS since it's compatible/portable across Windows, linuxes, Mac?

Edit: I may have misunderstood. On reflection it looks like canonical (using "/") paths is already the intention here?

However I meant using such paths everywhere but maybe that's not totally within the control of the GME/xPack plugins as some may be controlled by CDT, Eclipse or other plugins?

[ilg-ul]

Yes, during the latest changes to improve the CMSIS Pack updates, I also updated all code displaying lines on the console to using getCanonicalPath(), expecting to see only nice POSIX paths in the output.

For reasons beyond my understanding, some lines still show back-slashes, and I'm a bit confused by this, I don't know what I did wrong.

Can you confirm that this happens on your Eclipses too?