-
Notifications
You must be signed in to change notification settings - Fork 15
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
File Names or Titles with spaces break md-roam #30
Comments
Hmm. I don't seem to be able to reproduce the problem. I have not seen any issue or pull request for Org-roam on this, but would you like to try updating Org-roam? Does this example cover your cases you reported? Anything missed? |
I updated org-roam and still see the same behavior. I'm also on MacOS. To clarify, once I changed my filenames to no longer have spaces I was able to build the org-roam.db and use org-roam-insert without issue, maybe that was a separate issue unrelated to the other problem I have where files with spaces in the title don't have any backlinks. Although your example covers my cases and has backlinks so maybe there's something else happening. I'll include two screenshots to show what I mean: My website note has backlinks and works as expected. However the digital garden note below which is linked in website does not display website as a backlink. |
Your UI looks impressive. I’m also very happy to see Md-roam in action in a really beautiful way like you do. Thank you. Now... I’ll take a guess here.... Your expectation is that If so, I am afraid that I might disappoint you. The way wiki link works at the moment is that it uses the filename to link to another note. The syntax is On a separate, but related note, there is a pending pull request on Org-roam that adds a related feature. I wanted to see how this might be incorporated. I’m also looking to improve the wiki link syntax to be a bit more fluid in the note’s body of text like you are doing. This PR might be a very advanced starting point for that effort. |
Thanks for that compliment! I'm using the doom-tomorrow-day with the Adobe Garamond font and mixed-pitch-mode! You're right I was misunderstanding what the Hopefully that pending pull request opens up new possibilities, but for now I'll consider this closed. Thanks! |
@dschapman, in the meantime, I’m considering two additional features, based on this issue and looking at how you currently creates your website:
I cannot really promise that I have enough skill to do both, but I’ll give it a shot. I won’t be able to do much this week or weekend, but looking to do something after that (and hopefully ship something within July...). If I’m successful, then, I think it will let you use [[filename without .md]] to write your note, and then swap it to (title)[./filename.md] for publishing for Gatsby... Or add to the logic of Do you think that will be useful? Any thoughts? |
I think that adding to the md-roam-insert logic and supporting standard markdown links sounds most appealing from a workflow perspective. Obviously no rush to implement but that sounds cool to play around with. |
I was having trouble getting my the org-roam.db file to build correctly in my folder full of only markdown files. I would run org-roam-db-build-cache but whenever I used org-roam-find-file no files would show up. Eventually I tried renaming all my markdown files so that they no longer had spaces in the file, replacing it with
-
. After doing that I was able to run org-roam-db-build-cache correctly; however I noticed that the org-roam backlinks didn't show up for notes that had titles in them.For example: I have a note whose title is
website
. The backlinks show up fine when I have that file open. I also have a note whose title iswebsite redesign
. These notes both link each other but the backlinks only show up in the note with a title and not in the note with a space in the title. This seems to be true across all of my markdown notes. The ones with spaces don't have backlinks, the ones without spaces display their backlinks.The text was updated successfully, but these errors were encountered: