-
Notifications
You must be signed in to change notification settings - Fork 141
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
Refresh doesn't work #142
Comments
I have the same issue in Notepad++ 8.1.1 64bit with MarkdownViewer++ 0.8.2. A workaround for now is to double-click the MarkdownViewer button in the toolbar (to hide and show the preview panel). It would be nice to have an auto-preview feature, maybe once every second or when you save the file. |
another workaround: press Ctrl+Shift+M twice |
Workarounds are exactly that: workarounds, not solutions. The workaround works, though. Notepad++ 8.1.5 x64 |
hey guys... Anyone found the solution?? |
I have the same issue. The workaround works, but it's a shame about this issue. It's still the best markdown editor in NP++ |
I just installed this plugin and noticed this issue. Has this issue been resolved? |
Still happening Jan 27, 2023. This is a great tool but this is a pretty serious defect in basic functionality. |
Still happening Mar 01, 2023. This is a great tool but this is a pretty serious defect in basic functionality. |
Same here. Would love to see this fixed. |
Bump |
Same problem here :( |
Same problem. |
SAME |
Same here |
I am having this issue as well. My workaround is to close the plugin panel and re-open it.
It seems the plugin "Markdown Panel" serves a similar function and refreshes automatically. |
I believe this is the ongoing issue of issue #107 |
Same issue. |
Still an issue.. |
Same Issue
|
Noticed: |
Issue description
I continue editing the file in notepad++ and added several lines to README.md file, but the viewer is not refreshing at all. I pressed
Markdown to reproduce
(I can't you post my markdown since it is a commercial product)
Screenshot
Environment
The text was updated successfully, but these errors were encountered: