From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: org-cite styles don't allow * in them
Date: Tue, 5 Apr 2022 13:41:38 -0400 [thread overview]
Message-ID: <CAF-FPGPa_Fa-DzLF2iX3eAOt5EGAPO_NEY5bY_RtrHVsetSF7w@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETrxX28dMHK3UsKodYZz02xfwR1W5nm4AQvXBjU-1LLQRg@mail.gmail.com>
On Tue, Apr 5, 2022 at 12:11 PM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>
> Would you find it suitable to use [cite/command:pre @key post] in general?
I think it's a reasonable approach that would appeal to some users who
would treat org as a front-end to LaTeX primarily, and obviously
previous org-ref users, and that it's better than supporting this in a
parallel but incompatible syntax.
> For portability, I suppose there could be a defcustom mapping if one wanted to leverage the oc-csl library with pretty minimal effort.
Right.
I'm not sure what the precise right solution is, where, but something like that.
oc-biblatex, for example, has the new org-cite-biblatex-styles
defcustom, whose list entries look like:
("author" "caps" "Citeauthor*" nil nil)
So with that, a oc-biblatex user can already do this presumably.
("Citeauthor*" nil "Citeauthor*" nil nil)
But could also have a new org-ref processor with a simpler defcustom like:
("Citeauthor*" . "author/caps")
> I think two things need to be addressed to fix that. First is allowing a * in the style/variant section; there are probably 17 or so of these commands in natbib/biblatex. Second is fixing org-activate-link so that link activation functions don't get called on something like [cite/citet:@key]. This is necessary for org-ref and org-cite to co-exist, but also other packages or users might also define links like cite:.
+1
Bruce
next prev parent reply other threads:[~2022-04-05 17:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 21:06 org-cite styles don't allow * in them John Kitchin
2022-04-05 15:56 ` Bruce D'Arcus
2022-04-05 16:11 ` John Kitchin
2022-04-05 17:41 ` Bruce D'Arcus [this message]
2022-04-07 4:17 ` Ihor Radchenko
2022-04-07 11:30 ` John Kitchin
2022-04-16 16:29 ` Bruce D'Arcus
2022-04-17 8:42 ` Ihor Radchenko
2022-04-17 12:14 ` John Kitchin
2022-04-17 13:18 ` Ihor Radchenko
2022-04-17 14:24 ` John Kitchin
2022-04-18 9:09 ` Ihor Radchenko
2022-04-18 10:25 ` Bruce D'Arcus
2022-04-19 2:59 ` Ihor Radchenko
2022-04-21 8:06 ` Nicolas Goaziou
2022-04-21 10:09 ` Ihor Radchenko
2022-04-21 11:28 ` Nicolas Goaziou
2022-04-21 13:40 ` Ihor Radchenko
2022-04-22 12:42 ` Bruce D'Arcus
2022-04-22 13:30 ` John Kitchin
2022-05-22 15:51 ` Bruce D'Arcus
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF-FPGPa_Fa-DzLF2iX3eAOt5EGAPO_NEY5bY_RtrHVsetSF7w@mail.gmail.com \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).