Skip to content
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

Wikilinks support? #87

Open
Hackin7 opened this issue Dec 2, 2022 · 8 comments
Open

Wikilinks support? #87

Hackin7 opened this issue Dec 2, 2022 · 8 comments

Comments

@Hackin7
Copy link

Hackin7 commented Dec 2, 2022

Was wondering if there are any plans for this project to include wiki links support, like Obsidian

Something like this : [[link]]

@Linbreux
Copy link
Owner

Linbreux commented Dec 2, 2022

Hi @Hackin7

The link system we have now works but I find it sometime a little buggy. I think it would be a nice feature to support this!

Maybe we can support both for legacy.

@Jerakin
Copy link
Contributor

Jerakin commented Feb 19, 2024

I made a quick plugin for this https://github.com/Linbreux/wikmd/compare/main...Jerakin:wikmd:plugin/page-link?expand=1

But after making it I am not sure it's worth having. It will easily collide with [[tag]] system and other plugins. It's also not that much harder to write [Features](Features) than it is [[Features]].

What do you think @Linbreux is a plugin for it a good idea?

@lillemets
Copy link

I second the necessity for wikilinks support. I attempted to use an Obsidian vault as Wikmd directory so that I could use both editors. But guess I need to find another app to serve my notes.

@Linbreux
Copy link
Owner

Linbreux commented Aug 9, 2024

@lillemets

Did you try the plugin @Jerakin wrote? https://github.com/Jerakin/wikmd/tree/plugin/page-link/plugins/page-link

You should be able to just copy the folder inside the wiki plugins folder.

@lillemets
Copy link

You should be able to just copy the folder inside the wiki plugins folder.

I'm running Wikmd in a Docker container using the Container Manager app on a Synology device. I have mounted my note directory as a volume and I can preview their contents fine, except for links. But I don't seem to have any easy access to the Docker image or any other files. Perhaps I could also mount the plugin directory as a volume but I don't know what the path is. However, Obsidian also supports markdown links so I should probaby just convert all links my notes.

@Linbreux
Copy link
Owner

I can preview their contents fine, except for links.

Are this wikilinks?

Perhaps I could also mount the plugin directory as a volume but I don't know what the path is

You could create a wikmd-plugins folder on your host system and link the volume to this location in the docker image: /code/wikmd/plugins

I would suggest to also put the existing plugins in your hosts wikmd-plugins folder.

@johann-petrak
Copy link

johann-petrak commented Oct 17, 2024

I guess there are two possible ways to resolve this?

  • change things in a breaking way: so that [[xxxx]] is a wikilink and something else is used for plugins or other functionality , e.g. <> or {{xxxxx}}
  • change things in a backwards-compatible way so that [[xxxxx]] has the same functionality as before and another wikmd-specific shortcut is used for wikilinks, e.g. [xxxxx](#) (since # by itself would not make much sense or be almost never used as a link)

But having something to avoid [some stuff](some stuff) which is probably the most often used way to link between wiki pages would be quite useful and avoid typos or copy/paste mistakes.

Yet another (optional) feature could be to automatically recognize CamelCase or Snake_Case placed inside square brackets as wiki links and potentially show them formatted as "Camel Case" or "Snake Case" where snake case would have the advantage that both upper and lower case can be used. This must be optional though as it cannot be used in wikis where CamelCase or Snake_case is used as part of the text, e.g. programming related.

@pomalley
Copy link

pomalley commented Dec 6, 2024

I didn't notice this discussion and hacked together a semi-parser for this so that it wouldn't process [links] inside verbatim blocks: cfceda5

Also, I used single brackets (personal preference), so it just replaces [link] with [link](link) if there's no ( after the closing ].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants