5 ms·
I love AutoHotkey, and it works wonderfully in the niche of writing a bunch of tiny UI- and workflow-smoothing functions, like how an Emacs user gradually build
by skymt 6y ago
I love AutoHotkey, and it works wonderfully in the niche of writing a bunch of tiny UI- and workflow-smoothing functions, like how an Emacs user gradually builds up tweaks in their config file. The one time I tried to use it for scripting that required more than the most basic logic, I ran screaming back to Python. Over a decade of well-meaning development and reasonable design choices have resulted in AHK growing a syntax Frankensteined together from Basic, JavaScript, and batch script. Thankfully the upcoming AHK 2 is cleaning up a lot of the mess.
https://www.autohotkey.com/v2/v2-changes.htm https://www.autohotkey.com/v2/v2-changes.htm
- frosted-flakes 6y agoAKH v2 has been "upcoming" for close to a decade now. AutoHotkey started out as a fork of AutoIt by Chris Mallett, who stopped development around 2010 or so. Then Steve Gray (Lexikos) continued development under a fork called AHK_L, which later became AHK v1.1, and he's been the sole maintainer ever since. The GitHub repository is still fairly active, and I believe the v2 alpha is fairly stable, so I'm curious as to what changes still need to be made before it's done.
- badsectoracula 6y agoSounds like AHKv2 is doing the grave mistake of "cleaning up" by breaking all the scripts and work that people have put towards using the tool.
- airstrike 6y agoSeems to me like we need a 1to2.ahk file