unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: fringe buffer-boundary bitmaps
Date: Thu, 23 Jun 2005 00:48:05 +0200	[thread overview]
Message-ID: <m3hdfqrot6.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <buofyvahpmo.fsf@mctpc71.ucom.lsi.nec.co.jp> (Miles Bader's message of "Wed, 22 Jun 2005 15:28:15 +0900")

Miles Bader <miles@lsi.nec.co.jp> writes:

> Also, here are some alternate versions of the fringe line-wrapping
> indicator bitmaps:
>
> (define-fringe-bitmap 'continued-line [96 16 8 8 72 80 96 120] nil nil 'bottom)
> (define-fringe-bitmap 'continuation-line [8 16 16 16 18 10 6 30] nil nil 'top)
>
> These are lighter-weight than the current defaults, so maybe more
> controversial, but I like them a lot better.

They are quite nice, yes.  And contrary to the current bitmaps, they
actually look like arrows...

But if we change these, then probably we should change all the bitmaps
to a lighter version...

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  parent reply	other threads:[~2005-06-22 22:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22  0:51 fringe buffer-boundary bitmaps Miles Bader
2005-06-22  6:28 ` Miles Bader
2005-06-22  7:28   ` Miles Bader
2005-06-22 22:52     ` Kim F. Storm
2005-06-22 12:49   ` Robert J. Chassell
2005-06-23  0:19     ` Miles Bader
2005-06-23  7:45       ` Kim F. Storm
2005-06-23  8:05         ` Miles Bader
2005-06-23 21:14       ` Robert J. Chassell
2005-06-24  5:35       ` Richard M. Stallman
2005-06-22 22:48   ` Kim F. Storm [this message]
2005-06-22 15:42 ` Richard M. Stallman
2005-06-23  8:03   ` Kim F. Storm
2005-06-24  5:36     ` Richard M. Stallman
2005-06-24  8:37       ` Kim F. Storm
2005-06-25  0:31         ` Richard M. Stallman
2006-02-20 22:38           ` Kim F. Storm
2006-02-21  6:44             ` Miles Bader
2006-02-21 11:12             ` Giorgos Keramidas
2006-02-21 11:40               ` Kim F. Storm
2006-02-21 12:21                 ` Giorgos Keramidas
2006-02-21 14:55             ` Chong Yidong
2006-02-22  5:24             ` Richard M. Stallman
2006-02-23 23:45             ` Juri Linkov
2006-02-24 13:45               ` Kim F. Storm
2006-02-24 23:27                 ` Juri Linkov
2006-02-24 19:40               ` Richard Stallman
2005-06-22 19:03 ` Markus Gritsch
2005-06-22 22:43 ` Kim F. Storm
2005-06-23  9:53 ` Lute Kamstra
2005-06-23 10:08   ` Miles Bader
2005-06-23 12:18     ` Lute Kamstra
2005-06-23 13:49     ` Juanma Barranquero
2005-06-23 13:59       ` Juanma Barranquero
2005-06-23 15:15         ` Luc Teirlinck
2005-06-23 15:35           ` Juanma Barranquero
2005-06-23 18:20             ` Luc Teirlinck
2005-06-23 22:15               ` Juanma Barranquero
2005-06-24 14:12               ` Stefan Monnier
2005-06-23 15:23         ` Luc Teirlinck
2005-06-24  5:36     ` Richard M. Stallman

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3hdfqrot6.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@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.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).