-
-
Notifications
You must be signed in to change notification settings - Fork 400
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
link to .md in another folder #888
Comments
Thank you for your suggestion, currently it's only possible to link to a note in the same sub-folder. |
What would be required to make this work? |
Hm, I guess quite some things. Changing how linking to notes works in general. This might also break existing links. Also of course the Link dialog has to be adapted. |
mmmh... and will also interact with #266. I suppose the most resilient way to add this would be to make all paths relative to the root notes folder, similar to e.g. vim's find files works. That should then also work when using e.g. pandoc, as long as that is started from the notes root. Is there a road map or some other kind of mid-term planning for this project so I can get an idea of how planned features will interact? |
not really, there are too many things that come up constantly (by user request most of the time)
sure, but this smells like major regressions (that every pull request I got so far had) :) I wonder how you will deal with that ;) |
Could you please head over to #266 to test and comment on the new features. |
Expected behaviour
From my main.md I want to link a note in another (sub/parent) folder.
In the example I want to link from main.md to inner.md and outer.md.
Content of main.md:
I try / and \ in file path, because it differs from windows to linux, ....
I am using this notation and not the one with note://, because of compatibility with another application, but I tried both.
Actual behaviour
The link to another.md is working without any problem.
But when I click on the link to inner.md or outer.md I get the message
Output from the debug log file
The text was updated successfully, but these errors were encountered: