From: Gregory Heytings <gregory@heytings.org>
To: 47832@debbugs.gnu.org
Subject: bug#47832: 28.0.50; define-fringe-bitmap and emacs --daemon
Date: Fri, 16 Apr 2021 22:22:35 +0000 [thread overview]
Message-ID: <7dee3f4235cf450a3254@heytings.org> (raw)
When the init file contains define-fringe-bitmap that override default
fringe bitmaps, they are ignored by Emacs when it is started as a daemon.
This has stopped working at commit 88efc736f5, when Cairo became the
default backend.
How to reproduce:
1. create a ~/.emacs file with:
(define-fringe-bitmap 'empty-line [ #xff ] nil nil '(top t))
(setq-default indicate-empty-lines t)
2. emacs ~/.emacs => the empty lines fringe bitmaps are displayed
correctly, with a solid black column.
3. emacs --daemon
4. emacsclient -c ~/.emacs => the empty line fringe bitmaps are the
default ones, which are 4x1 pixel horizontal black lines.
When the init file contains define-fringe-bitmap that do _not_ override
default fringe bitmaps however, they are not ignored. For example with
(define-fringe-bitmap 'solid [ #xff ] nil nil '(top t))
the "solid" fringe bitmap can be used in frames created by emacsclient -c.
next reply other threads:[~2021-04-16 22:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 22:22 Gregory Heytings [this message]
2021-04-17 6:49 ` bug#47832: 28.0.50; define-fringe-bitmap and emacs --daemon Eli Zaretskii
2021-04-17 9:49 ` Gregory Heytings
2021-04-17 10:57 ` Eli Zaretskii
2021-04-17 11:21 ` Eli Zaretskii
2021-04-17 11:32 ` Gregory Heytings
2021-04-17 12:27 ` Eli Zaretskii
2021-04-17 12:52 ` Gregory Heytings
2021-05-25 4:21 ` Lars Ingebrigtsen
2021-05-25 11:55 ` Eli Zaretskii
2021-05-25 12:44 ` Gregory Heytings
2021-05-25 12:56 ` Eli Zaretskii
2021-05-25 13:03 ` Gregory Heytings
2021-05-25 13:15 ` Eli Zaretskii
2021-05-25 13:24 ` Gregory Heytings
2021-05-25 13:45 ` Eli Zaretskii
2021-05-26 13:27 ` Eli Zaretskii
2021-05-27 7:32 ` Gregory Heytings
2021-05-27 9:35 ` Eli Zaretskii
2021-04-17 11:34 ` Gregory Heytings
2021-04-17 12:28 ` Eli Zaretskii
2021-04-17 11:27 ` Gregory Heytings
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=7dee3f4235cf450a3254@heytings.org \
--to=gregory@heytings.org \
--cc=47832@debbugs.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).