If you make the Scripts menu visible, as explained in the previous item, you can choose this script at any time to open your Library folder.
Save the script in Script file format in your Scripts folder ( ~/Library/Scripts-alas, in the Save dialog, you’ll need to use the Go To Folder shortcut-Shift+Command+G-just to get to the Scripts folder). Launch AppleScript Editor, create a new script document, and enter the command do shell script "open ~/Library". Use an AppleScript Speaking of AppleScript, you can create a simple script that opens your Library folder. Perhaps the easiest option here is to activate Apple’s Scripts menu (via the preferences window for AppleScript Editor, which is in /Applications/Utilities) this systemwide menu includes an Open User Scripts Folder command. Do so, and then navigate up the folder hierarchy (by right-clicking the Finder-window’s title-bar icon, by pressing Command+Up, or, in column view, by scrolling to the left) to view the contents of your Library folder. Use an application that provides access Some applications that store files in ~/Library (usually in ~/Library/Application Support) include a button or menu command for opening that program’s support folder. Just type ~/Library and click Go to view the folder in the current Finder window. Use Go To Folder The Go To Folder command, in the Finder’s Go menu (also accessible by pressing Shift+Command+G), has long been a quick way to access invisible folders such as /Volumes and /usr it’s now useful for accessing your Library folder, as well. You can use the Go menu’s Go To Folder command for occasional access to ~/Library. If you’re the kind of user who rarely visits ~/Library, but you’d like to be able to open it if the need arises, these methods are for you. I’ve come up with 18 ways to do so which one(s) you choose will depend on how frequently you’ll need to access the folder and which method better fits your workflow.
You just need to know how to access the folder or, if you prefer, unhide it. Luckily, as I mentioned, the folder is just hidden, using a special file attribute called the hidden flag. While I understand Apple’s motives here-I’ve had to troubleshoot more than a few Macs on which an inexperienced user had munged the contents of ~/Library-there are plenty of valid reasons a user might need to access their personal Library folder. But that’s fodder for a different article.)
Yes, I realize that’s a questionable assumption, given that the first user account on a Mac is always set up as an admin account. (Why hide ~/Library but not /Library, the similar folder located at the root level of your drive, which holds systemwide support files? Most likely because only admin users can modify /Library, and Apple assumes that a user with admin-level privileges will know what he or she is doing.