emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Thomas S. Dye" <tsd@tsdye.online>
To: "emacs-orgmode\@gnu.org" <emacs-orgmode@gnu.org>
Subject: Problem with custom links
Date: Mon, 08 Feb 2021 14:31:09 -1000	[thread overview]
Message-ID: <87k0ri2ib6.fsf@tsdye.online> (raw)

Aloha all,

Recently, custom links that I've used for years changed their 
behavior.  They used to behave like other org mode links, but now 
they are displayed in a different color face and are always fully 
displayed, unless I add two new keywords to 
org-link-set-parameters.

  (org-link-set-parameters
   "parencite"
   :follow 'org-ebib-open
   :export (lambda (path desc format)
             (cond
              ((eq format 'html)
               (format "(<cite>%s</cite>)" path))
              ((eq format 'latex)
               (if (or (not desc) (equal 0 (search "parencite:" 
               desc)))
                   (format "\\parencite{%s}" path)
                 (format "\\parencite[%s][%s]{%s}"
                         (cadr (split-string desc ";"))
                         (car (split-string desc ";")) path)))))
   :display 'org-link
   :face 'org-link)

I added the :display and :face keywords after I stumbled upon a 
list of defined links (which I wish I'd noted because I haven't 
found it since) that indicated that :display was set to 'full 
(which confused me because I'd read that the default was supposed 
to be 'org-link).  Adding these two keywords restores the original 
behavior for me.

I'm wondering why I have to set these keywords to get the default 
behavior?

I did search ORG-NEWS for a relevant entry, but didn't see 
anything that rang a bell.

I hope you and yours are well in the face of the pandemic.

Let me know if you have questions.

All the best,
Tom

--
Thomas S. Dye
https://tsdye.online/tsdye

next             reply	other threads:[~2021-02-09  0:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  0:31 Thomas S. Dye [this message]
2021-02-12  5:16 ` Problem with custom links Kyle Meyer
2021-02-12 23:05   ` Thomas S. Dye

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=87k0ri2ib6.fsf@tsdye.online \
    --to=tsd@tsdye.online \
    --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

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