From: "M. ‘quintus’ Gülker" <post+orgmodeml@guelker.eu>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>, emacs-orgmode@gnu.org
Subject: Re: [bug] Macro in citation not expanded
Date: Mon, 17 Oct 2022 19:11:30 +0200 [thread overview]
Message-ID: <87tu425pla.fsf@guelker.eu> (raw)
In-Reply-To: <87lepg6rmh.fsf@localhost>
Am Sonntag, dem 16. Oktober 2022 schrieb Ihor Radchenko:
> Only bold, code, entity, italic, latex-fragment, strike-through,
> subscript, superscript, underline, and verbatim objects are allowed
> inside citations.
> This is hard-coded inside `org-element-object-restrictions'.
This is a bit unfortunate, because I like to use macros for inserting
semantic formatting which is not part of org’s syntax. In the example
given in my OP, I use it to mark up names with small caps. The exact
example given includes a short note by me talking about the cited author
a little further. Another example where I need this is when I cite some
statement made in an interview, which may come out as something like:
[cite:{{{name(Interviewee)}}} in @interviewer p. 5]
Indirect statements by persons mentioned in news articles are another
example where I would use such a construct.
I define the `name' macro in such a way that it will format
`Interviewee` in the same way as the citation style formats the author
name for @interviewer, ensuring uniformness in the created footnote.
I also use the very same `name' macro inside the actual article text, so
that uniform formatting is guaranteed there as well.
> It sounds reasonable to allow macros inside citation references.
> Maybe we also want to allow other things. Maybe simply allow all objects
> but other citations, line-breaks, and table-cells?
I have no strong opinion on this. I certainly do not need tables inside
citations. If it is easy to just permit everything except what you
named, I would say just allow it. Maybe someone has use for it. Maybe
footnotes inside [cite:] construct should also not be allowed, at least
for footnote-based styles.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kontakt@guelker.eu | O<
next prev parent reply other threads:[~2022-10-17 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 9:07 [bug] Macro in citation not expanded M. ‘quintus’ Gülker
2022-10-16 9:32 ` Ihor Radchenko
2022-10-17 17:11 ` M. ‘quintus’ Gülker [this message]
2022-10-18 4:31 ` [RFC PATCH] " Ihor Radchenko
2022-11-11 20:50 ` M. ‘quintus’ Gülker
2022-11-13 4:12 ` Ihor Radchenko
2024-01-24 11:30 ` Ihor Radchenko
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=87tu425pla.fsf@guelker.eu \
--to=post+orgmodeml@guelker.eu \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=yantar92@posteo.net \
/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.