Re: Problem with custom links

[Thomas S. Dye]

Aloha Kyle,

Thanks for taking a look at this, and also for the instructions 
how to test.  I get the results you report.

Separately, off list, John Kitchin kindly noted that my symptoms 
might be caused by org-ref.  A bit of snooping led me to 
understand that org-ref was installed on my system as a dependency 
of emacs-reveal, so the mystery is solved.

I'm happy using the two new keywords; they seem to protect my 
setup from being changed by org-ref.

All the best,
Tom


Kyle Meyer writes:

> Thomas S. Dye writes:
>
> > 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"
> [...]
> >    :display 'org-link
> >    :face 'org-link)
>
> I tried this snippet, dropping the :display and :face arguments
>
>   (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))))))
>
> with the following buffer:
>
>   [[parencite:foo][bar]]
>
> With an otherwise default configuration and the current master
> (49364f904), the link gets fontified with the org-link face and
> displayed as just "bar".  So, that seems to be behaving as 
> expected and
> I don't spot any relevant code change to the handling of the 
> defaults in
> org-activate-links.
>
> Have you tried to trigger it without any additional 
> configuration?


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