[[link]]::tag::
Is this a new type of tag? If it gets pulled into org-roam’s core, could we give it a different name? Things are getting confusing (see How to use ROAM_TAGS and/or tags?).
Yes, the proposed feature is a “link-tag” that annotates specific links with any kind of formal contextual information that a person might want to add. See my post here if you want a lengthy breakdown of their purpose Add Link-tags feature . Basically instead of adding a tag that applies to the entire note, you can just tag a specific link.
I’ve been using the term link-tag just to be semantically plain, but I have no preference. “Relations” was a suggested alternative that is truer to what they actually are. I just haven’t adopted ‘relations’ since it is a vague term if you are not clear on the feature context.
@zaeph, thanks for the explanation. Is there a new binding or something for standard org-mode internal links? I’m asking because the most common link I create is an internal link pointing to a dedicated target.
Internal links can be achieved by using the [[*…]] format, which will create an ID for the targeted headline in the current-file.
@zaeph, what’s the method for linking – not to a headline – but to a dedicated target? My existing org files have hundreds of those. Are links to dedicated targets possible in org-roam?
We haven’t looked at radio targets yet. We’d need to come up with a solution to include them in our UX model. Could you file an issue on the tracker for it?
@zaeph, just to be clear, I’m not talking about radio targets but about dedicated targets, the ones that are surrounded by <<>>
I love this feature, but the incremental search feels clunky and old fashioned. Why don’t we use FZF and ripgrep to find any fuzzy matching line within our files?
Let’s say I’m looking for a recipe that I want to link to. I just type [[…]] and continue to write “recipe classic lasagna” and I get a list of suggestions that fit the criteria. The results show a ranking of the closest matching title, header and/or line which I can choose from to make a link. If there are no matches I may create a new link with the same query. No need to think of search entry points, search order, or capitalization, just type what’s on your mind.
Here is a illustrative example of what I’m thinking of (the example uses vim, but bear with me):
You can have a very similar interface as in the GIF, for example with Ivy by tweaking counsel-rg (or counsel-ag) and changing the :action clause of ivy-read to calling org-roam-capture on the file: https://github.com/abo-abo/swiper/blob/9bb68419f1088ee4d8f2b76f84995fa02bceeed3/counsel.el#L3026
Bear in mind that linking notes together is intentionally a conscious effort in the Zettelkasten method. Reducing friction is not the goal here.
1 Like
It seems that overriding Org’s default fuzzy-link behaviour has brought some surprise to active users of fuzzy links. In addition, it seems that even the [[*Headline]] style links are actual functional internal links (as seen in the Org 9.4 changelog example at https://orgmode.org/Changes.html).
Because of this, I’ve been thinking about moving to a different bracket syntax (like {{Title*Headline}}). Any strong objections here?
EDIT: or actually going back to @alan’s original proposal of [[roam:…]]
3 Likes
I think [[roam:…]] links using org’s link infrastructure would be preferable to a completely new link syntax
1 Like
2 Likes
This looks amazing! Has any of this been implemented/do you have a patch you can share? I’d love to try it out.
Is this an existing feature of roam and ready for immediate consumption (and how?) or is this a future feature?