I find anchors useful - coming from Logseq as discussed in another thread. Headers don’t work since I’d like to link anywhere in a page, not only headers.
That being said, anchors don’t seem to work consistently if they are embedded in bullets. Not sure what’s the requirement for getting them to work, I’ve not figured it out with my tests. I just get an error: “Could not find anchor $xyz”.
Well, in page anchor doesn’t sound very useful to me. But cross-page anchor really helps when I want to cite things from different pages in fine grain. I would say it is a killer-feature for me that I didn’t know existing before your hunting down series.
But since you are seeking to remove it. I’ll feedback to this page a week later about whether I can use it in real scenarios.
Conceptually the content you want to refer to might not always presented as a header since it might not be a seperated concept worthy a heading when you originally organize the content. E.g. when I collect my reading notes, something might just be presented as a bullet point in one book, but later I find connection between this specific bullet point to another reading concept, this is the scenario I didn’t know how to deal with.
But TBH to make it really useful we might need to improve the doc a bit to make people really aware of the existing of that feature.
I don’t use anchors either, but I do see how it could be useful to link to something on another note that isn’t a header. E.g. maybe I want to link to a specific task on a page somewhere.
The thread @shashlick linked to had me thinking an alternative to anchors could be to allow linking to specific attributes on a page.
e.g.:
This is a page without headers.
- and this is a list
- with stuff
- [ ] and a task in the middle [id:task123]
- [ ] or two [id:task124]
- [ ] and maybe a /createid slashcommand that auto generates a uuid [id:6016DACF-3739-4625-A403-61BBB769FC5C]
And another page would have a link to [[myothernote?id=task123]]. Or maybe even just [[?id=task123]] and then the link will point to whatever note currently has that attribute.
I’m not sure if this would be less code than how anchors currently work, but it would at least be somewhat consistent by re-using existing features instead of a whole new concept.
My isssue is across pages. I created a page with a paragraph, followed by an anchor then another para and then a second anchor. First one works, second doesn’t. I remove the first anchor, second one still doesn’t work. I move it up, it still doesn’t work. It’s just hard to explain, I’m not able to think of a clear way to demonstrate.
Note that linking to anchors works - e.g. I’m typing out [[Page$...]] and it auto-completes. But when you click the link, it fails.
Coming back to this post for the feedback. I’m pretty happy to discover the anchor. It helps me to not only structure my note as tree (via titles). But also allow me to link things that was not structured hierarchically close together.
and only found that I created: