unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 21738@debbugs.gnu.org
Subject: bug#21738: 25.0.50; eww freezes/crashes at times
Date: Fri, 23 Oct 2015 17:55:45 +0300	[thread overview]
Message-ID: <83ziz9y6q6.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY2BAzzR99b=sMpkbyEMH421E+jOaPYnrG6BD=GSfpi+Ew@mail.gmail.com>

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Fri, 23 Oct 2015 10:41:34 -0400
> Cc: 21738@debbugs.gnu.org
> 
> > Another idea woukd be to ask on emacs-devel which versions of
> > Imagemagick do people use who can successfully display that page.
> 
> Will do.
> 
> > I don't.  That's why I thought about building without it.
> 
> OK. Have you felt any reason to ever build with Imagemagick because
> emacs built without it lacked any feature you needed?

No.  I don't have much use for showing images in Emacs.

> > The images on that page are PNG image files.  Can you display PNG
> > image files with an Emacs compiled with Imagemagick support, or does
> > Emacs hang (or crash) with every PNG file?
> 
> You know what, I always thought that I can display PNG files in emacs.
> In the version built with Imagemagick, it even successfully displayed
> a PNG file.
> 
> C-x C-f SOMEFILE.png
> 
> When in the same buffer when I did
> 
> C-x C-f SOMEOTHERFILE.png
> 
> my emacs froze just like in that eww experiment!
> 
> So just the first png displayed fine.

I guess it's time to ask on emacs-devel what versions others use, and
whether they have problems with PNG?





  reply	other threads:[~2015-10-23 14:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 22:12 bug#21738: 25.0.50; eww freezes/crashes at times Kaushal Modi
2015-10-22 22:30 ` Wolfgang Jenkner
2015-10-22 22:35   ` Kaushal Modi
2015-10-22 22:37     ` Kaushal Modi
2015-10-23  6:55 ` Eli Zaretskii
2015-10-23 14:01   ` Kaushal Modi
2015-10-23 14:29     ` Eli Zaretskii
2015-10-23 14:41       ` Kaushal Modi
2015-10-23 14:55         ` Eli Zaretskii [this message]
2015-10-23 15:46         ` Wolfgang Jenkner
2015-10-23 16:59         ` Glenn Morris
2015-10-23 19:01           ` Kaushal Modi
2015-10-23 19:15             ` Kaushal Modi
2015-10-23 19:16             ` Eli Zaretskii
2015-10-23 19:23               ` Kaushal Modi
2015-10-23 19:27                 ` Kaushal Modi
2015-10-23 19:46                 ` Eli Zaretskii
2015-10-23 19:52                   ` Kaushal Modi
2015-10-23 20:05                     ` Kaushal Modi
2015-10-23 20:12                     ` Eli Zaretskii
2015-10-23 20:35                       ` Kaushal Modi
2015-10-23 20:42                         ` Eli Zaretskii
2015-10-23 20:43                         ` Kaushal Modi
2015-10-23 21:16                           ` Kaushal Modi
2015-10-23 21:29                             ` Kaushal Modi
2015-10-24  5:22                             ` Eli Zaretskii
2015-10-26 15:26                               ` Kaushal Modi
2015-10-23 16:29       ` Andreas Schwab
2015-10-27 20:25         ` Wolfgang Jenkner
2015-10-27 22:50           ` Kaushal Modi
2015-10-24 15:05 ` Wolfgang Jenkner
2015-10-26 15:22   ` Kaushal Modi
2015-10-27 14:27     ` Wolfgang Jenkner

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=83ziz9y6q6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21738@debbugs.gnu.org \
    --cc=kaushal.modi@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 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).