[v2-beta-1] Hotstring * option override Topic is solved

[joedf]

Hi there, I received this email from a fellow user and I am forwarding it in here. I will act as a "relay" by email.

Hello,

I'm blind and not able to use the forum, sorry for that.

I have a bug in AutoHotkey V2, Beta 1.

If I deactivate a hotstring with the * option, disable it and enable a
hotstring with the same content but with other options, the * option is
enabled again.

Example:

My Code:

Hotstring(':*:tst', 'hallo')
Hotstring(':*:tst',, false)
Hotstring('::tst', 'hallo', true)
The result should be, that I have to enter tst and an ending char to
execute the replacement. But the ending char isn't necessary.

Could you please fix this?

Thanks for this great scripting language!

MfG Adrian Kurz

[swagfag]

was that ever an advertised feature for it to now be considered a bug? im saying this because it doesnt work that way in v1 either(and i cant recall it ever having)

If the hotstring already exists, any options specified in String are put into effect, while all other options are left as is.

yes, the irony that is my use of primarily visual aids to explain something to a blind man is not lost on me. sorry, guy
according to that the * was never disabled to begin with. u arent specifying any new options, and any old ones "are left as is"
if u wanted to disable it, do what other parts of the docs suggest:

* (asterisk): An ending character (e.g. Space, ., or Enter) is not required to trigger the hotstring. For example:

Code: Select all

:*:j@::[email protected]

The example above would send its replacement the moment you type the @ character. When using the #Hotstring directive, use *0 to turn this option back off.

[joedf]

I see what you mean. I havent used Hotstring() much. So the solution is to instead use

Code: Select all

Hotstring(':*0:tst', 'hallo', true)

Thanks!