Post · bonfire.cafe

Post

Recently there's some stream of former #logseq users coming to @silverbulletmd this leads to some interesting observations and ideas on what these users miss compared to their previous workflows: https://community.silverbullet.md/t/coming-from-logseq-outlines-and-linked-mentions/290

I remembered that @toolsontech had a series of #LogSeq videos so decided to revisit them. Good to understand what "the logseq way" looks like, to see if we can somehow support it in #SilverBullet, or if that makes any sense at all.

https://www.youtube.com/watch?v=uJclYLS4oHs

Bas (Tools on Tech)

@toolsontech@pkm.social replied · 4 days ago

@zef @silverbulletmd Would kill for getting my sidebar in Silverbullet 😄

Less of an issue with multiple windows, but that and linking to specific lines the two things I miss most

Zef Hemel

@zef@social.zef.pub replied · 4 days ago

@toolsontech never say never, but I mentally delegated sidebars and panels and tabs to the browser you use. Various ones support split panes now 😉 Linking to specific lines, yeah, this is a fundamental issue: how do you persistently point to a place in a text file taking into account that one may put more characters before it laster on?

Bas (Tools on Tech)

@toolsontech@pkm.social replied · 4 days ago

@zef I would say stay as close to Markdown specs as possible, since we can define custom ID's to headings to link to (See https://www.markdownguide.org/extended-syntax/#heading-ids) maybe using that but also accepting those ID's on non headers would be closest to the specs.

I think obsidians method (Adding ^uniqueid) also very clean, and probably used at larger scale.

Updating the line numbers, while possible would never be robust enough.

Extended Syntax | Markdown Guide

Advanced features that build on the basic Markdown syntax.

Zef Hemel

@zef@social.zef.pub replied · 4 days ago

@toolsontech At some point I introduced a named anchor syntax: $myAnchor allowing you to link to it, e.g. [[page$myAnchor]] removed that since nobody seemed to use it (neither did I)

Bas (Tools on Tech)

@toolsontech@pkm.social replied · 4 days ago

@zef Love that you always take the effort to remove unused features. Keeps the application lean.

Zef Hemel

@zef@social.zef.pub replied · 4 days ago

@toolsontech only way not to go insane. Also: a rare opportunity to actually do this. What product regularly removes features? I also still do it too rarely with SB, but v2 was an opportunity for a rapture.

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.1-beta.28 no JS en

Automatic federation enabled