From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: set different colors for different link types Date: Sat, 30 Apr 2011 09:55:28 +0530 Message-ID: <81mxj89xhj.fsf@gmail.com> References: <4DBA7A0B.8@gmail.com> <4DBB4C73.9020803@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:57764) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QG1kc-0003oT-3y for emacs-orgmode@gnu.org; Sat, 30 Apr 2011 00:25:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QG1kb-00036l-6Q for emacs-orgmode@gnu.org; Sat, 30 Apr 2011 00:25:50 -0400 Received: from mail-pv0-f169.google.com ([74.125.83.169]:48218) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QG1ka-00036Z-Ur for emacs-orgmode@gnu.org; Sat, 30 Apr 2011 00:25:49 -0400 Received: by pvc12 with SMTP id 12so3584740pvc.0 for ; Fri, 29 Apr 2011 21:25:48 -0700 (PDT) In-Reply-To: <4DBB4C73.9020803@gmail.com> (Christian Wittern's message of "Sat, 30 Apr 2011 08:40:35 +0900") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Christian Wittern Cc: Org Mode Mailing List > Hi Michael, > > Thank you for your suggestion. However, I would prefer not to clutter > the text with repeating the protocol there. Also, the example I gave > is mainly for illustration, in the way I use it, the description would > not show the filename, but some other text. > > Chris > > On 2011-04-30 00:18, Michael Brand wrote: >> For links with a description I always just repeat the protocol tag >> there manually: >> [[file://path/to/my file][file: myfile]] >> [[http://www.example.com/path/to/my file][http: myfile]] >> >> Together with the space after the colon this shows, also immediately, >> if you look only at the link description or at the link itself: >> [[file://path/to/my file]] >> [[http://www.example.com/path/to/my file]] >> >> This color-independent solution works even if colors would not be >> available occasionally like with some terminal configs. >> >> Michael >> >> 2011/4/29 Christian Wittern: >>> In the archives, I have seen on and off references to a new, extensible >>> syntax that would go beyond /italic/, *bold* and =code=, but I have seen no >>> traces of seeing it implemented. >>> >>> For the time being, therefore I am settling on having different linktypes >>> coming up in different colors, which I hope is doable, but again, I found no >>> immediate solution. I wonder if somebody has an idea of how to go about >>> this. What I would like to see is that, for example: >>> >>> [[file://path/to/my file][myfile]] comes out visibly different from >>> [[http://www.example.com/path/to/my file][myfile]] , for example the one in >>> red, the other in blue. The easiest way to figure out the protocol is to "pretend" that you are editing the link and thereby have the curtain raised a bit to reveal the backstage. Do a C-c C-l or M-x org-insert-link RET (with cursor right over the link) followed by 'C-g'ing. If you are willing to hack something together, here is a possible entry points for attack. With M-x highlight-regexp you could add persistent regexp patterns for fontification. 1. Do a M-x describe-text-properties RET on a link to see what is under the hood. For example in one of my links I see --8<---------------cut here---------------start------------->8--- Text content at position 509: There are text properties here: face org-link font-lock-multiline t fontified t help-echo "LINK: file:src/org-jambu/lisp/org-odt.el" keymap [Show] mouse-face highlight org-no-flyspell t --8<---------------cut here---------------end--------------->8--- 2. Start with org-descriptive-links set to nil (makes all components of link visible) 3. Start with org-bracket-link-analytic-regexp as a starting regexp which needs to be fine grained into say web urls, file urls etc etc 4. See org-activate-bracket-links for ideas on how org accomplishes highlighting correctly. C-h hi-lock-mode C-h f highlight-regexp C-h v hi-lock-file-patterns-policy C-h v org-descriptive-links C-h v org-angle-link-re C-h v org-bracket-link-regexp C-h v org-bracket-link-analytic-regexp C-h f org-activate- (look for functions like org-activate-bracket-links etc) Jambunathan K. --