In my case, I created a filed called disable.txt that contains only the following line, torun my desired AppleScript: osascript /Users/Dave/Scripts/disableHotCorners.scpt txt file that contains the commands you want to send to OS X'sTerminal. Save plink.exe intoC:\Windows\System32 (this is not strictly necessary, but it makes writing batch scripts alot easier, as we will be able to call plink.exe directly - much like when we put an app in one ofOS X's system directories so we can call it directly in Terminal without having to specify its exactlocation).
#Shell program for mac download#
You can download it (as well as a GUI-based Terminal emulator, 'putty.exe') from here.
The utility that makes this work is a small Windows-based command line ssh client, called plink.exe.
Well, none of us would behere if we didn't believe that anything requiring requiring 10 seconds work couldn't be achieved inless than 1, would we? Richard Kulesus created a great pairof AppleScripts to disable/enable Active Screen Corners, but switching it on and off involvedmoving away from my virtual machine, running the script, and moving back. My workmates freak out a little when using my laptop, because every time they hit a corner of thescreen it activates Dashboard, Spaces, or Exposé.
#Shell program for mac windows#
Now, let'steach Windows to speak a little Unix. Bear inmind that this requires at least a middling knowledge of Windows - this is probably most useful toMac owners who have to run Windows at work and have some level of familiarity with it. In this example, we will be using Richard Kulesus' excellent, freeAppleScripts to disable and enable Active Screen Corners, directly within our Windows VM. It's important that this solution be scriptable, so we can create double-clickable actions toperform common tasks. Even though I'm working in a Windows environment, there are so many useful thingsthat can be done via AppleScripts or Terminal commands to control network, system and componentsettings, that it can be very useful to run them directly from the virtual machine.Īfter messing about with clunky folder actions that would trigger an Automator action (or launchdplist) to arbitrarily kick off scripts, it occured to me that a much better way of doing this wouldbe to find a Terminal client on Windows that could ssh into the OS X host and run commandsdirectly.
directly inside my Windows virtualmachine at work. Sometimes I want to run AppleScripts, bash scripts, etc.
0 kommentar(er)
