I'm working on an editor plugin for developing AutoHotkey scripts (similar to SciTe for AutoHotkey).
Currently if we want to pipe warnings to stdout to show them in an error console in the editor, we have to manually specify this at the top of the file (applies to both v1 & v2):
In a professional editor, viewing the warnings as message boxes is very annoying and requires hitting Enter
x times to get rid of them for each script run. Since printing warnings to console is the natural way to go, the only solution we have currently to guarantee that warnings are printed to console (while the user is using my editor plugin) is to manually modify the user's script at runtime and insert #Warn All, StdOut
at the top of their file. This adds design complexity and seems unnecessary since a similar issue has already been resolved with the introduction of /ErrorStdOut
for regular script errors.
Thus, can we add a command line switch option for warnings so that those can be automatically piped to stdout too, just as we can with /ErrorStdOut
? (If not for v1, then at least for v2?)
(Ideally, if we could specify whether we wanted to pipe warnings to stdout or stderr, that would be even better since most editors will give stderr special highlighting. Eg: something like /Warn=All,StdErr
Currently running AutoHotkey v1.1.33.07 on a Windows 10 machine. (Also testing v2 with v2.0-a133)
All code I post on the AutoHotkey forum is under the MIT License
unless otherwise noted in the post. (Basically, it's free for anyone to use/modify, but please credit me if you decide to use it as part of another post or project that will be public.)
"The tomorrow of yesterday is today, so don't make an excuse to delay!"