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
I propose a new org-linker feature which replaces helm-org-contacts with one command of org-linker.
I do think of this workflow:
User invokes new command which takes a path to an Org file or maybe even a combination of Org file + some identifier of a sub-heading (new behavior)
command asks user for her query string (just like sl-quick-insert-inline-link
a link is inserted and a back-link is inserted at the other side as well (just like sl-quick-insert-inline-link)
This way, I can quickly link contacts with back-links.
If this function is implemented that way, that an arbitrary file or an arbitrary sub-heading is used as parameter to define the scope for link targets, I do think that this function is going to be extremely versatile for many use-cases, not just linking contacts. Users might define their commands to link to headings of a specific projects, specific blog posts written within org, and so forth.
Thank you!
The text was updated successfully, but these errors were encountered:
Let me make sure I understand the use case correctly. It sounds basically like org-super-links functionality, but with the ability to limit the search buffers to a specific buffer or heading?
This way, a user is able to limit the search space to a specific buffer (my contacts only) or (as the optional extension) a headings (my current project).
Hi,
I'm using https://github.com/tmalsburg/helm-org-contacts to link to contacts within one Org file since years.
I propose a new org-linker feature which replaces helm-org-contacts with one command of org-linker.
I do think of this workflow:
sl-quick-insert-inline-link
sl-quick-insert-inline-link
)This way, I can quickly link contacts with back-links.
If this function is implemented that way, that an arbitrary file or an arbitrary sub-heading is used as parameter to define the scope for link targets, I do think that this function is going to be extremely versatile for many use-cases, not just linking contacts. Users might define their commands to link to headings of a specific projects, specific blog posts written within org, and so forth.
Thank you!
The text was updated successfully, but these errors were encountered: