From: Bastien <bzg@altern.org>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: Emacs Org mode <emacs-orgmode@gnu.org>
Subject: Re: Link colours in new Worg style
Date: Fri, 08 Mar 2013 18:24:12 +0100 [thread overview]
Message-ID: <87y5dxztxf.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20130308140522.GF13199@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Fri, 8 Mar 2013 15:05:22 +0100")
Hi Suvayu,
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> The new Worg style is amazing; the text is very clear and much more
> readable now. However I have a major complaint about the links. It
> seems the new style overrides my browser's colour setting for unvisited
> and visited links. I think this is extremely confusing. As per my
> setting, I have blue for unvisited links and purple for visited links.
> The new style overrides this to red for unvisited and blue for visited.
> Obviously you can see how this leads to a confusion. I would really
> appreciate it if this was left to the user and not determined by the
> webpage.
The previous stylesheet already used non-default colors for
non-visited and visited links. I just changed the colors.
Here is the setting you saw:
a {text-decoration: none; color: #FF0000; font-weight: 400;}
a:visited {text-decoration: none; color: #0066CC; font-weight: 400;}
a:hover {text-decoration: underline; color: #FF0000}
But you're right this is confusing, as this is the exact opposite
of... most browsers default settings. I swaped the color, let me
know if this looks better.
PS: The Unicorn-on-steroid logo will change, I'm waiting for my
friend to submit a new one. Perhaps the colors will change a bit
too.
--
Bastien
next prev parent reply other threads:[~2013-03-08 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 14:05 Link colours in new Worg style Suvayu Ali
2013-03-08 17:24 ` Bastien [this message]
2013-03-08 18:05 ` Suvayu Ali
2013-03-09 10:06 ` Bastien
2013-03-09 11:36 ` Achim Gratz
2013-03-09 11:40 ` Bastien
2013-03-09 13:05 ` Bastien
2013-03-09 14:17 ` Carsten Dominik
2013-03-09 14:25 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5dxztxf.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.