Have separate "Use Markdown links" options for wikilinks and image links

Feature requests
1

Have you searched for an existing request?

Yes. See “related feature requests”.

Use case or problem

I want to export my notes to my site, which accepts [[wikilinks]] but not ![[image_links]].

Indeed, if [[wikilinks]] are becoming more and more integrated in websites, it’s not the case for ![[image_links]].

Therefore, users may have a framework that accepts [[wikilinks]] but not [[image_links]].

Proposed solution

Unbundle the “Use Markdown links” option in the “Editor” menu.

I’d like to have separate options for wikilinks and image links.

[ ] Use Markdown links for wiki-style links : [[…]]
[ ] Use Markdown links for internal image links : ![[…]]

Current workaround (optional)

In my case, that forces me to modify image links (markdown) by hand, which is be quite cumbersome.

Related feature requests (optional)

There is :
https://forum.obsidian.md/t/autocomplete-for-links-images-using-standard-markdown-notation/ → Autocomplete images and wikilinks links as markdown links. A comment explains partially what I need, by the way.

→ Convert internal links to wikilinks

Use standard MD links for images - #4 by WhiteNoise → This is close, but does not mention the decoupling between wikilinks and image_links.

@matti told me that he asked for the same thing. Great, we can be friends now ! :smile:

21 Likes
2

My own Request is related to this :Setting link and image link styles independently

4 Likes
3

Thanks, I’ll update my request !

2 Likes
4

Have you searched for an existing request?

Yes.

Use case or problem

  • DevonThink supports only standard image links, e.g. ![](foo.jpg)
  • DevonThink supports clickable WikiStyle links, e. g. [[bar]]

… but I can only set every kind of link (image and non-image) to standard or everything to obsidian. I can not set them independently.

Proposed solution

There should be two settings: One for “normal”/internal links and one for image links.

Current workaround (optional)

Use standard. But then links are only clickable (in DevonThink as in Obsidian) in the (Pre)View-Mode of the file.

4 Likes
5

I use GitJournal. It supports wiki links, but it only supports the markdown style of image links. Please separate the link format switch from the image link format.

3 Likes
6

Oh I would like to bump this. The ability to retain Wikiliks for markdown files, but using Markdown links for images (especially when pasting, and putting in those %20 in spaces), would make the notes more compatible with other markdown editors as well.

5 Likes
7

I just discovered that the default internal links for pasted images e.g.

![[Pasted image 20201106170215.png]]

will not display in basically any external markdown editor. What is the advantage of using these style of links vs “standard” markdown format of:

![](attach/Pasted%20image%2020201106170215.png)

Anyone got a good solution for converting existing internal links to standardized format (for images only…) ?

1 Like
8

A similar problem - I use GitJournal and have to manually fix markdown links to notes in wiki links. Besides GitJournal, most editors on iOS/Android do not support the wiki style of image links and support the wiki style for links to notes. Easy-to-fix stuff that significantly expands the ability to use the knowledge base on mobile devices.

2 Likes
9

A temporary solution to the problem is to use the Wikilinks to MDLinks plugin (available in community plugins). You can use it to switch between wiki and markdown links to notes or images using a keyboard shortcut.
However, I still hope that the developers will separate the option for images and links to notes in the program without using third-party plugins.

5 Likes
10

Yes, much need this!

Using ![](image.png) and ![](<image name with space.png>) for normal image and other files, and using ![[Note Ref]] for internal note links.

Waiting for that!

1 Like
11

+1 please

1 Like
12

I would also like to have separate options for internal vs. external links. For internal links, Wikilinks are less verbose and nicer. For external links, Markdown links are not only more interoperable with other apps but they’re also easier to read (the text should come first, not the less important URL).

13

Great suggestion for interoperability. Hope to see this added soon.

14

Use case or problem

Obsidian ![[image-embed.png]] syntax is not consistent with markdown standards, and I like interoperability wherever I can get it. This makes it difficult to use other markdown hypertext notebook tools like LogSeq on the same directory. In the editor settings, I can replace wikilinks with markdown syntax for linking to files. However, I want to keep wikilinking to pages, and change image embeds to a more traditional ![image-embed.png](../assets/image-embed.png). I can only change them both at once.

Proposed solution

Create separate settings for toggling wikilinks/markdown links for pages and images.

1 Like
15

Please

16

Let’s not forget that it would be useful to have separate options for internal markdown links and external web links. internal markdown links should be using [[wikilinks]] syntax while external links should be using [markdown](http://syntax)

17

Bump. I’m in the exact same boat as OP; I need Wikilinks for md but markdown for imgs for my site to work.

1 Like
18

I am bumping because I just tried to import my vault to dendron and all my images broke. I was under the impression that my data was portable

19

This is pretty darn important to me. I’m writing my thesis in Obsidian, using pandoc to convert the Markdown to PDF (even managing to skip LaTeX, which is great!) - but all my images break and I’m having to manually fix the links…

In fact, I think it’d be great to have new settings in Options → Files & Links:

  • a boolean Use [[Wikilinks]] for images, corresponding to Use [[Wikilinks]]
  • New image link format, corresponding to New link format, with the same “Relative path to file”, “Absolute path in vault” and “Shortest path when possible” options.

That way, I could have all my image links be relative, standard markdown links, and working with Pandoc would be much easier.

20

A vault-wide search and replace with regular expressions (use it in Notepad++, Sublime Text or any other capable text editor) could do this:

Search: !(\[\[)(.*?)([.])(png|jpg|jpeg|bmp|gif|tiff|anyotherimagetype)(\]\])
Replace: ![](<attach/$2$3$4>)

The anyotherimagetype if unchanged, can be left there – it doesn’t make any difference.
Obviously any major overhaul like this must be advanced with caution but this regex is stringent and safe enough to use and should work, provided that the attachment folder is called attach and all images files are in that folder.

1 Like