It was a typo. It should have been printenv.
It was a typo. It should have been printenv.
I've always used 'env' instead. I'm lazy. Don't want to waste extra characters. Feels a little like the MS-PowerShell command names which are really-long-to-be-descriptive-but-unnecessary-if-you-know-the-shorter-version-already.
In complex programs, I prefer long-descriptive-names. Not so much for 1-line commands.
We are getting way off topic here. The problem is solved. And the user is running X, no matter how many similar commands s/he runs to tell us that.
Bookmarks