Keysharp - C# port of AHK

[mfeemster]

@burque505 I've ported the old AutoCorrect.ahk script to Keysharp.

Changes:
-Port code to from v1 style syntax to v2/Keysharp style.
-Add more words ending in ign to exclude from autocorrecting.
-Add more corrections at the end.

Diff with the original to make sure you're adding/removing the ones you want.

[eugenesv]

This will not support the Unicode example you posted above because Keysharp translates script code into C#. So variable names in Keysharp need to be valid for C#. That's the best we can do.

Wouldn't the best thing we could do be some kind of name mangling instead during the translation? For example, Unicode symbols could be translated into their names and then you could add some long ASCII prefix to such variables that no user would ever use in a variable name to avoid confusing arrow symbol translated into "arrow" with use defined "arrow" in a name?

So then you could freely use Unicode in names and only be limited by said prefix and maybe some other edge cases you're unlikely to encounter (but be warned if translation isn't unique).

[mfeemster]

Porting to linux is my main priority now, so something like that is on a very distant back burner. Until then, only valid C# variable names are supported.

[SOTE]

Porting to linux is my main priority now...

Very good news!

[mfeemster]

We don't have a new release ready yet, but I just wanted to let everyone know I've been working on this almost non stop this year except for a few months hiatus in the spring. User @Descolada has been doing extensive testing and finding all sorts of bugs that I've been fixing. We are substantially closing the gap between lingering differences between AHKv2 and Keysharp behavior (with some listed caveats).

I also spent a lot of time over the summer getting things ready for linux. I've got most functionality running there except for anything relating to the keyboard/mouse, hotkeys/hotstrings and manipulating non-Winforms GUI controls in other programs. Those will be *extremely* difficult to implement. I will be consulting the code for AHK_X11 to see how they proceeded.

We are going to wrap up the last few bug fixes over the coming weeks and should hopefully have a release ready around the new year.

Thanks for your patience.

[Chunjee]

I also spent a lot of time over the summer getting things ready for linux.

[x32]

I've been checking on this development from time to time and am excited to see it progress. With the roll out and substantial downgrade of Windows 11 I'm fairly sure that a switch to Linux is inevitable. Not that I know much about Linux but have used it a bit in the past, including testing ports of AHK. Most likely Iron AHK but I don't remember as I also tested AHK with Wine with limited functionality.

Edit: It was AutoHotkeyCE that I used on the Pocket PC.
Again I don't remember for sure, but I think it was Iron AHK I used fairly extensively on a Pocket PC running Windows Mobile 2003 SE. I used this device regularly as an audio tech while mixing concerts and theater. One of my most used AHK programs was triggering sound fx and simply playing music. Before cell phones were around there were not many small music players, and sound fx triggers were large stand alone devices that were limited to a few sound, and were expensive. With a Pocket PC I had a small device that had quite a few live audio tools in a small package, and could keep as much music and FXs as I needed on SD cards.

I'm going to load up a new Linux computer and start learning it again, and maybe be ready by the time you release the Linux version. Is there a particular flavor of Linux that you're going to start porting to? If there is I'll start learning that one.

Thanks for all your hard work.