all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 34346@debbugs.gnu.org
Subject: bug#34346: 26.1; Big hang when opening text (racket) files with .art extension (image-mode)
Date: Thu, 07 Feb 2019 05:30:20 +0200	[thread overview]
Message-ID: <83ftt0s2b7.fsf@gnu.org> (raw)
In-Reply-To: <875ztwej09.fsf@ambrevar.xyz> (message from Pierre Neidhardt on Wed, 06 Feb 2019 21:53:26 +0100)

> From: Pierre Neidhardt <mail@ambrevar.xyz>
> Cc: Eli Zaretskii <eliz@gnu.org>, 34346@debbugs.gnu.org
> Date: Wed, 06 Feb 2019 21:53:26 +0100
> 
> If the extension does not match Emacs' expectations, it should not freeze it for
> a minute and almost halt the computer to a grind.
> 
> In other words, Emacs should fail gracefully when image-mode does not make sense
> with the actual content of the file.
> 
> Does that make sense?

I does, I just think that your desire is generally unattainable, even
though in the specific case in point perhaps we should simply drop
support for .art extensions.





  reply	other threads:[~2019-02-07  3:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 12:31 bug#34346: 26.1; Big hang when opening text (racket) files with .art extension (image-mode) Pierre Neidhardt
2019-02-06 14:01 ` Basil L. Contovounesios
2019-02-06 14:15   ` Pierre Neidhardt
2019-02-06 15:47 ` Eli Zaretskii
2019-02-06 19:09   ` Glenn Morris
2019-02-06 19:11     ` Glenn Morris
2019-02-06 20:53       ` Pierre Neidhardt
2019-02-07  3:30         ` Eli Zaretskii [this message]
2019-02-07 12:04           ` Pierre Neidhardt
2019-02-07 14:44             ` Eli Zaretskii
2019-02-07 14:59               ` Pierre Neidhardt
2019-02-07 17:27                 ` Eli Zaretskii
2019-02-07 15:52               ` Stephen Berman
2019-02-07 16:59                 ` Glenn Morris
2019-02-07 17:07                   ` Pierre Neidhardt
2019-02-06 20:55   ` Pierre Neidhardt
2019-02-06 18:27 ` Glenn Morris

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=83ftt0s2b7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34346@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.