search

ahkscript / SublimeAutoHotkey

AutoHotkey AHK language package for SublimeText including syntax highlighting, comments toggling, auto-completions, build system definitions, commands for ahkrun, ahkcompile, ahkrunpiped.
The Unlicense
207 stars 43 forks source link

[Feature Request] Run multiple different AHK versions. #48

Closed lvalkov closed 5 years ago

lvalkov commented 6 years ago

I've only amended ahkrunpiped() because it's what I primarily use, but you get the gist of it. Allow the user to run/runpiped/compile a script based upon the filepath to the interpreter/compiler fed as an argument to each respective function.

Sample keybinds: { "keys": ["f5"], "command": "ahkrunpiped" }, { "keys": ["f6"], "command": "ahkrunpiped", "args": { "pathToAhkExe" : "AHK_L_v2" } }, { "keys": ["f7"], "command": "ahkrunpiped", "args": { "pathToAhkExe" : "AHK_H_v2" } },

robertcollier4 commented 6 years ago

I like everything but im hesitant about -

  1. "Switched from .tmLanguage to .sublime-syntax" - This package is used by other editors which still use the tmLanguage format. We don't want to break off from them. There seems to be no benefit to the yaml format except for easier readability/editability - and this file is very rarely read or edited. Seems to give no benefit to me for us to switch the syntax to the new format, and only disadvantage in losing some of our user base.

  2. "Deprecate obsolete commands" - This package is used by AutoHotkey classic users still as well. I still prefer AutoHotkey Classic many times due to its superiority in speed. We should keep the old commands. And add additional new ones for AutoHotkey_L as well.

robertcollier4 commented 5 years ago

Closing this as staying with the .tmLang format keeps interoperability with other editors.