You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This package definitely fits my philosophy far better than org-roam. Backlinks are handy, but I'd much rather rely on old-fashioned medium-length org documents than a zettelkasten web of tiny snippets with special indexing and node mapping.
However, org-super-links is erroring when I try to link to the top level of a file instead of a heading within it. When I use org-super-links-store-link and then org-super-links-insert-link, it fails with e.g. Before headline at position 35 in buffer semiotics.org. Choosing the file with org-super-links-link gets me Wrong type argument: stringp, nil.
Is this intended behavior? AFAIK, there should be no issue in principle with putting a drawer at top level, before headings.
The text was updated successfully, but these errors were encountered:
This package definitely fits my philosophy far better than org-roam. Backlinks are handy, but I'd much rather rely on old-fashioned medium-length org documents than a zettelkasten web of tiny snippets with special indexing and node mapping.
However, org-super-links is erroring when I try to link to the top level of a file instead of a heading within it. When I use
org-super-links-store-link
and thenorg-super-links-insert-link
, it fails with e.g.Before headline at position 35 in buffer semiotics.org
. Choosing the file withorg-super-links-link
gets meWrong type argument: stringp, nil
.Is this intended behavior? AFAIK, there should be no issue in principle with putting a drawer at top level, before headings.
The text was updated successfully, but these errors were encountered: