AutoHotkey Community

Hi,

maybe there's another bug, or I misunderstand something:

:B0:Ha::te the
If I type
Ha{Space}rain
I'll get
Ha te the rain
shouldn't it be
Hate the rain

:OB0:Ha::te the
If I type
Ha{Space}rain
I'll get
Ha te therain
schouldn't it be
Hate therain

Well, I know I could use this
::Ha::Hate the

Using the example from the help ...
:OB0:btw::
MsgBox You typed "btw".
return

is the same like ...
:B0:btw::
MsgBox You typed "btw".
return

Shouldn't the firt one omit the ending character?

Tekl

_________________
Tekl

Turning off automatic backspacing via B0 for an auto-replace hotstring was not anticipated as part of the design. It never occurred to me that anyone would do it.

However, I see now that it might have its uses, such as avoiding unnecessary backspaces when the text you type will serve as the leading part of the word or phrase you're trying to construct.

As it stands now, B0 prevents the option "O" (omit end-char) from working. Given the rarity of using "O" with "B0", perhaps this should be documented rather than changing the program (which would risk breaking existing scripts).

On the other hand, please let me know if you can think of practical uses for O+B0. Also let me know if any of the examples you posted are still unexplained.

Thanks for reporting this. At the very least, it warrants a change to the documentation.

Hi,

I agree, don't change the O-Option.

The new Option "O+" or maybe "B2" would be the best solution.

_________________
Tekl

I thought about more and due to the extreme rarity of using B0+O, I think it's better to fix the "O" option to work even when B0 is in effect. Very few scripts (if any) should be broken by this, so the benefit seems to outweigh the cost.

Even if some scripts are broken, the nature of hotstrings makes it unlikely they will be broken in a bad way: users will notice it next time they type the hotstring and then fix the script.

Hi Chris,

that's good, so I'm the only one who don't have to change his script

_________________
Tekl