emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Bruce D'Arcus <bdarcus@gmail.com>
Cc: Greg Minshall <minshall@umich.edu>,
	emacs-orgmode@gnu.org,
	Titus von der Malsburg <malsburg@posteo.de>
Subject: Re: org-cite-list-bibliography-files
Date: Mon, 26 Jul 2021 11:31:06 -0400	[thread overview]
Message-ID: <m2v94xytvp.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <CAF-FPGMxaSPDTt1RJ8fF=_faeWKCX6U6YG5eqB9+r2OXyKO9JA@mail.gmail.com>

I think it should work like setting header args on src-blocks, where
there is a hierarchy that the most local setting always overrides the
less local setting, described at https://orgmode.org/manual/Using-Header-Arguments.html.

This gives you the opportunity for system wide args, e.g. a global set
of bib files via a variable setting,

file-level options via keyword settings

header-level options via property settings

src-block level options

For bibliographies, it is only necessary to go to file-level I think.

Bruce D'Arcus <bdarcus@gmail.com> writes:

> Hi Greg,
>
> On Mon, Jul 26, 2021 at 1:56 AM Greg Minshall <minshall@umich.edu> wrote:
>
>> is a reasonable approach: if local, use just that; if no local, use
>> global (if it exists).
>>
>> then, the "alternative" might be: use both local and global?
>
> That should be the default.
>
> But as Emmanual noted last week, there are cases where one might want
> to combine them.
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2021-07/msg00495.html
>
> It's just not the common case.
>
> Bruce


--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
Pronouns: he/him/his


  reply	other threads:[~2021-07-26 15:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 14:47 org-cite-list-bibliography-files Titus von der Malsburg
2021-07-25 15:14 ` org-cite-list-bibliography-files Bruce D'Arcus
2021-07-25 15:36   ` org-cite-list-bibliography-files Titus von der Malsburg
2021-07-25 21:30     ` org-cite-list-bibliography-files Bruce D'Arcus
2021-07-26  5:56       ` org-cite-list-bibliography-files Greg Minshall
2021-07-26  8:46         ` org-cite-list-bibliography-files Bruce D'Arcus
2021-07-26 15:31           ` John Kitchin [this message]
2021-07-26 10:46     ` org-cite-list-bibliography-files Eric S Fraga
2021-07-28 13:12 ` org-cite-list-bibliography-files Bruce D'Arcus
2021-07-28 13:56   ` org-cite-list-bibliography-files John Kitchin
2021-07-28 14:17     ` org-cite-list-bibliography-files von der Malsburg, Titus
2021-07-28 19:17       ` org-cite-list-bibliography-files Bruce D'Arcus
2021-07-28 14:19   ` org-cite-list-bibliography-files Titus von der Malsburg
2021-07-28 14:22     ` org-cite-list-bibliography-files John Kitchin
2021-07-30  7:49 ` org-cite-list-bibliography-files Nicolas Goaziou

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=m2v94xytvp.fsf@andrew.cmu.edu \
    --to=jkitchin@andrew.cmu.edu \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=malsburg@posteo.de \
    --cc=minshall@umich.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).