From: storm@cua.dk (Kim F. Storm)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Jason Rumney <jasonr@gnu.org>
Subject: Re: Alternative fringe bitmaps for continuation/truncation
Date: Mon, 28 Apr 2008 12:18:36 +0200 [thread overview]
Message-ID: <87abjegu4j.fsf@kfs-lx.rd.rdm> (raw)
In-Reply-To: <jwv7ieiiqe2.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon\, 28 Apr 2008 00\:03\:31 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> If you don't like the current "fat (curly) arrows" bitmaps used in the
>>> fringe for continuation and truncation lines, the following more
>>> modest bitmaps may be more appealing.
>>>
>> I think they are likely to invite bug reports about corrupted display if we
>> make them the default.
> I'd tend to agree, although I must say that with the half-width fringes
> I use, these continuation icons look better than the slightly truncated
> arrows (because my fringes aren't wide enough).
For the continuation bitmaps I don't expect such bug reports -
the ... idiom is quite well-known, and the curly arrows are so
much in your face that I suppose many users dislike them.
> I'm not convinced by the truncation icons, tho.
I agree that they are a bit too cryptic for general acceptance.
I think these are much better:
(define-fringe-bitmap 'right-truncation
"\x04\x02\xa9\x02\x04" nil nil 'bottom)
(define-fringe-bitmap 'left-truncation
"\x20\x40\xaa\x40\x20" nil nil 'bottom)
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2008-04-28 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 16:59 Alternative fringe bitmaps for continuation/truncation Kim F. Storm
2008-04-27 21:02 ` Jason Rumney
2008-04-28 4:03 ` Stefan Monnier
2008-04-28 10:18 ` Kim F. Storm [this message]
2008-04-28 10:53 ` Jason Rumney
2008-04-28 15:00 ` Stefan Monnier
2008-04-28 17:38 ` Kim F. Storm
2008-04-28 17:50 ` Jason Rumney
2008-04-28 22:01 ` Kim F. Storm
2008-05-02 23:48 ` Juri Linkov
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=87abjegu4j.fsf@kfs-lx.rd.rdm \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).