-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'd love to see the source for this! #1
Comments
Thanks, I'm glad you like it! All source is on GitHub in this project. The master branch contains the unsigned script module, and if I ever have changes checked in but not released yet, they will be there. The release branch contains the latest signed release, and the assembly contains the Visual Studio solution for the binary module. I follow this model for all my modules on GitHub. Have a look at the assembly source and let me know what you think! |
Note, that should say the assembly branch, not just the assembly. Sorry if this caused any confusion. |
Ah, I didn't think to look in a different branch. Thank you! (that's a neat trick for keeping both source and binary releases as part of the same repo--thank you for that, too!) |
You're welcome! |
FormatPx is awesome. I have some experience monkey-patching the formatting commands, and I would love to see your approach. Are you sharing the source anywhere?
Thanks!
The text was updated successfully, but these errors were encountered: