From: Ihor Radchenko <yantar92@gmail.com>
To: "András Simonyi" <andras.simonyi@gmail.com>
Cc: John Kitchin <jkitchin@andrew.cmu.edu>,
Bruce D'Arcus <bdarcus@gmail.com>,
emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: [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)
Date: Mon, 04 Jul 2022 20:28:36 +0800 [thread overview]
Message-ID: <87zghpm58r.fsf@localhost> (raw)
In-Reply-To: <CAOWRwxANA8TGvRSgRb8grv96E6wTSaZ37xoX2ONm8BmKvb+QhA@mail.gmail.com>
András Simonyi <andras.simonyi@gmail.com> writes:
> I think that the problem with simply adding one or more new activation
> processors with different fontification for the "*" key is that Org
> has no way of knowing (at least for sure) which export processor will
> be used for a exporting a certain Org buffer, since it can depend on
> the chosen export backend (see the variable
> org-cite-export-processors). E.g., org-cite could be set up to use the
> "natbib" processor for "LaTeX" export and the "basic" processor for
> any other format. I think that it'd be more in the spirit of the
> "basic" activation processor to be more permissive and not treat "*"
> as an error, similarly to citation styles not supported by the "basic"
> export processor but supported by others.
I do not agree.
If someone sets up natbib for latex export and basic for other formats,
"*" will not be correctly exported in those other formats (because basic
does not support @* syntax) - something fontification should better
highlight for the user.
Also, are there any similar non-key constructs in latex in addition to "*"?
Best,
Ihor
next prev parent reply other threads:[~2022-07-04 12:30 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
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 [this message]
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=87zghpm58r.fsf@localhost \
--to=yantar92@gmail.com \
--cc=andras.simonyi@gmail.com \
--cc=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).