From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 10578@debbugs.gnu.org
Subject: bug#10578: 24.0.92; No png images on OpenSUSE 12.1
Date: Wed, 25 Jan 2012 20:31:15 +0100 [thread overview]
Message-ID: <87y5svinp8.fsf@gnus.org> (raw)
In-Reply-To: <CAAeL0SQ_7rU3m4jrB4ekkHbY+vkhUE5Os11wOjOzVOatcv41=w@mail.gmail.com> (Juanma Barranquero's message of "Mon, 23 Jan 2012 02:11:42 +0100")
Juanma Barranquero <lekktu@gmail.com> writes:
> The simplest way is just to warn with a fixed message, as in the
> attached patch.
I think that's a good approach.
> In any case, that kind of warning can be intrusive, because
> display-warning keeps displaying the *Warnings* buffer. For example,
> if I load libpng12 in a png14-compiled Emacs and visit a PNG file, I
> get a string of 9 warnings, and 3 more each time I try to advance the
> cursor. I think it wouldn't be much of a problem with image_error,
> because the errors are caused by displaying images, and as soon as you
> kill the corresponding buffer you're OK.
Perhaps it would be an idea to add a simple rate-limiting device? That
is, don't output the "Look in the *Messages* buffer" more often than,
say, once per second. Or minute. Perhaps per ten seconds makes more
sense, so that the message isn't as easily lost, but makes it possible
to continue using Emacs.
[...]
> + warning[0] = intern ("image");
> + warning[1] = build_string ("Image error, please check *Messages*");
> + warning[2] = intern (":error");
> + Vdelayed_warnings_list = Fcons (Flist (3, warning),
> + Vdelayed_warnings_list);
And perhaps just factor it out into its own function, and just say
"Display error, please check *Messages*", and then all redisplay code
that outputs error messages in this manner can use it to alert the user
about this?
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
next prev parent reply other threads:[~2012-01-25 19:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 16:12 bug#10578: 24.0.92; No png images on OpenSUSE 12.1 Lars Ingebrigtsen
2012-01-22 16:30 ` Eli Zaretskii
2012-01-22 16:50 ` Lars Magne Ingebrigtsen
2012-01-22 16:59 ` Achim Gratz
2012-01-22 17:02 ` Andreas Schwab
2012-01-25 19:25 ` Lars Ingebrigtsen
2012-01-22 17:51 ` Eli Zaretskii
2012-01-22 18:12 ` Eli Zaretskii
2012-01-22 19:32 ` Juanma Barranquero
2012-01-22 20:41 ` Eli Zaretskii
2012-01-22 21:25 ` Juanma Barranquero
2012-01-22 21:38 ` Juanma Barranquero
2012-01-23 1:11 ` Juanma Barranquero
2012-01-25 19:31 ` Lars Ingebrigtsen [this message]
2012-01-26 4:26 ` Juanma Barranquero
2012-01-26 5:43 ` Eli Zaretskii
2012-01-26 12:27 ` Juanma Barranquero
2012-01-26 13:45 ` Eli Zaretskii
2012-01-26 14:59 ` Juanma Barranquero
2012-01-26 17:22 ` Juanma Barranquero
2012-01-26 17:26 ` Juanma Barranquero
2016-02-08 6:18 ` Lars Ingebrigtsen
2016-02-08 18:17 ` Eli Zaretskii
2016-02-09 0:13 ` Lars Ingebrigtsen
2016-02-09 0:17 ` Lars Ingebrigtsen
2016-02-09 0:23 ` Lars Ingebrigtsen
2016-02-09 3:41 ` Eli Zaretskii
2012-01-25 19:28 ` Lars Ingebrigtsen
2012-01-26 1:49 ` Stefan Monnier
2012-01-26 17:21 ` Achim Gratz
2012-01-22 16:46 ` Achim Gratz
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=87y5svinp8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=10578@debbugs.gnu.org \
--cc=lekktu@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).