mdelobelle / obsidian_supercharged_links

obsidian plugin to add attributes and context menu options to internal links

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Out-links break the plugin

EliasSchlie opened this issue · comments

Whenever one of my .md files has an out-link (with the structure: [link](https://www.example.com)) in it, the links are not getting colored in this file anymore.

Is this the same for you? I think this it's a bug.

commented

I can't reproduce this. What Obsidian version are you on? (Settings -> About). If you're on the latest version (1.1.16) and are still experiencing this. Could you provide an example file that breaks?

@OptionalM
I am at the latest version. It is still happening. In the reading view, everything is fine, but in live-preview, it breaks.

Here is an example: Example file.md

commented

Your file works for me. Could you provide your Obsidian version, Installer version, and Plugin version?
You could also try disabling other plugins that might be interfering with Supercharged Links.

Obsidian_sNoWeLK9Rf

@OptionalM

I tried to replicate the issue in another volt with exactly the same .obsidian folder, but the link was working there. I don't know what is the reason for this. It can't be the plugins...
Have you got an idea?

@OptionalM

I really changed everything around in my volt and I think I found the problem. For some reason, I can't have a folder called ( inside my volt

commented

Great! Thanks. I'll look into that.

commented

Are you sure it's ( and not %? Even if it's ( it might be related to #174 (and #163 by extension)
This setup is not enough to break it for me:

├─ (
│  ├─ Example.file.md
│  ├─ Note 1.md

I don't really understand it. By renaming the ( folder, I got the plugin to work in files with outlinks, But in my test volt, it's not breaking when I add a ( folder

@OptionalM

Can you summarise this discussion? Can i close this issue?

commented

Summary up to here: We are unable to reproduce this bug. There is slight hope that this is related to #163 and fixed now.
@Snowfox2002 could you confirm whether or not plugin version 0.9.7 fixes this for you?