From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: sean.sieger@gmail.com, 7716@debbugs.gnu.org
Subject: bug#7716: 23.2.91; Pretest Windows binary doesn't support PNG images
Date: Fri, 24 Dec 2010 11:21:12 -0800 [thread overview]
Message-ID: <9E74C35E9AFE4DB6942F94A6264F6621@us.oracle.com> (raw)
In-Reply-To: <8362ujdmdu.fsf@gnu.org>
> Maybe because the attachments make the message too big. How about if
> you try reporting the bug without the attachments first, then respond
> to the bug report with several messages, one each with a single image
> file that fails to display.
Actually, there is _no_ bug (other than the PNG problem that you reported).
That is, with emacs -Q, I am able to see the images that I reported as not
seeing.
I first tried moving the GnuWin32 folder up my PATH hierarchy, after I
discovered that there were several zlib.dll's on my machine. When I tried with
emacs -Q things were OK. And the PATH position had no bearing on it.
With my setup I cannot see the images in question, for some reason, but with
emacs -Q I can see them OK. Guess I'll have to do the binary-search-dot-emacs
dance to find out what the problem is...
Thinking that perhaps the problem was that I use (an old version of) Cygwin, and
that it has its own zlib etc., I tried setting up Cygwin after i started emacs
-Q, but image display still worked OK (modulo the PNG bug), so that's not the
problem.
Anyway, the good news is that there is no need to file a bug, unless I discover
later that the problem comes from Emacs (and not from some of my code).
next prev parent reply other threads:[~2010-12-24 19:21 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 6:03 bug#7716: 23.2.91; Pretest Windows binary doesn't support PNG images Eli Zaretskii
2010-12-23 15:29 ` Drew Adams
2010-12-23 16:09 ` Eli Zaretskii
2010-12-23 17:36 ` Drew Adams
2010-12-23 18:23 ` Eli Zaretskii
2010-12-23 21:18 ` Drew Adams
2010-12-23 23:24 ` Sean Sieger
2010-12-24 0:40 ` Drew Adams
2010-12-24 2:56 ` David De La Harpe Golden
2010-12-24 10:03 ` Eli Zaretskii
2010-12-24 9:59 ` Eli Zaretskii
2010-12-24 16:03 ` Drew Adams
2010-12-24 16:23 ` Eli Zaretskii
2010-12-24 16:47 ` Drew Adams
2010-12-24 18:11 ` Eli Zaretskii
2010-12-24 18:21 ` Drew Adams
2010-12-24 18:36 ` Drew Adams
2010-12-24 19:03 ` Eli Zaretskii
2010-12-24 19:21 ` Drew Adams [this message]
2010-12-24 19:35 ` Eli Zaretskii
2010-12-24 19:46 ` Drew Adams
2010-12-24 23:52 ` Drew Adams
2011-01-10 22:59 ` Drew Adams
2011-01-11 4:07 ` Eli Zaretskii
2011-01-11 4:41 ` Drew Adams
2011-01-11 18:45 ` Eli Zaretskii
2011-01-11 19:19 ` Drew Adams
2011-01-11 19:31 ` Eli Zaretskii
2011-01-11 19:53 ` Drew Adams
2011-01-11 21:02 ` Lennart Borgman
2010-12-24 18:21 ` Sean Sieger
2010-12-24 19:01 ` Eli Zaretskii
2010-12-23 18:51 ` Sean Sieger
2010-12-23 18:37 ` Sean Sieger
2010-12-23 18:57 ` Sean Sieger
2010-12-23 18:58 ` Eli Zaretskii
2010-12-23 20:23 ` Sean Sieger
2010-12-24 9:47 ` Eli Zaretskii
2010-12-24 22:24 ` Eli Zaretskii
2010-12-24 22:56 ` Sean Sieger
2010-12-25 9:19 ` Eli Zaretskii
2010-12-25 10:58 ` Sean Sieger
2010-12-25 12:57 ` Eli Zaretskii
2010-12-29 18:05 ` Eli Zaretskii
2010-12-29 20:12 ` Sean Sieger
2010-12-29 23:57 ` Jason Rumney
2010-12-30 4:12 ` Eli Zaretskii
2010-12-30 15:58 ` Jason Rumney
2010-12-31 12:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9E74C35E9AFE4DB6942F94A6264F6621@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7716@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sean.sieger@gmail.com \
/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.