Feature: Interpret absolute image links relative to g:mkdp_images_path
#651
Comments
PaulBreugnot
pushed a commit
to PaulBreugnot/markdown-preview.nvim
that referenced
this issue
May 15, 2024
As suggested in iamcco#651, `g:mkdp_images_path_as_root` can now be set to 1 to resolve absolute image paths against `g:mkdp_images_path`. Example: ```  ``` with `let g:mkdp_images_path = /home/user/.markdown_images`. If `g:mkdp_images_path_as_root = 0` (default), then the image path is interpreted as an absolute linux path, starting at the root of the system. If `g:mkdp_images_path_as_root = 1`, the path is interpreted as `/home/user/.markdown_images/path/to/image.png`. This is notably useful to reproduce the behavior of markdown hosting websites, such as Github wikis, where absolute image paths are resolved against https://github.com/username/repository/wiki/.
PaulBreugnot
pushed a commit
to PaulBreugnot/markdown-preview.nvim
that referenced
this issue
May 15, 2024
As suggested in iamcco#651, `g:mkdp_images_path_as_root` can now be set to 1 to resolve absolute image paths against `g:mkdp_images_path`. Example: ```  ``` with `let g:mkdp_images_path = /home/user/.markdown_images`. If `g:mkdp_images_path_as_root = 0` (default), then the image path is interpreted as an absolute linux path, starting at the root of the system. If `g:mkdp_images_path_as_root = 1`, the path is interpreted as `/home/user/.markdown_images/path/to/image.png`. This is notably useful to reproduce the behavior of markdown hosting websites, such as Github wikis, where absolute image paths are resolved against https://github.com/username/repository/wiki/.
|
I'm new mkdp user, could anyone please help me understand on how to use images in the markdown preview. Do I need to update something in my vim configs? |
|
Not for the preview to work, as long as you have the correct syntax and path the image it should display.
|
|
thank you @Tweekism and also I was having issue loading the images. I noticed that the image name contained spaces and so I remove the spaces and it worked. |
|
Oh ok, well I haven't tested this, but if your images have spaces in them, replacing spaces in your link it |
|
thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some common workflows interpret absolute links relative to a well-known directory rather than the actual root of the filesystem, akin to how a web server interpret absolute links relative to the domain. I don't think there is currently a way for this plugin to behave like that regarding images.
I would suggest an additional boolean option for interpreting absolute image links relative to the existing
g:mkdp_images_path(if provided). For instance, ifg:mkdp_images_pathis set to/foo/bar, then an image likewould resolve to/foo/bar/baz.png.This should be an easy add-on and would turn this plugin from "great" to "excellent" :)
The text was updated successfully, but these errors were encountered: