From: Michael Brand <michael.ch.brand@gmail.com>
To: Christian Wittern <cwittern@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: set different colors for different link types
Date: Fri, 29 Apr 2011 17:18:52 +0200 [thread overview]
Message-ID: <BANLkTikc0XKROQhjPSY_FMzNvQCVdVJUeA@mail.gmail.com> (raw)
In-Reply-To: <4DBA7A0B.8@gmail.com>
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 <cwittern@gmail.com>:
> 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.
next prev parent reply other threads:[~2011-04-29 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 8:42 set different colors for different link types Christian Wittern
2011-04-29 15:18 ` Michael Brand [this message]
2011-04-29 23:40 ` Christian Wittern
2011-04-30 4:25 ` Jambunathan K
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=BANLkTikc0XKROQhjPSY_FMzNvQCVdVJUeA@mail.gmail.com \
--to=michael.ch.brand@gmail.com \
--cc=cwittern@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).