In our case, adding a Get Specified Finder Items action allows us to choose a valid file and test the outcome of the action:Īutomator provides error and success messages in when running tasks, a luxury that using the context menu may not provide you. The best method for testing and debugging an Automator task is by adding additional actions to the task to simulate real usage. The name you save the task as is what will display as the context menu name.ĭebugging and Testing the Context Menu Item File -> Save in the menu bar to save the Automator task.You can add additional checks to ensure the file is of the correct extension and other validation using a bit more scripting. # For every file, unrar it to the current directory Now you can write whatever shell scripting you'd like, receiving the file arguments as My script to unrar'ing files is overly simple:.When the Run Shell Script box appears in the right pane, change the Pass input value to to arguments.Within the left actions pane, select Run Shell Script.Within the right pane's top panel, choose files or folders from the first dropdown and then Finder.app from the second dropdown.The following steps will have you on your way to adding a context menu within macOS Finder: The example we'll use is creating a context menu to unrar rar archives. That UI on Mac is Automator let's explore how we can add custom context menu items within macOS Finder! Creating a Context Menu Item with Automator The problem is that yarn install, brew install, and other package managers don't come with UI extending capabilities.so knowledgable people like us need to find a way to shoehorn those functionality into a UI. As much as I like exercising my command line skills, for many tasks I'd rather click a time or two.

Matlab context menu left click mac