From 3d0e859692956d706154a7af4e072a9f23f0cd78 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Cl=C3=A9ment=20Pit-Claudel?= Date: Wed, 22 Apr 2020 17:46:07 -0400 Subject: [PATCH] Minor doc clarification regarding fringe bitmaps * doc/lispref/display.texi (Customizing Bitmaps): Add a note regarding the order of bits being the opposite of that in XBM images. (Bug#40784) --- doc/lispref/display.texi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi index 0b7358ea171..e655f2f0cae 100644 --- a/doc/lispref/display.texi +++ b/doc/lispref/display.texi @@ -4342,7 +4342,8 @@ The argument @var{bits} specifies the image to use. It should be either a string or a vector of integers, where each element (an integer) corresponds to one row of the bitmap. Each bit of an integer corresponds to one pixel of the bitmap, where the low bit corresponds -to the rightmost pixel of the bitmap. +to the rightmost pixel of the bitmap. (Note that this order of bits +is opposite of the order in XBM images; @pxref{XBM Images}.) The height is normally the length of @var{bits}. However, you can specify a different height with non-@code{nil} @var{height}. The width -- 2.39.2