From: "Bruce D'Arcus" <firstname.lastname@example.org>
To: John Kitchin <email@example.com>
Cc: org-mode mailing list <firstname.lastname@example.org>,
Nicolas Goaziou <email@example.com>
Subject: Re: A minor suggestion about formatting citations
Date: Mon, 11 Oct 2021 10:54:09 -0400 [thread overview]
Message-ID: <CAF-FPGPyMqj8=cJV52EUQWp6RvRdeS2rzp5DjJ8qaen4WWa2XA@mail.gmail.com> (raw)
On Mon, Oct 11, 2021 at 10:28 AM John Kitchin <firstname.lastname@example.org> wrote:
> you should probably trim each key, and re-add spaces where you want them in the function that does these kinds of things.
I realize that's an option, but something about that feels wrong to me.
We're adding a single space as prefix, not because it's meaningful for
citation purposes (there actually is no prefix, though org-cite
interprets it as " "), but only so buffer formatting works correctly.
And then presumably code needs to be added to the export machinery to
strip those empty affixes?
Am not saying the latter goal isn't important; just seems like the
side effect isn't ideal.
> Maybe that should even be controlled by a defcustom that allows 0-1 spaces.
You mean in org-cite? I think that'd be my preference, unless there's
a better solution to this issue.
next prev parent reply other threads:[~2021-10-11 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 23:09 A minor suggestion about formatting citations Vikas Rawal
2021-10-11 7:38 ` Eric S Fraga
2021-10-11 9:40 ` Nicolas Goaziou
2021-10-11 13:38 ` Bruce D'Arcus
2021-10-11 14:28 ` John Kitchin
2021-10-11 14:54 ` Bruce D'Arcus [this message]
2021-10-11 15:54 ` Nicolas Goaziou
2021-10-11 16:55 ` Bruce D'Arcus
2021-10-13 12:51 ` Nicolas Goaziou
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).