You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm already using your plug-in because this allows me to see an image in the markdown. With most markdown, you can read and write the markdown and understand it, but with an image, you can't read it (see it) and you can't type it in. You have to paste it in, and without a preview of some sort, you are blind unless you switch to the rendered view.
The enhancement I would like is to be able to adjust the scale of the image: 25%, 50%, 75%, 100%, 150%, 200%. In my case, because the image is a screenshot from a HiDPI display, I want to scale it to 50% in order to get the same size and pixel density as it was on my screen.
For scales other than 100%, it is fine that the markdown changes to an <img> tag.
Is that an enhancement that fits with the philosophy of this plug-in?
The text was updated successfully, but these errors were encountered:
Unfortunately, I don't see myself implementing this feature in the near future. I will accept a pull request, and can provide some help to anyone seeking to implement it.
Please see this forum question for the background to this feature request.
I'm already using your plug-in because this allows me to see an image in the markdown. With most markdown, you can read and write the markdown and understand it, but with an image, you can't read it (see it) and you can't type it in. You have to paste it in, and without a preview of some sort, you are blind unless you switch to the rendered view.
The enhancement I would like is to be able to adjust the scale of the image: 25%, 50%, 75%, 100%, 150%, 200%. In my case, because the image is a screenshot from a HiDPI display, I want to scale it to 50% in order to get the same size and pixel density as it was on my screen.
For scales other than 100%, it is fine that the markdown changes to an
<img>
tag.Is that an enhancement that fits with the philosophy of this plug-in?
The text was updated successfully, but these errors were encountered: