-
Notifications
You must be signed in to change notification settings - Fork 650
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
Add support for block-level linking #294
Comments
Hey @robgrace! Foam Sneak Peek: Block Referencing and Block Embedding It's one of the features we want in Foam |
I really like the |
Really need this feature. |
Hey, @ingalless. Definitely looks great! Is there any news, progress? Long time, no see. |
I'm looking forward to this feature, because I really need to re-arrange my blocks of notes in another way. Hope to hear of any progress. |
It has been more than 1 year since the sneak peek video was uploaded and there is no block referencing (?). Any workaround? |
+1. Dendron also uses the |
I would still really like to see this |
Yes I agree, and the support for sections (#856) implicitly added support for blocks in the model (as a block can modeled as a "type" of section), now it would be a matter of changing the markdown parser to recognize the anchors. |
Any news about this? I came from Obsidian and this feature is a really useful. |
As an alternative perspective, I thought I’d share a way you can achieve
similar functionality in a foam-esque way.
Another option along side using sections is to create your blocks as
separate notes. Then, embed these “block notes using the embed syntax
`![[Note Name]]`.
This way you gain the ability to link to blocks, also your blocks will show
up in the graph and thus be more discoverable.
Just one more option. I know this wouldn’t work for everyone but I wanted
to share it.
…On Mon, Oct 3, 2022 at 7:08 PM Paul Portillo ***@***.***> wrote:
Any news about this? I came from Obsidian and this feature is a really
useful.
—
Reply to this email directly, view it on GitHub
<#294 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSIXNMPKUSJV7DN34NDE7DWBNYQ7ANCNFSM4S3SW33Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I am wondering what's missing here. It looks like the requested feature is working. Although a minor issue needs to be fixed in the preview editor. Or do we want to be able to work more granular then sections? |
The request here is to allow the linking at the block level, not only at the section level |
The one fix (or maybe checkbox option to select) is that Obsidian never released this feature as an in-line or seamless block. I would love to see that here. |
I'd love to see this added. And transcluding links at the block level too, including transcluding sub-list items if applicable. |
(This is more of a core feature, rather than an enhancement, inasmuch as foam is trying to replicate Roam behavior):
Roam, and now Obsidian, provide support for block-level linking between markdown notes. It would be great if Roam could follow suit and provide this capapbilty.
Unfortunately, there are now three styles of intra-note linking to choose from:
((block-id))
to text block (bullet) with internal block-id[[NoteTitle#^block-id]]
-- link to a text block annotated with^block-id
[Description](#heading-id)
-- link to a heading annotated with{#custom-id}
I vote for the Obsidian-style linking, since this is the format that I'd imagine most people will be co-editing with vscode.
The text was updated successfully, but these errors were encountered: