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

Handle relative paths in Markdown export #846

laurent22 opened this Issue Oct 4, 2018 · 4 comments


None yet
3 participants

This comment has been minimized.

GIT-STATA commented Nov 13, 2018

Hi laurent22,

thanks so much for your great work! I really appreciate all of it!

Right now I do not find any way for using a absolute or relative path, that is portable between Mac, Linux or Windows. It would be great to even implement that possibility in Joplin!

It would be great to enhance this feature that way, that you could use a relative path in the first place to write md files in Joplin as well! In editors like ATOM or SUBLIME TEXT you already can use a relative path for pictures or file attachments. That way you could keep your directory infrastructure as well as your 'naming conventions'.

For example, we use

Many thanks again!


This comment has been minimized.

forcewake commented Nov 20, 2018

Yep, @laurent22 thanks a lot!

Regarding the relative paths in the export.
In the current implementation there is only one issue - find the way to determine the level of _resources folder, due to notebooks hierarchy
or change the way how the images (or resources in general) are stored.

Second option can break some compatibility for users which are already rely on specific folder structure.


This comment has been minimized.


laurent22 commented Nov 20, 2018

@GIT-STATA, this is unlikely to be implemented since the recommended way to include a file is to attach it rather than link to a local file (that way it is synced with the notes). If you want to link to a local file you can already do so using the file:/// protocol. You would just need to make sure that all your devices have the same path structure, using symlinks if necessary.

@laurent22 laurent22 closed this in 897f53b Nov 21, 2018


This comment has been minimized.

GIT-STATA commented Nov 21, 2018

Thanks a lot! I really appreciate all of your efforts!

Still if I do use the file:/// protocol I can't use a local path
like that one:

C:\Program Files\YEAR\M.01\DAY.jpg

A fix for #906 was merged!
I guess, that should solve those problems?

Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment