Closed bootsiaz closed 6 years ago
Thanks for the pull. We are looking at a new release coming soon. I have to release the new markdown
, pymdownx
, and this package all at the same time as the head of pymdownx
and this package depend on the latest markdown
version. But it should happen soon.
Great! No problem. I can wait for the new release. Thanks!
FYI, the reason I haven't pulled the trigger on this was I am waiting for Markdown to release the next official tag so I can package the official tag as a dependency. If by the end of the week, it still hasn't been released, I may just package the beta of the soon to be released tag so I can get this out.
Okay, so I can't tell when the next release of Markdown is going to happen. I'm on the team, but I don't control when things get released. I will most likely this week take some time to re-sync and release a beta so I can release this.
FYI, I am going to make a release tonight including this. I got tired of waiting for an official release of a new version of Python Markdown (to use the 3.0 version, we need some unreleased bug fixes). So instead of pushing master, which requires 3.0, I will push an intermediate release based off the last 3.3.3 release with recent code highlight additions.
Sorry it took so long to get this out.
Hi Isaac,
I finally found some time to work some more on my plugin. I have a quick question. How do I escape asterisks * when passing in to the mdpopups syntax highlighter?
I am adding the mdpopups command to all popups in my plugin.
Thanks again.
andrew
On Thu, Nov 29, 2018 at 8:28 PM Isaac Muse notifications@github.com wrote:
FYI, I am going to make a release tonight including this. I got tired of waiting for an official release of a new version of Python Markdown (to use the 3.0 version, we need some unreleased bug fixes). So instead of pushing master, which requires 3.0, I will push an intermediate release based off the last 3.3.3 release with recent code highlight additions.
Sorry it took so long to get this out.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/facelessuser/sublime-markdown-popups/pull/60#issuecomment-443087310, or mute the thread https://github.com/notifications/unsubscribe-auth/AFy5sRFXo60NcLqBQyBDhjcWnU2egEJIks5u0LPigaJpZM4Xbkuv .
Never mind. I set the markdown flag to false and it fixed the issue.
thanks,
andrew
On Fri, Dec 21, 2018 at 10:35 AM Andrew Carter jmandrewcarter@gmail.com wrote:
Hi Isaac,
I finally found some time to work some more on my plugin. I have a quick question. How do I escape asterisks * when passing in to the mdpopups syntax highlighter?
I am adding the mdpopups command to all popups in my plugin.
Thanks again.
andrew
On Thu, Nov 29, 2018 at 8:28 PM Isaac Muse notifications@github.com wrote:
FYI, I am going to make a release tonight including this. I got tired of waiting for an official release of a new version of Python Markdown (to use the 3.0 version, we need some unreleased bug fixes). So instead of pushing master, which requires 3.0, I will push an intermediate release based off the last 3.3.3 release with recent code highlight additions.
Sorry it took so long to get this out.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/facelessuser/sublime-markdown-popups/pull/60#issuecomment-443087310, or mute the thread https://github.com/notifications/unsubscribe-auth/AFy5sRFXo60NcLqBQyBDhjcWnU2egEJIks5u0LPigaJpZM4Xbkuv .
I have started using mdpopups for my HDLProject plugin. Before I push the changes for my plugin, I wanted to make sure these mappings get added.