emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Rudolf Adamkovič" <salutis@me.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Mention #+PRINT_BIBLIOGRAPHY in the Org manual
Date: Sat, 22 Oct 2022 09:18:12 -0400	[thread overview]
Message-ID: <CAF-FPGNDu9cOiw0gvPfXxO0Kd3Sj8iEYwkN=ht=e_nE+zeUxEw@mail.gmail.com> (raw)
In-Reply-To: <87wn8s1j7q.fsf@localhost>

I'm not sure what I think about this. I can't ever recall having a
practical issue with this example (I'd expect it's more common for
people with very long cite keys?), though in the past I have had
issues with whitespace when moving around citation-references
programmatically (as, for example, with
~citar-org-shift-reference-left~ and such).

On Sat, Oct 22, 2022 at 2:14 AM Ihor Radchenko <yantar92@posteo.net> wrote:
> Rudolf Adamkovič <salutis@me.com> writes:
> > Ihor Radchenko <yantar92@posteo.net> writes:
> >
> >> Feel free to submit a patch for org-cite-make-insert-processor.
> >
> > Could the patch make '[cite: @key]' the new default when inserting
> > citations, or should it introduce a new customization point?
> I think it can be the new default.
> However, please send the patch in a separate thread, so that people can
> see it and oppose if they have objections.
> --
> 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>

      reply	other threads:[~2022-10-24  1:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 10:59 [BUG] Mention #+PRINT_BIBLIOGRAPHY in the Org manual Rudolf Adamkovič
2022-06-14  6:47 ` Marvin Gülker
2022-10-20  4:40 ` Ihor Radchenko
2022-10-20 14:42   ` Rudolf Adamkovič
2022-10-21  3:22     ` Ihor Radchenko
2022-10-21 14:56       ` Rudolf Adamkovič
2022-10-22  6:11         ` Ihor Radchenko
2022-10-22 13:18           ` Bruce D'Arcus [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:

  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-FPGNDu9cOiw0gvPfXxO0Kd3Sj8iEYwkN=ht=e_nE+zeUxEw@mail.gmail.com' \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=salutis@me.com \
    --cc=yantar92@posteo.net \


* 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).