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: Mon, 04 Jan 2021 19:20:01 +0100 [thread overview]
Message-ID: <87lfd8a7ji.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <5fe3461a.1c69fb81.f26ce.16e0@mx.google.com> (stardiviner's message of "Wed, 23 Dec 2020 10:48:52 +0800")
Hello,
stardiviner <numbchild@gmail.com> writes:
> Bump this thread, hi, Nicolas, any thoughts or update about this?
>
> 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?
That's correct. coderef, customid, and fuzzy links are internal links.
They are not really customizable. They are meant to behave the same in
all Org documents.
>> 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?
Coderef and custom-id links are fontified, so you may still change their
appearance using font-lock configuration variables. Here be dragons.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-01-04 18:21 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
2020-05-23 1:16 ` stardiviner
2020-12-23 2:48 ` stardiviner
2021-01-04 18:20 ` Nicolas Goaziou [this message]
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=87lfd8a7ji.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).