From: Ihor Radchenko <yantar92@gmail.com>
To: "András Simonyi" <andras.simonyi@gmail.com>
Cc: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] oc-csl: Add support for nocite citations
Date: Sun, 03 Jul 2022 19:58:37 +0800 [thread overview]
Message-ID: <875ykeh0gi.fsf@localhost> (raw)
In-Reply-To: <CAOWRwxAAhfNDzd1-PD3yZSEt7dFOAKZaveTPMPOEgXgYEXeqfg@mail.gmail.com>
András Simonyi <andras.simonyi@gmail.com> writes:
>> By "*", do you mean something like [cite/n:@*]?
>> If so, will it be correctly fontified as an existing citation?
>
> ... As for fontification, this is a very good
> question! I've checked it now with the built-in "basic"
> activation processor and it shows the "*" with an "error" face,
> indicating that it's not a key in the bibliography file(s), which
> might not be ideal. Nonetheless, this problem is not limited to or
> introduced by this patch, because the same construct and
> functionality is also supported by the "biblatex" and "natbib" export
> processors. Actually, the possibility of using "*" as a key comes
> simply
> from a citeproc-el change, not from oc-csl, I just thought that it is
> obscure enough to merit an explicit mention in the NEWS file.
I do understand that @* syntax is coming from citeproc-el. However, we
are talking about changes to Org core. If Org highlights @* with 'error
face, some users will be confused.
Could you please elaborate about "the same construct and functionality
is also supported by the "biblatex" and "natbib" export processors"?
I cannot call myself expert in LaTeX, but I've never heard about LaTeX
\cite/\nocite commands supporting "*" argument. I cannot find any traces
of "*" functionality in oc-bibtelatex/oc-natbib as well.
Best,
Ihor
next prev parent reply other threads:[~2022-07-03 11:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 9:30 [PATCH] oc-csl: Add support for nocite citations András Simonyi
2022-07-02 4:38 ` Ihor Radchenko
2022-07-02 8:32 ` András Simonyi
2022-07-03 11:58 ` Ihor Radchenko [this message]
2022-07-03 12:26 ` Bruce D'Arcus
2022-07-03 12:35 ` Ihor Radchenko
2022-07-03 12:38 ` Bruce D'Arcus
2022-07-03 12:53 ` John Kitchin
2022-07-03 13:10 ` [BUG] @* in [cite/nocite:@*] is a valid special LaTeX bibliography key, but it is highlighted using "error" face by oc.el (was: [PATCH] oc-csl: Add support for nocite citations) Ihor Radchenko
2022-07-04 6:53 ` András Simonyi
2022-07-04 12:28 ` Ihor Radchenko
2022-07-04 12:57 ` András Simonyi
2022-07-04 13:16 ` Bruce D'Arcus
2022-07-04 11:54 ` [PATCH] oc-csl: Add support for nocite citations Ihor Radchenko
2022-07-05 19:17 ` Bruce D'Arcus
2022-07-05 19:28 ` Bruce D'Arcus
2022-07-05 19:37 ` Bruce D'Arcus
2022-07-07 10:46 ` 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
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=875ykeh0gi.fsf@localhost \
--to=yantar92@gmail.com \
--cc=andras.simonyi@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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 public 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).