Please feel free to use that repo.
I've added the first page to the Wiki.
Seems like the Wiki would be a great place for documentation.
I'm not sure what I have to do to allow you to edit it -- there is a thing where I can add "collaborators", but I need your email address to do that.
I'll have to take a look at that hotfix code.
Does that work OK when developing the macros, or is it just a good way to distribute them?
I've come up with something that works for me.
See the my post, reply #4 of:
https://community.slickedit.com/index.php/topic,17302.msg67232.html#msg67232for how I do it.
Basically, I have customized a number of Slick standard macro files and have a separate set of new macro files.
I put them all in %USERPROFILE%\Documents\Slickedit\24.0.1\..\Macros
To keep from cluttering the "Config" directory.
If that hotfix packaging works well we should be able to create a build process to create the Hotfix.zip files for people to download.
For versioning: Not sure what to do here, I just maintain a single current version and haven't worried about backwards compatibility. We should be able to do that either by embedded #ifdefs, or keeping separate folders/branches for each Slick version. Presumably, most new development would be only for the current version of Slick.