

- #Autohotkey martin mpc how to#
- #Autohotkey martin mpc install#
- #Autohotkey martin mpc portable#
- #Autohotkey martin mpc download#
- #Autohotkey martin mpc mac#
(If you end up liking it, you can put a shortcut to it in your Windows Start Menu “Startup” folder, to automatically load the script every time you log in.) To load the machotkey.ahk script and “activate” its keyboard shortcuts, double-click on the script file in File Explorer. If you want to be able to compile your scripts into standalone executables (*.exe files), enable (or don’t disable) the “script compiler” option when you’re installing AutoHotkey.
#Autohotkey martin mpc install#
To use the script, you first have to install the “Current Version” of AutoHotkey, from here:
#Autohotkey martin mpc portable#
You can store your AutoHotkey scripts in any folder you want, but I find that my arrangement makes it easy to back up my portable programs and scripts and sync them with other Windows computers. The scripts that other users might want to use are in:Ĭ:\Program Files (portable)\AutoHotkey ScriptsĪnd the ones that only I would probably want to use are in:Ĭ:\Users\MyUserName\Program Files (portable)\AutoHotkey Scripts I keep my AutoHotkey scripts in two special folders I created.
#Autohotkey martin mpc download#
(There may have been a download link available somewhere, but I was done poking around by then.) I copied the script’s contents, pasted them into a new Notepad++ tab, and saved it as machotkey.ahk.

In this case, I found what I was looking for (machotkey.ahk) here: Github confuses the hell out of me too! I often have to spend an *unreasonable* amount of time poking around in a project’s various subdirectories. I’m pretty sure this article has gone through a couple/few revisions and I’m not going to read it from top to bottom again, but from a quick scan I think Ashwin just accidentally typed. There is no precompiled executable available for download. SHORT VERSION: Yes, the shortcuts *can* be you don’t want machotkey.EXE (an executable), you want machotkey.AHK (an AutoHotkey script). Make sure you save a backup copy of the original downloaded script before you start hacking away, in case you screw up and need to start over. I’d steer clear of modifying any of the “non-shortcut” lines until you have a decent understanding of their code.
#Autohotkey martin mpc mac#
Experienced Mac users will be able to guess a lot of them from looking at the left side of the line experienced Windows users will recognize a lot of them directly. Ideally, you will want to know what the original Windows keyboard shortcuts on the right side of the shortcut lines do before you start modifying the script’s shortcut mappings. If you don’t want a particular shortcut, just put a “ ” (without the quotes) at the beginning of its line. = comments out all following text up to and including the next hard line break (not automatically wrapped line breaks). AutoHotkey’s documentation on “Remapping Keys” and “Hotkeys” are good places to start.
#Autohotkey martin mpc how to#
NOTE TO NON-CODER AUTOHOTKEY NEOPHYTES (like me): AutoHotkey can be pretty complex, but if you just want to hack this particular script a bit, it shouldn’t be *too* hard to figure out how to comment out or modify some of the keyboard shortcuts. However, it apparently only takes a “right-click, Compile Script” command in File Explorer to compile scripts into *.exe programs, provided you’ve enabled the script compiler option when you installed AutoHotkey (or when you re-install it). I’ve never had a reason to compile any of my AutoHotkey scripts (e.g., to share them with people who don’t use AutoHotkey). Then you can run it as an AutoHotkey script, edit and reload it, and, when you are happy with the results, either continue using it as a script or compile it into your own, customized “portable” utility. (The AHK prefix is a pretty big tip-off, even if you don’t read the Github project’s readme.) Accordingly, if you download (or copy and save as) the machotkey.ahk script from the Github AHKShortcutLikeMac project, you *can* edit the shortcuts. *Love* the laptop its keyboard, not so much.)Īlso, it’s an AutoHotkey script. (My typing accuracy is going downhill with age, and my current laptop’s keyboard isn’t helping. That’s why I try to copy-and-paste from a known-good original for such things when I can, instead of typing from scratch. I don’t care that much about inconsequential typos, but I *do* care about them in program names and code. Part of the typo is still there: “AHSKShortcutLikeMac” with a stray S between the H and the K instead of “AHKShortcutLikeMac.”
