From: "Bruce D'Arcus" <firstname.lastname@example.org>
To: Ypo <email@example.com>
Cc: org-mode-email <firstname.lastname@example.org>
Subject: Re: Could a citation act as a link, or a link to be exported as a citation?
Date: Mon, 7 Jun 2021 08:24:02 -0400 [thread overview]
Message-ID: <CAF-FPGOH+9TBGyvpnFupmFPHE=y5sGSnyfaLG14fF0E-qSN7yg@mail.gmail.com> (raw)
On Mon, Jun 7, 2021 at 3:02 AM Ypo <email@example.com> wrote:
> I've been reading you about cites. Conversation is above my head, but just in case it could be helpful, I would like to address a frequent problem in the workflow of taking notes, that advanced users suffer too.
> When taking notes, it's usual to make some bibliographical references in one file and some related notes in a different file. I link both using internal links, but it can't be exported directly as a bibliography, which would be cool indeed.
> Could a citation act as a link, or a link to be exported as a citation?
In general, a citation is conceptually a kind of specialized link.
And org-ref and now org-cite is designed around the possibility of
attaching actions to those citations. So, for example:
> An example, could the link "[[id:20210607T083216.726761][...]]" be substituted by a cite, that takes you to the reference?
The oc-basic processor has an at-point function that will do just
this, if by "reference" you mean the bibtex (and maybe ultimately csl
json) source entry.
Have you looked at org-roam and org-roam-bibtex?
If not, that might give you some ideas, as it heavily relies on org
links, but also has support for citations.
Plans there are to support org-cite, BTW.
prev parent reply other threads:[~2021-06-07 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 7:02 Could a citation act as a link, or a link to be exported as a citation? Ypo
[not found] ` <firstname.lastname@example.org>
2021-06-07 10:37 ` Ypo
2021-06-07 12:24 ` Bruce D'Arcus [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).