# Generate Link @ Cursor Position

**URL:** https://community.silverbullet.md/t/generate-link-cursor-position/3372
**Category:** Plugs and Libraries
**Created:** [October 11, 2025, 1:41pm UTC](https://community.silverbullet.md/t/generate-link-cursor-position/3372 "2025-10-11T13:41:25Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ChenZhu-Xie](https://community.silverbullet.md/user_avatar/community.silverbullet.md/chenzhu-xie/32/1476_2.png) [@ChenZhu-Xie](https://community.silverbullet.md/u/ChenZhu-Xie)
#### Post date: [October 11, 2025, 6:53pm UTC](https://community.silverbullet.md/t/generate-link-cursor-position/3372/2 "2025-10-11T18:53:10Z")

</div>

An analogy to help @zef and those intrigued by this intellectual exercise understand:

At present, the **`Linked Mentions`** and **`Linked Tasks`** widgets of a given `[[Page A]]` are essentially Cursor-level precise backlink **s** — each pointing from the `[[Page A]]` to a specific cursor position within other`[[Page ?]]` **s**.

Now, imagine that **these 2 backlink widgets are no longer fixed at the top or bottom of a `[[Page A]]`**, but can instead float freely.  
In that case, they no longer belong to a particular **Page Object** `[[Page A]]`, but rather to a designated **Anchor Object** `[[Page A@pos]]`.

This instantly yields automatic backlink **s** for “floating” `[[Page A@pos]]` (rather than “fixed” `[[Page A]]`), since it reuses _ **the precise backlinks mechanism** _ already implemented in `Library/Std/Widgets/Widgets`.

Furthermore, the former forward/outward link **s** (from `[[Page ?]]` **s** ) to `[[Page A]]` would now all become link **s** to `[[Page A@pos]]`. Note that this simply requires extending the index to also record and update the pos and corresponding `[[Page A@pos]]` name — which is quite feasible, given that `Library/Std/Widgets/Widgets` already employs a similar mechanism in Auto-Backlink **s**.

Beyond this, nothing more is required — it is essentially a fine-grained **Cursor-level** extension of the existing **Page-level** system. And although it may appear somewhat recursive, there is no actual loop involved.

Believe me, this will be the **next killer feature** of SB v2, **second only to `Linked Tasks`** : fully automated, cursor-level precise for/out-ward and back/in-ward linking — something almost no other note-taking software/website/app has achieved.

I have already implemented this exact functionality in [the supplementary materials of my short paper](https://arxiv.org/abs/2412.17224) as well as in my [PhD dissertation](https://github.com/ChenZhu-Xie/NJU_thesis_doctor__xcz). Since it can be realized in the **LaTeX** ecosystem, it is certainly **achievable** in **SilverBullet**.

1/2 of the journey remains:

manual Forwardlink to a `[[Certain Page]]`  
 auto Backlink **s** to `[[Other Pages@pos]]` **s** with **auto-updated pos**  **s** from a `[[Certain Page]]`  
 auto Backlink **s** to `[[Other Pages@pos_O]]` **s** with **auto-updated pos\_O**  **s** from a `[[Certain Page@pos_C]]`  
 manual Forwardlink to a `[[Certain Page@pos_C]]` with **auto-updated pos\_C** (without **s**!)

Note that once the 4 points above are implemented, the referencing positions of `[[Other Pages@pos_O]]` **s** may themselves reside within the `[[Certain Page]]` which contains the anchor `[[Certain Page@pos_C]]` that is cited. This signifies a complete transition away from the Page-based paradigm.

Keep going, @zef — this “_will definitely make SB great again_”!

---

_[View the full topic](https://community.silverbullet.md/t/generate-link-cursor-position/3372)._