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

Links are structured incorrectly when writing files directly to content directory #1

Open
gmuller opened this issue Feb 16, 2022 · 2 comments

Comments

@gmuller
Copy link

gmuller commented Feb 16, 2022

Instead of writing all of the files to a sub-directory of content/obsidian/ , I'm trying to write all of the files directly to content/ I tried to following command-line:

~/go/bin/omh -O ~/notes -H ~/code/quickstart -p / -i 'public'

While this does write all of the files to the content dir, it creates links with triple slashes, such as:

[Belief in conspiracy theories is like the belief in myth](///belief-in-conspiracy-theories-is-like-the-belief-in-myth/)

I will look at this a little later, but I think I understand where links are built (omh.go convertNote method), but not certain if that is the right place to repair this, or if there is another way to accomplish what I'm looking for.

@pchr8
Copy link

pchr8 commented Jun 8, 2024

Were you able to find a solution, @gmuller ? For me both / and . seem to default to garden

EDIT passing an empty argument seems to work!

@pchr8
Copy link

pchr8 commented Jun 10, 2024

Empty argument introduces double-slash bug in assets linking (//assets/pic.png), I tried to fix that and some other things in my fork that I now use to build my own website — may be useful: https://github.com/pchr8/obsidian-meets-hugo

(This is literally the first thing I've ever done in Go but seems to work mostly)

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

2 participants