emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
	Bruce D'Arcus <bdarcus@gmail.com>
Subject: Re: org-cite styles don't allow * in them
Date: Sun, 17 Apr 2022 10:24:00 -0400	[thread overview]
Message-ID: <CAJ51ETpZK_+QvjsSvAdVnVwP2npdQjA2MoPO6=zmSUqrs7wp-w@mail.gmail.com> (raw)
In-Reply-To: <87h76rj1a7.fsf@localhost>

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

On Sun, Apr 17, 2022 at 9:18 AM Ihor Radchenko <yantar92@gmail.com> wrote:

> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > I am also not a fan of using Unicode here and prefer a simple ascii
> > asterisk. That works fine for me so far, but I am not a heavy user of
> bold
> > markup and citations.
>
> What about something like [cite/citet*/:@key]?
> "*/" is not recognised as bold ending.


That is a great solution when you want to have bold, and it would be
optional if you don’t use bold there.  You still would need to add * to the
cite pattern.

>

>
> > As I mentioned there is the same problem for links, and in the last 10
> > years I can’t recall an issue being reported with bold.
>
> This is because links containing "\\*[ -.,;:!?'")}\\[]" match are
> extremely rare.
>
> 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.


>
> Best,
> Ihor
>
> --
John

-----------------------------------
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

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

  reply	other threads:[~2022-04-17 14:24 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 [this message]
2022-04-18  9:09                 ` Ihor Radchenko
2022-04-18 10:25                   ` Bruce D'Arcus
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='CAJ51ETpZK_+QvjsSvAdVnVwP2npdQjA2MoPO6=zmSUqrs7wp-w@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --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).