From: Richard Lawrence <email@example.com>
To: Bruce D'Arcus <firstname.lastname@example.org>,
Bruce D'Arcus <email@example.com>,
Subject: Re: org-cite: make 'suppress-author' a citation 'style'
Date: Mon, 26 Apr 2021 09:51:00 +0200 [thread overview]
Message-ID: <87pmyhjxgb.fsf@aquinas> (raw)
"Bruce D'Arcus" <firstname.lastname@example.org> writes:
>> We introduced :suppress-author because someone requested it at some
>> point. I don't remember who, but it may be worth asking that person.
> I did some quick searching.
> Wow; this goes back a long time!
> Anyway, Richard Lawrence summarized previous discussions, which includes
> this detail, in this 2015 post:
> Not sure if he introduced the idea or not, but if not, he should know.
I don't remember exactly anymore, and a quick search does not turn up
the source, but I can say in general that the concern back then was to
make the citation syntax at least as flexible as the BibLaTeX citation
commands, to support users who currently use BibLaTeX (and don't have
much interest in non-LaTeX output).
> I think there are two points to consider before removing suppress-author
>> 1. does it make sense to apply it independently on references within
>> a full citation?
I don't remember what my thinking was exactly, but it was probably
something like this: (a) we need citations with multiple references; (b)
in some such citations we may need to suppress the author of some
references without suppressing the author of others; (c) thus
:suppress-author must be a reference-level property, not a property of
the whole citation object and (d) uniformity demands that every
reference should have it (even if it doesn't make sense in practice to
apply it to references in the middle of the list).
That said, here is a possible use case for this: suppose you are
referencing multiple works from a given author and want to avoid
printing the author's name multiple times, but also want to include a
further reference to a work by another author:
e.g. you can write
Smith claims foo [(cite): -@Smith2019; -@Smith2020; see also @Jones2018].
Smith claims foo (2019; 2020; see also Jones 2018).
Does that help?
next prev parent reply other threads:[~2021-04-26 7:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 10:52 Bruce D'Arcus
2021-04-24 12:28 ` Bruce D'Arcus
2021-04-24 17:08 ` Nicolas Goaziou
2021-04-24 17:28 ` Bruce D'Arcus
2021-04-24 19:36 ` Bruce D'Arcus
2021-04-24 20:09 ` Nicolas Goaziou
2021-04-24 22:51 ` Bruce D'Arcus
2021-04-25 5:55 ` András Simonyi
2021-04-25 12:50 ` Bruce D'Arcus
2021-04-25 19:48 ` András Simonyi
2021-04-25 20:12 ` Bruce D'Arcus
2021-04-26 7:53 ` Denis Maier
2021-04-26 9:05 ` Denis Maier
2021-04-26 9:34 ` Joost Kremers
2021-04-26 11:36 ` Bruce D'Arcus
2021-04-26 7:51 ` Richard Lawrence [this message]
2021-04-26 9:33 ` Bruce D'Arcus
2021-04-27 7:36 ` Richard Lawrence
2021-04-27 7:52 ` Denis Maier
2021-04-27 8:24 ` Richard Lawrence
2021-04-27 10:05 ` Bruce D'Arcus
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).