5 AutoHotkey Scripts for Data Scientists

The notebook is ready and the actual work has not started. First the project folder, then the editor, then the terminal, then the tab with the docs. Then a column of customer IDs arrives in a spreadsheet and has to become a Python list, so it goes through a web formatter of uncertain ownership. Then a file path copied from Explorer has to lose its backslashes before the notebook will read it. Then the windows get dragged into the same arrangement as yesterday. None of that is analysis, and all of it happens before analysis on most Windows machines, most days.

AutoHotkey exists for this layer. The five scripts below are small, and each removes one of those rituals without touching the data pipeline itself. That boundary is the point, so it gets a section of its own first.

The five scripts, the desktop chore each one takes over, the AutoHotkey feature that does the work, and the first thing to watch. Alt text: four-column reference table listing a workspace launcher, a clipboard-to-list converter, analysis hotstrings, a path formatter, and a window layout hotkey with chore, feature, and caution columns. Credit: original reference table based on the AutoHotkey v2 documentation.

Before the Scripts: Keep AutoHotkey in Its Lane

AutoHotkey is a free, open-source automation utility for Windows, and its scripting language was built around one idea: a keyboard shortcut can run any code you like. The tool is Windows-only in the plainest sense: on a Mac or a Linux box the same jobs go to Hammerspoon, Keyboard Maestro, AutoKey, or a shell alias, and none of what follows transfers. Everything here is AutoHotkey v2. The v1 line is no longer maintained, but a decade of forum answers were written in it, and most of them will not run under v2 unchanged. A #Requires AutoHotkey v2.0 line at the top of the file makes that mismatch fail loudly instead of strangely. Ten seconds well spent, every time.