From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 39662@debbugs.gnu.org, rpluim@gmail.com, thibault@thb.lt
Subject: bug#39662: 28.0.50; Emacs crashes in x_cr_define_fringe_bitmap if (fringe-mode 0)
Date: Wed, 19 Feb 2020 05:27:07 +0200 [thread overview]
Message-ID: <83k14jl0j8.fsf@gnu.org> (raw)
In-Reply-To: <8c68006d-54b5-7fd5-128a-c253b4899cde@yandex.ru> (message from Dmitry Gutov on Tue, 18 Feb 2020 22:29:02 +0200)
> Cc: thibault@thb.lt, 39662@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 18 Feb 2020 22:29:02 +0200
>
> On 18.02.2020 22:12, Eli Zaretskii wrote:
> >> But itʼs friendlier to existing code to change 0 to 1, no?
> > Yes.
>
> Speaking of diff-hl, signaling an error would probably be more
> constructive since if the call succeeds, the user might turn on
> fringe-mode and find that all bitmaps defined by diff-hl are 1-pixel
> wide for no apparent reason.
I thought in the scenario we are discussing there will be no bitmaps
shown at all, since the scenario disables the fringes. Isn't that so?
next prev parent reply other threads:[~2020-02-19 3:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 15:06 bug#39662: 28.0.50; Emacs crashes in x_cr_define_fringe_bitmap if (fringe-mode 0) Thibault Polge
2020-02-18 15:45 ` Robert Pluim
2020-02-18 16:54 ` Thibault Polge
2020-02-18 19:32 ` Robert Pluim
2020-02-18 19:50 ` Eli Zaretskii
2020-02-18 20:03 ` Robert Pluim
2020-02-18 20:12 ` Eli Zaretskii
2020-02-18 20:29 ` Dmitry Gutov
2020-02-18 20:34 ` Robert Pluim
2020-02-18 21:32 ` Dmitry Gutov
2020-02-19 3:27 ` Eli Zaretskii [this message]
2020-02-19 8:59 ` Robert Pluim
2020-02-19 15:39 ` Eli Zaretskii
2020-02-26 9:56 ` Robert Pluim
2020-02-26 14:27 ` Dmitry Gutov
2020-02-26 15:27 ` Robert Pluim
2020-02-26 17:55 ` Eli Zaretskii
2020-02-26 18:36 ` Robert Pluim
2020-02-18 19:29 ` Dmitry Gutov
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=83k14jl0j8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39662@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=rpluim@gmail.com \
--cc=thibault@thb.lt \
/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.