From: "Bruce D'Arcus" <email@example.com> To: "Bruce D'Arcus" <firstname.lastname@example.org>, org-mode-email <email@example.com>, Richard Lawrence <firstname.lastname@example.org> Subject: Re: org-cite: make 'suppress-author' a citation 'style' Date: Sat, 24 Apr 2021 13:28:03 -0400 [thread overview] Message-ID: <CAF-FPGOz6j3q2cv-j7Y6qEWB-x4NAfK5CZxS5qshu74hf80boA@mail.gmail.com> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1683 bytes --] On Sat, Apr 24, 2021, 1:08 PM Nicolas Goaziou <firstname.lastname@example.org> wrote: > Hello, > > "Bruce D'Arcus" <email@example.com> writes: > > > This distinction is wrong, and we should treat "suppress-author" as a > > citation style instead. > > > > The result would be: > > > > [cite/supress-author:doe19;doe20] > > > > Or even can keep the shorthand: > > > > [cite/-:doe19;doe20] > > > > In fact, with the change, could even remove it entirely > > 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: https://lists.gnu.org/archive/html/emacs-orgmode/2015-02/msg00932.html Not sure if he introduced the idea or not, but if not, he should know. I think there are two points to consider before removing suppress-author > syntax: > > 1. does it make sense to apply it independently on references within > a full citation? > > 2. does it make sense to apply it on top of another style? > Yes; excellent summary. As I say, my impulse is to say no to both, outside some corner cases that people could work around in other ways. But I hope people will challenge me if this is a bad idea. And hopefully Richard can weigh in. If both answers are no, this can definitely go away. > > > Or even can keep the shorthand: > > > > [cite/-:doe19;doe20] > > Note that Org Citation library does not recognize styles. It is up to > the processor to interpret it as a short-hand for "suppress-author". > Right; I understand. Bruce > [-- Attachment #2: Type: text/html, Size: 3377 bytes --]
next prev parent reply other threads:[~2021-04-24 17:29 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 [this message] 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 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
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-FPGOz6j3q2cv-j7Y6qEWB-x4NAfK5CZxS5qshu74hf80boA@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: org-cite: make '\''suppress-author'\'' a citation '\''style'\''' \ /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
Code repositories for project(s) associated with this 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).