Testing Gist in WordPress
WordPress Gist Support
First up is the top level Gist, not an individual file from the Gist. I had to remove my Github name from the URL to make this work. Annoying but hopefully I can remember to remove it.
|// I edited this gist after putting it on WordPress.|
So that works! Great! I like that because when I share source in WordPress and go back to edit the post, it changes the angle brackets to their code “>” versions! I find that feature very frustrating, especially since I do tend to go back and make minor edits to posts.
One drawback in my testing though. I am not able to share an individual file from within that gist. Another note is that I was in HTML view using WordPress’ editor when I added the URL for my Gist, in the Visual view I do not see anything in that area.
Tonight I will try to edit this post using Open Live Writer to add another Gist and see how that works.
Now to see if Open Live Writer will work.
|public interface ILogging : IDisposable|
|/// This method is really for testing purposes.|
|void LogError(Exception e);|
|void LogError(string message);|
|void LogInformation(string message);|
Sadly that did not work, and it broke both gists in the post. I am simply editing it now in the WordPress editor.
Gists are a great way to go. They do not get lost when you update/edit the post in WordPress. If you need to edit the code you shared you can edit the Gist and it will be changed when someone view’s the post without having to edit the post.
The only gotcha is that you have to use the WordPress editor. While this really isn’t a big deal, just an extra step. If you use a different editor just post it as a draft to you blog, then use the WordPress editor to make sure the Gist links are not links and publish.