From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Tom Gillespie <tgbugs@gmail.com>,
org-mode-email <emacs-orgmode@gnu.org>,
Bruce D'Arcus <bdarcus@gmail.com>
Subject: Re: [org-cite] citations in property drawers?
Date: Wed, 15 Sep 2021 21:20:09 +0200 [thread overview]
Message-ID: <87r1dp63yu.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJ51ETpmqFMy0PbfjTNxuUR0U9ri_V1=ZvSSfNESF=bjdBrJ2Q@mail.gmail.com> (John Kitchin's message of "Wed, 15 Sep 2021 13:19:48 -0400")
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> Not all org files are destined for export. I slightly feel users should be
> allowed to put citations in places where it might not make sense in export,
> and that they are responsible for knowing what they are doing.
>
> I am sympathetic to the reality that the second half of that statement is a
> big ask, and that it can lead to confusion. Nothing stops anyone from
> manually typing or pasting a citation into those places though. I would be
> inclined to use the activate function to highlight those that are in places
> that won't export, rather than limit where people can put them using the
> insert mechanism.
Not all Org files are destined for export, yet any syntactically correct
Org file is expected to export without fuss. So, allowing citations
anywhere and then let Org later fail without notice may be asking for
trouble.
I understand the problem, but the solution should not be: "let's pretend
export does not exist".
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-09-15 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 20:18 [org-cite] citations in property drawers? Bruce D'Arcus
2021-09-09 18:44 ` Bruce D'Arcus
2021-09-15 5:05 ` Tom Gillespie
2021-09-15 12:41 ` Nicolas Goaziou
2021-09-15 17:02 ` Tom Gillespie
2021-09-15 17:19 ` John Kitchin
2021-09-15 19:20 ` Nicolas Goaziou [this message]
2021-09-16 16:52 ` Tom Gillespie
2021-09-15 17:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1dp63yu.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=tgbugs@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.