emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: overlap between cite syntax and link activation
Date: Sun, 3 Apr 2022 19:44:54 -0400	[thread overview]
Message-ID: <CAJ51ETo_cNn-oEWakGJk3LUKqgnw=QvBLcco=iZaBcG8b3kdJQ@mail.gmail.com> (raw)

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

I think there is some overlap between the org-cite syntax and org-link

Consider this org-cite:


Now define this link:

#+BEGIN_SRC emacs-lisp
(org-link-set-parameters "bare"
:help-echo "BARE LINK"
:activate-func (lambda (start end path _bracketp)
 (message-box "%S activating bare" (list start end path))
 (put-text-property start
    'face '(:foreground "OrangeRed1"))))


When I put my cursor on the org-cite line and press spc, I see a message
box pop up, and the @key has a tooltip of "BARE LINK".

I guess this means the activate-func is being used too aggressively. It
looks like it is called after (re-search-forward org-link-any-re limit t).
This does seem to match the cite syntax above.

Does anyone else see this?


Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213

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

             reply	other threads:[~2022-04-03 23:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 23:44 John Kitchin [this message]
2022-04-04  0:55 ` Bruce D'Arcus
2022-04-22 12:47   ` Bruce D'Arcus
2022-04-22 17:10     ` Nicolas Goaziou
2022-04-24  7:19       ` Ihor Radchenko
2022-04-24  9:03         ` Nicolas Goaziou

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:

  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='CAJ51ETo_cNn-oEWakGJk3LUKqgnw=QvBLcco=iZaBcG8b3kdJQ@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \


* 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


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).