emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: org-cite styles don't allow * in them
Date: Mon, 18 Apr 2022 06:25:33 -0400	[thread overview]
Message-ID: <CAF-FPGODEyok=tBWH4NEXoqqSZYmd8Jbpzmw0Z+83zp594jD7w@mail.gmail.com> (raw)
In-Reply-To: <87a6ciyd02.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

On Mon, Apr 18, 2022, 5:08 AM Ihor Radchenko <yantar92@gmail.com> wrote:

> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> >> In contrast, [cite/citet*:@key] is likely to be used fairly frequently
> >> and has much higher chance to break things.
> >
> >
> > We have had a citet*:key link (and all the other * variants) for a long
> > time in org-ref, with no reported issues I can recall.
>
> I respect your experience in this regard. If the discussed issue is
> uncommon in practice, we may simply provide citet* and similar styles +
> fallback citet*/ as an alias. The citet* will be the default while
> citet*/ may be suggested, say, by org-lint if we add a new checker for
> this.
>

Just to clarify, I don't believe the discussion is to add such styles to
the included org-cite processors (which already support such
functionality), but rather to allow it, for example for third party ones;
say a hypothetical org-ref one.

Bruce



> P.S. Thinking more about org-lint, I imagine that it could be a good
> practice to run org-lint before every export. For example, it can save
> people from a common problem with handling broken links during export.
>
> Best,
> Ihor
>

[-- Attachment #2: Type: text/html, Size: 1941 bytes --]

  reply	other threads:[~2022-04-18 10:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 21:06 org-cite styles don't allow * in them John Kitchin
2022-04-05 15:56 ` Bruce D'Arcus
2022-04-05 16:11   ` John Kitchin
2022-04-05 17:41     ` Bruce D'Arcus
2022-04-07  4:17   ` Ihor Radchenko
2022-04-07 11:30     ` John Kitchin
2022-04-16 16:29       ` Bruce D'Arcus
2022-04-17  8:42         ` Ihor Radchenko
2022-04-17 12:14           ` John Kitchin
2022-04-17 13:18             ` Ihor Radchenko
2022-04-17 14:24               ` John Kitchin
2022-04-18  9:09                 ` Ihor Radchenko
2022-04-18 10:25                   ` Bruce D'Arcus [this message]
2022-04-19  2:59                     ` Ihor Radchenko
2022-04-21  8:06     ` Nicolas Goaziou
2022-04-21 10:09       ` Ihor Radchenko
2022-04-21 11:28         ` Nicolas Goaziou
2022-04-21 13:40           ` Ihor Radchenko
2022-04-22 12:42       ` Bruce D'Arcus
2022-04-22 13:30         ` John Kitchin
2022-05-22 15:51       ` 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

  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='CAF-FPGODEyok=tBWH4NEXoqqSZYmd8Jbpzmw0Z+83zp594jD7w@mail.gmail.com' \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=yantar92@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 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).