From: Bastien <bzg@altern.org>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: css link colors for Worg are difficult to spot
Date: Wed, 03 Apr 2013 11:45:24 +0200 [thread overview]
Message-ID: <87fvz8uevf.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CA+M2ft-vJCDE5doa39OKzpmgxAakYeetBnWeYYZz=i9MZFbMmA@mail.gmail.com> (John Hendy's message of "Mon, 1 Apr 2013 08:14:12 -0500")
Hi John,
John Hendy <jw.hendy@gmail.com> writes:
> I find the links difficult to spot in Worg sometimes, especially
> depending on monitor angle and current brightness setting. Is this an
> issue for anyone else?
Yes, it is for me too.
> I fiddled around in /style/worg.css a bit and didn't land on anything
> too great. I'm wondering if anyone with a design background might have
> suggestions for link colors? I guess if no one else is affected by
> this... I'll just deal with it and mine sweep wildly with my mouse
> when I think a link should be in there somewhere :)
Even if that's not great, something *better* would be nice already.
The difficult part is to stick to the colors of the Unicorn while
making the link more readable -- if you can enhance this, the change
will be welcome.
Thanks,
--
Bastien
next prev parent reply other threads:[~2013-04-03 9:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 13:14 css link colors for Worg are difficult to spot John Hendy
2013-04-03 9:45 ` Bastien [this message]
2013-04-03 10:20 ` Christian Moe
2013-04-03 10:47 ` Vincent Beffara
2013-04-03 10:57 ` Bastien
2013-04-04 0:05 ` John Hendy
2013-04-04 9:56 ` Bastien
2013-04-04 7:40 ` Achim Gratz
2013-04-05 23:11 ` Bastien
2013-04-06 8:23 ` Alexander Poslavsky
2013-04-06 8:28 ` Gmane orgmode down? Bastien
2013-04-06 8:46 ` Christian Moe
2013-04-06 9:35 ` Bastien
2013-04-06 17:53 ` css link colors for Worg are difficult to spot John Hendy
2013-04-06 17:59 ` Bastien
2013-04-15 19:55 ` John Hendy
2013-04-16 6:28 ` 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
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=87fvz8uevf.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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).