Here docs and here strings were introduced exactly to avoid this. This syntax ( echoing into a pipe) is considered inelegant and inefficient, because it requires an additional process ( echo) and an additional pipe. This will make Posix sh, dash, and shellcheck happy and will still work in bash and zsh. Over time, different contributors in the MacAdmins Slack have optimized this command: loggedInUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk '/Name :/ & ! /loginwindow/ ' ) With prescient timing, Erik Berglund figured out a different method, which still accesses the same system framework, but through the scutil command rather than the PyObjC bridge. But in the macOS Catalina release notes, we have learned that some, yet undefined, future version of macOS will not include the Python, Ruby, and Perl interpreters any more. This used to be fine, as the python binary shipped with macOS. While this has worked wonderfully and more reliably than other solutions, it always looked inelegant, and added a dependency on the python binary. But there are edge cases, mostly with Fast User Switching, where these methods don’t return the correct user.
There are various other solutions to get the current user which use stat, who, or last commands. However, the semi-official, “sanctioned” method has always involved a rather elaborate python one-liner, originally published by Ben Toms: loggedInUser=$(/usr/bin/python -c 'from SystemConfiguration import SCDynamicStoreCop圜onsoleUser import sys username = (SCDynamicStoreCop圜onsoleUser(None, None, None) or ) username = ] (username + "\n") ')
There are many solutions to get the current logged in user in macOS to use in a shell script.
#How is default path set in bash for mac os x how to
…or, how to deal with deprecated bash and python…
0 kommentar(er)
