You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Knowing the hostname is useful. Recently I was importing a foreign machine config file (checking issues on the Mac) and noticed that the script was using the name of the machine where I was uploading it, not the name of the original machine. Given that machine name is an important human-usable clue where something originated, this is undesirable.
I think the right thing to do is to capture this information in the machine configuration file. This would require changes on all supported platforms, but the actual implementation is simple (gethostname()).
The text was updated successfully, but these errors were encountered:
Knowing the hostname is useful. Recently I was importing a foreign machine config file (checking issues on the Mac) and noticed that the script was using the name of the machine where I was uploading it, not the name of the original machine. Given that machine name is an important human-usable clue where something originated, this is undesirable.
I think the right thing to do is to capture this information in the machine configuration file. This would require changes on all supported platforms, but the actual implementation is simple (gethostname()).
The text was updated successfully, but these errors were encountered: