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

Backlinks do not show with relative paths #209

Closed
mjshashank opened this issue Dec 3, 2020 · 5 comments
Closed

Backlinks do not show with relative paths #209

mjshashank opened this issue Dec 3, 2020 · 5 comments

Comments

@mjshashank
Copy link

When I have files with conflicting names (in my case, one inside a subdirectory and one at the root level), the backlinks panel does not show up the linked note.

Is this a know issue?

@mjshashank
Copy link
Author

For more context:

This is my structure:

--sample/
--sample-1.md
--sample-2.md
--test.md
--test.md

There is wiki link in sample-1.md like [[sample/test.md]] and a wiki link in sample-2.md like [[test.md]].

For the backlinks panel of sample/test.md

  1. It shows sample-2.md which is an incorrect backlink
  2. It doesn't show sample-1.md which is a missing backlink

For the backlinks panel of test.md

  1. It shows only sample-2.md which is the right backlink

Attaching screenshots below:

Screenshot 2020-12-03 at 2 39 54 PM
Screenshot 2020-12-03 at 2 40 20 PM
Screenshot 2020-12-03 at 2 40 15 PM
Screenshot 2020-12-03 at 2 40 24 PM

svsool added a commit that referenced this issue Dec 6, 2020
@svsool
Copy link
Owner

svsool commented Dec 6, 2020

Thanks for reporting. It was fixed and will be released in the next version.

@svsool svsool closed this as completed Dec 6, 2020
@Hocnonsense
Copy link

I also meet this question. I think it is necessary to treat absolute path and relative path in different manner.

@svsool
Copy link
Owner

svsool commented Jan 2, 2021

Links format is configurable via settings, @Hocnonsense.

image

@Hocnonsense
Copy link

Thanks for your advice. And this may be a feature request. Should I open a new issue?

What I mean is that it should recognize / ./ and ../.

For example, when I'm reading journals, my note look like this:

/+ root
 |
 +--/+ doi1
 |   |
 |   +--+ Introduction.md
 |   |
 |   +--+ Methods.md
 |   |
 |   +--+ Results.md
 |   |
 |   +--+ README.md
 |
 +--/+ doi2
 |   |
 |   +--+ Introduction.md
 |   |
 |   +--+ Methods.md
 |   |
 |   +--+ Results.md
 |   |
 |   +--+ README.md
 |
 +-- README.md

So when i wrote [[README]] in /doi1/Introduction.md, I hope it could refer to /doi1/README.md, or allow me to write [[./README]]. (Now I have to write [[doi1/README]], however it don't suit vscode manner because there don't exist a /doi1/doi1/README.md)

It is necessary when you maintain a large library containing knowledge from several domain, when several abbreviations are the same, and when you want to reconstruct or split the large library.

After all, I'me grateful for your excellent vscode-memo. It helped me a lot!!

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

3 participants