Page 1 of 1
Hotstring stopped working on 1.1.36.01
Posted: 07 Dec 2022, 04:25
by JanSal
Hi there,
The following hotstrings have worked well for me with past versions of Autohotkey up to the recent update 1.1.36.01:
Code: Select all
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
:?C*:!!::¡
:?C*:??::¿
They now return ¿ and ¡ respectively
-- how to debug such an issue? Thank you for any suggestions.
Re: Hotstring stopped working on 1.1.36.01
Posted: 07 Dec 2022, 04:36
by mikeyww
Are you showing your entire script?
What is the last modification date of your AHK script?
Re: Hotstring stopped working on 1.1.36.01
Posted: 07 Dec 2022, 04:59
by JanSal
Hi
@mikeyww
Thank you for your reply! I isolated the hotstrings and put them into a new script, which shows the same erratic behaviour.
Interesting however is that, if I run the script from a small IDE, called
CodeQuickTester, the hotstrings run without issues, despite the utility using the same AHK instance as the other script.
Re: Hotstring stopped working on 1.1.36.01 Topic is solved
Posted: 07 Dec 2022, 05:13
by JanSal
Just figured it out, for some reason VSCodium started to save files in UFT8 instead of UFT8-BOM, switching to UFT8-BOM encoding everything runs smoothly now.
Re: Hotstring stopped working on 1.1.36.01
Posted: 07 Dec 2022, 05:26
by mikeyww
Mine worked without UTF-8. I'm not sure why there is a difference, probably just something at my end. Glad you have it working.
UTF stands for Unicode Transformation Format.