From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, storm@cua.dk
Subject: Re: default-indicate-buffer-boundaries
Date: Sat, 4 Feb 2006 09:33:52 +0900 [thread overview]
Message-ID: <fc339e4a0602031633h6d6c0a83x@mail.gmail.com> (raw)
In-Reply-To: <200602031820.k13IKXQ12242@raven.dms.auburn.edu>
2006/2/4, Luc Teirlinck <teirllm@dms.auburn.edu>:
> I believe that Miles, the only person complaining about them
> being "too much in your face" uses a non-default fringe background color.
Yes.
[It's not uncommon that various emacs defaults which look OK on a
light background look a bit crappy on a dark background.]
-miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2006-02-04 0:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 18:06 default-indicate-buffer-boundaries Richard M. Stallman
2006-01-31 19:25 ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-01 19:40 ` default-indicate-buffer-boundaries Richard M. Stallman
2006-02-02 0:00 ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-03 5:05 ` default-indicate-buffer-boundaries Richard M. Stallman
2006-02-03 5:16 ` default-indicate-buffer-boundaries Miles Bader
2006-02-03 9:12 ` default-indicate-buffer-boundaries Kim F. Storm
2006-02-04 18:25 ` default-indicate-buffer-boundaries Richard M. Stallman
2006-02-03 9:10 ` default-indicate-buffer-boundaries Kim F. Storm
2006-02-03 18:20 ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-04 0:33 ` Miles Bader [this message]
2006-02-04 12:19 ` default-indicate-buffer-boundaries Robert J. Chassell
2006-02-05 0:57 ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-06 7:52 ` default-indicate-buffer-boundaries Juri Linkov
2006-02-01 23:37 ` default-indicate-buffer-boundaries Kim F. Storm
2006-02-02 1:46 ` default-indicate-buffer-boundaries Miles Bader
2006-02-02 2:29 ` default-indicate-buffer-boundaries Luc Teirlinck
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=fc339e4a0602031633h6d6c0a83x@mail.gmail.com \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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.