From: Juri Linkov <juri@linkov.net>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 59243@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#59243: 28.2.50; Larger Fringe Bitmaps
Date: Sun, 13 Nov 2022 19:49:48 +0200 [thread overview]
Message-ID: <865yfidapf.fsf@mail.linkov.net> (raw)
In-Reply-To: <9fc85987-cc78-2f9b-60e1-b893dbe9b848@daniel-mendler.de> (Daniel Mendler's message of "Sun, 13 Nov 2022 11:08:19 +0100")
> Please consider the fringe bitmaps I've defined in bigger-fringe.el.
> This is a cheap change which nevertheless should increase
> accessibility a little bit. I override the bitmaps defined in
> fringe.c, flymake.el, diff.el and diff-hl.el. The file
> bigger-fringe.el contains the command `fringe-bitmap-test', which
> I've used to create a screenshot of the updated fringe bitmaps. I've
> attached the screenshot for comparison.
Oh, I have the opposite problem: the default fringe bitmaps are too big
for my font size. So I have to use smaller versions:
(define-fringe-bitmap 'light-down-arrow [32 32 32 32 32 32 168 112 32] nil nil 'bottom)
(define-fringe-bitmap 'light-up-arrow [32 112 168 32 32 32 32 32 32] nil nil 'top)
(define-fringe-bitmap 'light-top-left-angle [254 254 128 128 128] nil nil 'top)
(define-fringe-bitmap 'light-bottom-left-angle [128 128 128 254 254] nil nil 'bottom)
(define-fringe-bitmap 'light-left-bracket [254 254 128 128 128 0 0 0 0 128 128 128 254 254] nil nil 'center)
(define-fringe-bitmap 'light-right-curly-arrow [96 16 8 8 72 80 96 120] nil nil 'bottom)
(define-fringe-bitmap 'light-left-curly-arrow [8 16 16 16 18 10 6 30] nil nil 'top)
(define-fringe-bitmap 'light-right-arrow [16 8 252 8 16] nil 11 'center)
(define-fringe-bitmap 'light-left-arrow [32 64 254 64 32] nil nil 'center)
(setq-default fringe-indicator-alist
'((truncation . (light-left-arrow light-right-arrow))
(continuation . (light-left-curly-arrow light-right-curly-arrow))
(overlay-arrow . right-triangle)
(up . light-up-arrow)
(down . light-down-arrow)
(top . (light-top-left-angle top-right-angle))
(bottom . (light-bottom-left-angle bottom-right-angle
top-right-angle light-top-left-angle))
(top-bottom . (light-left-bracket right-bracket
top-right-angle light-top-left-angle))
(empty-line . empty-line)
(unknown . question-mark)))
Maybe a new customizable option could allow to select from different sets
of bitmaps with such labels as "Large", "Medium", "Small".
next prev parent reply other threads:[~2022-11-13 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 10:08 bug#59243: 28.2.50; Larger Fringe Bitmaps Daniel Mendler
2022-11-13 11:47 ` Eli Zaretskii
2022-11-13 13:08 ` Daniel Mendler
2022-11-13 13:48 ` Eli Zaretskii
2022-11-13 17:49 ` Juri Linkov [this message]
2022-11-13 18:17 ` Eli Zaretskii
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=865yfidapf.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=59243@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=mail@daniel-mendler.de \
/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).