emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: stardiviner <numbchild@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [QUESTION] Org "customid" and "coderef" links seems not fontified as other file: link
Date: Sat, 23 May 2020 09:16:59 +0800	[thread overview]
Message-ID: <875zcnbgc4.fsf@gmail.com> (raw)
In-Reply-To: <87h7w8dmh7.fsf@nicolasgoaziou.fr>

Hash: SHA256

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

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

That's a good solution, will be simple for future links manipulation.

> Help welcome.

Sure, anything I can help you can say.

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

I read the function `org-activate-links' source code, I guess you mean I can
advice on the `properties' let-binding variable. Add `'display' text property,
right? I don't know how to add advice for this functionality. Do you have any
sample code for hinting? I will be much thankful.


- -- 
[ stardiviner ]
       I try to make every word tell the meaning that I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


  reply	other threads:[~2020-05-23  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  0:38 stardiviner
2020-05-22 15:21 ` Nicolas Goaziou
2020-05-23  1:16   ` stardiviner [this message]
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:

  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=875zcnbgc4.fsf@gmail.com \
    --to=numbchild@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --subject='Re: [QUESTION] Org "customid" and "coderef" links seems not fontified as other file: link' \


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