show environment variables appropriate for Mac client

Hi,

Don't forget that this is a cross platform application. Said variables could be used inside a session that as been set by a Windows user in a shared session. So, you can see them as purely informative.

We're not resolving environment variable in Mac as of yet, so this wouldn't be of much use either way.

Best regards,

Would still like to see this. Would have been helpful with SSH agent auth...

Hi Jo,

Well, I don't see why we couldn't add a Environment Variables Mac section. Except everything in printenv, do you see anything else that could be relevant?

As for the nomenclature, I can't really use %<...>% to prevent conflict with Windows variable. I could do it like the other sections, something like $MAC_<...>$ (replacing <...> with the name of the actual environment variable).

Or did you see it more as a kind of binding between the environment variables of Windows and those of Mac (when applicable) to keep as much as possible the cross platform behavior between RDM Windows and RDM Mac. (%USERNAME% -> $USER, %HOMEPATH% -> $HOME, etc.)?

Best regards,

I'm not thinking of cross platform, I'm only thinking of "I'm on a Mac and want to know what variables are available for me to use on Mac" ;)

I understand you have cross-platform complications but I have no strong opinion about that. I personally would not attempt to map back and forth, because I work with tools that do that and there's always a million problems because of mismatched expectations. Although I wouldn't mind if $VAR sourced from X on Mac and Y on Windows, they are your variables use them as see fit.