emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: mail@nicolasgoaziou.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: oc-biblatex too aggressive in replacing styles
Date: Tue, 30 Nov 2021 20:43:10 +0100	[thread overview]
Message-ID: <87ilw9whtd.fsf@gmx.us> (raw)
In-Reply-To: <87fsrgp2ww.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 28 Nov 2021 19:10:07 +0100")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Rasmus <rasmus@gmx.us> writes:
>
>> However, I think it is currently too aggressive in overwriting styles.
>
> Ah?
>
>> Could it perhaps accept any style that is given in
>> ‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’ and only
>> overwrite it if another style is explicitly specified in the file to be
>> exported?
>
> Isn't it the case already?

For me it is not. But maybe I used the latest release and not the latest git version.  Let me recheck and get pack. 

>> Currently, the only way I have found that I can specify that I want to use
>> biblatex-chicago is by issuing
>>
>>     #+cite_export: biblatex chicago-authordate
>
> If you need chicago-authordate style globally, you can set
> `org-cite-export-processors' instead, e.g., to
>
>   ((t biblatex "chicago-authordate"))

I see. I had missed that you could supply a third argument, but it seems to work perfectly! Thanks! 
(And sorry about the noise.)

Maybe I will try to write a patch for the manual.

Kind regards,
Rasmus

-- 
A clever person solves a problem. A wise person avoids it


      reply	other threads:[~2021-11-30 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 17:01 oc-biblatex too aggressive in replacing styles Rasmus
2021-11-28 17:19 ` Bruce D'Arcus
2021-11-28 17:38   ` Bruce D'Arcus
2021-11-28 17:48     ` Rasmus
2021-11-28 18:10 ` Nicolas Goaziou
2021-11-30 19:43   ` Rasmus [this message]

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=87ilw9whtd.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).