unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36337@debbugs.gnu.org, triska@metalevel.at
Subject: bug#36337: 26.1; XBM images are sometimes not displayed correctly
Date: Sun, 23 Jun 2019 16:26:16 +0000	[thread overview]
Message-ID: <CAOqdjBfp7Gp2=9bOe4pw4iAYPY=vqXmo-ncf6W-L_R1zozbkjw@mail.gmail.com> (raw)
In-Reply-To: <83tvcgml2s.fsf@gnu.org>

On Sun, Jun 23, 2019 at 2:29 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Pip Cet <pipcet@gmail.com>
> > Date: Sun, 23 Jun 2019 08:05:55 +0000
> > Cc: 36337@debbugs.gnu.org
> > This is easy enough to fix by rewriting the bool vector, but that's
> > potentially very slow (on debug builds), so maybe we shouldn't do
> > that?
> >
> > Does the attached patch work for you?
>
> Thanks, but I really hope there's a more elegant solution.

I thought there had to be, but I've yet to think of anything that's
unequivocally better.

My suggestion would be to expand `substring' to work on bool vectors,
then building a vector of bool vectors and using the existing code for
that case. Less code in image.c, plus a new utility function that
might be generally useful. (However, do we want to encourage people to
use bool vectors?)

I don't think performance is an issue, though, and you might disagree.

> If not,
> maybe we should simply require that both width and height be an
> integral multiple of 8 in this case.

Why would you require the height to be a multiple of 8?





  reply	other threads:[~2019-06-23 16:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  7:15 bug#36337: 26.1; XBM images are sometimes not displayed correctly Markus Triska
2019-06-23  8:05 ` Pip Cet
2019-06-23  8:22   ` Markus Triska
2019-06-23 14:29   ` Eli Zaretskii
2019-06-23 16:26     ` Pip Cet [this message]
2019-06-23 16:40       ` Eli Zaretskii
2019-06-23 19:16         ` Pip Cet
2019-06-28  7:57           ` Eli Zaretskii
2019-06-28  8:29             ` Pip Cet
2019-06-28 12:43               ` Eli Zaretskii
2019-06-29  7:20                 ` Pip Cet
2019-06-29  7:56                   ` Eli Zaretskii
2019-06-29  8:25                     ` Pip Cet
2019-06-29  9:54                       ` Eli Zaretskii
2019-06-30  9:48                         ` Pip Cet
2019-06-30 14:34                           ` Eli Zaretskii
2019-06-30 14:53                             ` Pip Cet
2019-06-30 15:15                               ` Eli Zaretskii
2019-06-30 15:36                                 ` Pip Cet
2019-06-30 16:09                                   ` Eli Zaretskii
2019-06-30 17:12                                     ` Pip Cet
2019-06-30 17:35                                       ` Eli Zaretskii
2019-09-24 16:35                                         ` Lars Ingebrigtsen

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='CAOqdjBfp7Gp2=9bOe4pw4iAYPY=vqXmo-ncf6W-L_R1zozbkjw@mail.gmail.com' \
    --to=pipcet@gmail.com \
    --cc=36337@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=triska@metalevel.at \
    /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).