emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: stardiviner <numbchild@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [QUESTION] Org "customid" and "coderef" links seems not fontified as other file: link
Date: Fri, 22 May 2020 17:21:24 +0200	[thread overview]
Message-ID: <87h7w8dmh7.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87imgoregv.fsf@gmail.com> (stardiviner's message of "Fri, 22 May 2020 08:38:24 +0800")

Hello,

stardiviner <numbchild@gmail.com> writes:

> I have following minimal testing code:
>
> #+begin_src emacs-lisp
> (defun org-link-beautify (start end path bracketp)
>   "Display icon for the Org link type."
>   (message
>    (format "start: %s, end: %s, path: %s, bracketp: %s" start end path bracketp)))
>
> (dolist (link-type (mapcar 'car org-link-parameters))
>     (org-link-set-parameters link-type :activate-func #'org-link-beautify))
> #+end_src
>
> The ~message~ does not print parameter values at all. I guess those "customid"
> [[#Usage] and "coderef" (coderef) are different with "file:" etc links. Is this
> true? Here is my complete source code I want to try fontify customid and coderef
> links.
>
> https://github.com/stardiviner/org-link-beautify/blob/master/org-link-beautify.el#L67
>
> Is there any way to fix this problem?

[[#cusom]], [[*headline]], [[(coderef)]] or, simply [[target]], are
internal links, with a special syntax. In particular, they do not go
through the `org-link-parameters' process.

We could integrate them in that variable, i.e., extract the "follow"
function from `org-link-open', handle completion, storage, with
dedicated functions, etc.

Help welcome.

Meanwhile, your best bet is to defadvice `org-activate-links'.

Regards,

-- 
Nicolas Goaziou


  reply	other threads:[~2020-05-22 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  0:38 [QUESTION] Org "customid" and "coderef" links seems not fontified as other file: link stardiviner
2020-05-22 15:21 ` Nicolas Goaziou [this message]
2020-05-23  1:16   ` stardiviner
2020-12-23  2:48 ` stardiviner
2021-01-04 18:20   ` Nicolas Goaziou
2021-01-05  4:37     ` miles christopher

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=87h7w8dmh7.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=numbchild@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).