From: Ihor Radchenko <yantar92@posteo.net>
To: Edgar Lux <edgarlux@mailfence.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] #+cite_export: ... bibstyle citestyle cannot be universally used as global defaults (was: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite)
Date: Sat, 04 Feb 2023 11:31:35 +0000 [thread overview]
Message-ID: <87ilghfyzs.fsf@localhost> (raw)
In-Reply-To: <746321315.112536.1675416834079@ichabod.co-bxl>
Edgar Lux <edgarlux@mailfence.com> writes:
> ... All in all, the idea sounds great. I appreciate that my opinion is taken into account, but I know very little about citation systems. I was only a bit concerned about the effort which is needed to implement the changes, as little as they may be.
At this point, we should not jump into the implementation. Rather
discuss possible pros and cons.
For example, looking at my proposal now, I see how the proposed idea is
a bit awkward:
In #+cite_export: processor[opt1=val1,opt2=val2,...] bibliography-style[...] citation-style[...]
I assumed that there is one "major" bibliography-style/citation-style.
However, it is not really the case in practice. The styles are combined.
For example, adding links to bibliography to citations is applied
regardless of the particular citation command being used.
So, I am not leaning closer to only allowing options being passed to
"processor", but not to styles. This will at least come closer to
certain settings being citation package global config applied to
everything. If we have options applied to specific citation commands,
they will rather fit into citation-style/sub-style.
#+cite_export: processor[opt1=val1,opt2=val2,...] bibliography-style citation-style
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-02-04 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 21:31 Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite Edgar Lux
2023-01-20 10:59 ` Ihor Radchenko
2023-01-20 16:57 ` Edgar Lux
2023-01-21 8:37 ` Ihor Radchenko
2023-01-21 20:25 ` Edgar Lux
2023-01-22 11:15 ` Ihor Radchenko
2023-01-22 11:36 ` András Simonyi
2023-01-22 19:47 ` Edgar Lux
2023-01-23 10:43 ` Ihor Radchenko
2023-01-22 19:19 ` Edgar Lux
2023-01-23 11:06 ` Ihor Radchenko
2023-01-23 20:58 ` Edgar Lux
2023-01-24 10:54 ` [BUG] #+cite_export: ... bibstyle citestyle cannot be universally used as global defaults (was: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite) Ihor Radchenko
2023-02-03 9:33 ` Edgar Lux
2023-02-04 11:31 ` Ihor Radchenko [this message]
2023-02-04 23:14 ` Edgar Lux
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=87ilghfyzs.fsf@localhost \
--to=yantar92@posteo.net \
--cc=edgarlux@mailfence.com \
--cc=emacs-orgmode@gnu.org \
/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).