-
Notifications
You must be signed in to change notification settings - Fork 177
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
Links with headers/anchors break #28
Comments
Thanks for the report, that makes sense. We can probably strip out the part after hash in the case of |
To be honest I'm kind of wondering if it could read the file but start at
the anchor in both cases. But it's ultimately up to you, I just noticed it
behaves oddly.
(Also there could be an argument made of having arrows point to another
existing node but probably is complex)
…On Sun, Mar 31, 2019, 9:17 AM Jakub Dundalek, ***@***.***> wrote:
Thanks for the report, that makes sense.
We can probably strip out the part after hash in the case of [a
link](file/somwhere.md#elsewhere). But where would you expect the link to
point out in the case of [a link](#elsewhere)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEgscPoAbRjl5LwypAaNmH34Yr_tZlA_ks5vcLVMgaJpZM4cTKJ9>
.
|
Having anchor to another specific node might be cool. However, probably more effort than I have time to put in. I will see what can be done when I find some time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
home.md
file/somwhere.md
works nicely
but if you try this it doesn't...
home.md
It tries to make a file named
somwhere.md#elsewhere
when clickedSimilarly,
[a link](#elsewhere)
tries to make a file called#elsewhere
.I am using this in the atom extension but I think it probably has to do with this project missing the feature.
The text was updated successfully, but these errors were encountered: