From: Thien-Thi Nguyen <ttn@glug.org>
Cc: guile-user@gnu.org
Subject: Re: PLEASE: debugging embedded guile code
Date: Sat, 26 Apr 2003 18:25:39 -0400 [thread overview]
Message-ID: <E199Y71-0004U1-00@colo.agora-net.com> (raw)
In-Reply-To: <3EAAE877.7140ECB6@veritas.com> (message from Bruce Korb on Sat, 26 Apr 2003 13:13:43 -0700)
From: Bruce Korb <bkorb@veritas.com>
Date: Sat, 26 Apr 2003 13:13:43 -0700
It's also hard to read
dark blue on a black background (glug page).
i confess as a w3m user (on console) i don't really test www.glug.org
for color correctness / image placement / anything graphical, before
deployment -- sometimes it's more fun to generate stuff than to look at
what's generated, eh? :-)
anyway, a simple find-grep on www.glug.org shows "bgcolor" black on a
few pages, for which there is no corresponding "fgcolor" blue. however,
i see there is no explicit {un}visited link color specification, clearly
a bug. thanks for the tip. i've manually jammed
link = "yellow" alink = "yellow" vlink = "green"
in the live index.html body tag for now; still waiting for an
opportunity to revive the hard drive on which rests source for that
page, to do a proper regen from http://www.glug.org/index.laml (and
do other maintenance).
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-04-26 22:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 11:12 Source locations Joris van der Hoeven
2003-02-08 17:22 ` Wolfgang Jaehrling
2003-02-09 19:05 ` Joris van der Hoeven
2003-02-25 14:19 ` PLEASE: debugging embedded guile code Joris van der Hoeven
2003-02-25 14:36 ` Dale P. Smith
2003-02-27 12:17 ` Customized error reports Joris van der Hoeven
2003-02-28 18:06 ` Paul Jarc
2003-04-26 14:51 ` PLEASE: debugging embedded guile code Neil Jerram
2003-04-26 16:40 ` Bruce Korb
2003-04-26 19:12 ` Neil Jerram
2003-04-26 20:13 ` Bruce Korb
2003-04-26 22:25 ` Thien-Thi Nguyen [this message]
2003-04-27 20:49 ` Neil Jerram
2003-04-27 21:57 ` Bruce Korb
2003-04-28 15:54 ` Paul Jarc
2003-04-28 16:07 ` Bruce Korb
2003-04-28 19:21 ` Neil Jerram
2003-04-28 20:06 ` Bruce Korb
2003-04-28 20:58 ` Neil Jerram
2003-05-16 17:19 ` Bruce Korb
2003-05-16 19:23 ` Neil Jerram
2003-05-16 20:27 ` Bruce Korb
2003-05-16 21:21 ` Rob Browning
2003-05-16 21:56 ` Bruce Korb
2003-05-17 0:31 ` Bruce Korb
2003-05-17 2:33 ` Bruce Korb
2003-05-19 15:00 ` Paul Jarc
2003-04-28 13:52 ` Mikael Djurfeldt
2003-04-28 19:26 ` Neil Jerram
2003-04-26 14:45 ` Neil Jerram
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E199Y71-0004U1-00@colo.agora-net.com \
--to=ttn@glug.org \
--cc=guile-user@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.
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).